[tei-council] TEI Stylesheets, the road less travelled

[Syd Bauman]

Well I'm not going to throw a hissy fit, but why would we want to do
such a thing? Yes, git is newer and shinier than svn, but its
advantages are not those we want anyway. And its added complexity (in
order to support those advantages that we won't be taking advantage
of) will make things harder for those who want to pick this stuff up.
True, some would say the user interface at GitHub is a bit nicer than
SourceForge, but not everyone, and that doesn't seem like sufficient
reason for such a significant change. Doesn't the maxim "if it ain't
broke, don't fix it" apply? Or am I missing something? (Are we think
MEI would be a fork instead of a customization or some such?)

P.S. I'll try to take a good look at the <precision> recommendation later
     today.


> As part of a summer clear out, I would like to start sorting out
> the TEI XSL stylesheets. You may have noticed that I have done a
> fair amount on the general documentation already (mure more do)
> 
> as regards the source, I have cloned the whole shebang to GitHub,
> under the TEI's name, at https://github.com/TEIC/Stylesheets.
> 
> I propose to (in order)
>    1 not work on the Subversion copy at all any more, ever 2 rename
>    directories, and generally move things around, in Github. backward
>    compatibility not guaranteed 3 set up Jenkins to take this as the
>    master copy for releases to e.g. oxygen and TEI web site 4 start
>    telling people how to use the Github setup 5 delete everything not
>    needed to make Guidelines from Sourceforge copy (see how it goes)
> 
> will y'all violently object and throw hissy fits?