[tei-council] Sourceforge Upgrade

[James Cummings]

In that case does anyone have any final reservations that I 
should not do this *tomorrow* Wednesday 13 March?

I will take silence as assent and proceed tomorrow if I don't 
hear cries of stop.
I'll send an email to this list announcing before I start (so get 
anything checked into SVN now while you can). And I'll send email 
out afterwards saying that it is done. (And that the Jenkins 
owners should reconfigure their jenkins) and then to TEI-L noting 
the change of URLs for the repository etc.

-James


On 12/03/13 17:33, Sebastian Rahtz wrote:
>
> On 12 Mar 2013, at 16:30, James Cummings <james.cummings at it.ox.ac.uk> wrote:
>
>> One of the decisions is whether this is a good point to move
>> community-contributed code out of the repository (e.g. things
>> like Byzantium and Vesta and process-pb).  I'd be interested in a
>> list from people, especially Sebastian, of what they think should
>> be moved elsewhere?
>
>
> I'm happy to move passivetex, Stylesheets-xslt1, TEIOO-Deprecated, TEIWORD, jerusalem, Vesta and tei-emacs to Github;
> but I see any advantage to doing it before the migration. Just press the button, Luke.
>
> Byzantium is not on SF
>
> process-pb is part of Stylesjheets. splitting that is a bigger project
> --
> Sebastian Rahtz
> Director (Research) of Academic IT
> University of Oxford IT Services
> 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
>


-- 
Dr James Cummings, James.Cummings at it.ox.ac.uk
Academic IT Services, University of Oxford