[tei-council] Criteria for TEI Repository Inclusion

[James Cummings]

Hi there,

We were having a discussion recently about a TEI Customisation that we 
created for the ENRICH project and its future maintenance.  Although I 
believe we're leaning in favour of setting up a separate Sourceforge or 
Google Code repository for it and managing it separately from the TEI SF 
repository, somehow 'donating' it to the TEI-C was suggested at one 
point.  While I frankly think it is better for such things to be managed 
separately form the TEI, it made me realise that we don't seem to have a 
set policy on when something (an ODD, a piece of software, etc.) gets 
included in the TEI SF repository and when it doesn't.

Currently we have directories for the following:

Carthage
Documents
Extensions
genetic
I18N
javalib
jerusalem
P4toP5
P5
P5-Council
passivetex
Roma
Stylesheets
Stylesheets2
TEIC
TEICSS
tei-emacs
TEIOO
TEIWORD
Vesta


And of course a number of ODD files in P5/Exemplars/ which are the 
templates provided in Roma.

The question is when a new piece of software or important TEI 
Customisation is being created, when should it be considered part of the 
TEI SF repository and when should it be hosted elsewhere?

One thing to bear in mind is that the TEI SF SVN repository does not 
give fine-grained access.  If you give access to personX as a developer 
on it, then they have the ability to add/change/edit the whole of the 
TEI Guidelines and any of the software above.  Currently I'm just trying 
to have us think about when something should be part of this repository 
or not, and under what circumstances we might 'adopt' things that the 
TEI-C itself did not create.  However, I could see good arguments for 
making things like the Stylesheets, Roma, Vesta, TEIOO, etc. separate SF 
or other projects at some point in the future.

Any thoughts?

-James