[tei-council] Criteria for TEI Repository Inclusion

Laurent Romary laurent.romary at loria.fr
Wed Mar 3 09:03:49 EST 2010

Do rember that whatever we discuss here, the result has to be  
transparent for our users. Let me restate the policy statement I made  
a long time ago: we should avoid fragmented our technical tools...

Le 3 mars 10 à 14:53, James Cummings a écrit :

> Martin Holmes wrote:
>> My feeling is that the only subprojects that should end up on the  
>> site are ones which are sponsored/maintained by an official SIG. If  
>> the
>> SIG disbands or becomes moribund (no activity for a year, say),  
>> then the
>> customization should be moved to an archive area as soon as a problem
>> appears with it (for instance, if an update to TEI breaks something  
>> in
>> the customization, or a bug emerges that no-one is willing to fix).
> Would another option be to have a separate repository for TEI-SIG
> (i.e. contrib of a specialised sort) and have it administered by
> the SIG coordinator?
> -James
> _______________________________________________
> tei-council mailing list
> tei-council at lists.village.Virginia.EDU
> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council

More information about the tei-council mailing list