> (1) Volunteers to become editors of the Stoa blog and add news items as
> they arise.
Yes, while we need to be discerning on relevant news, we also need to make
sure no news-worthy news item slips through our nets.
> (2) What topics should we divide news items into?
May I suggest to keep your three four topics (projects;
tools; events), keep "General" as a default for items that don't fit into
any other category, and divide "admin" into "digClass" and "Stoa" for news
items pertinent to either of these two projects?
Best
Juan
----------------------------------------------------------------------------
Juan Garcés
Centre for Computing in the Humanities, King's College London
Kay House, 7 Arundel Street
London WC2R 3DX
T: +44 (0)20 7848 1393
F: +44 (0)20 7848 2980
-----Original Message-----
From: The Digital Classicist List [mailto:[log in to unmask]]
On Behalf Of Gabriel BODARD
Sent: 02 August 2005 15:47
To: [log in to unmask]
Subject: Weblog
Dear all,
We have just moved the Digital Classicist news service (aka the Blog) to the
Stoa's server (many thanks to Ross for this). See http://www.stoa.org. We
now
have two things to ask of you, the Digitalclassicist community:
(1) Volunteers to become editors of the Stoa blog and add news items as they
arise. If you need help signing up or adding news items, contact Ross or
myself
for assistance.
(2) What topics should we divide news items into? At the moment, all news is
filed under the topic "General". Other possible topics include: projects;
tools; events; admin. We probably want to avoid the Slashdot situation where
every news item is a new topic, but a range of topics under which entries
can
be sorted or filed might be a good thing. Any other suggestions?
All best,
Gabriel
--
=======================================
Gabriel BODARD
Inscriptions of Aphrodisias
Centre for Computing in the Humanities
King's College London
Kay House
7, Arundel Street
London WC2R 3DX
Email: [log in to unmask]
Tel: +44 (0)20 78 48 13 88
Fax: +44 (0)20 78 48 29 80
=======================================
|