[tei-council] Sourceforge Upgrade

Gabriel Bodard gabriel.bodard at kcl.ac.uk
Tue Mar 12 13:45:09 EDT 2013


Then if we want to roll, we just need:

(a) code freeze, general announcement

(b) someone press the button (in the morning, I'd suggest)

(c) with people who maintain the jinkses (and any externals in the svn?) 
on standby to update the urls asap.

(d) release code freeze...

Anything missing?

On 2013-03-12 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 Gabriel BODARD
Researcher in Digital Epigraphy

Digital Humanities
King's College London
Boris Karloff Building
26-29 Drury Lane
London WC2B 5RL

T: +44 (0)20 7848 1388
E: gabriel.bodard at kcl.ac.uk

http://www.digitalclassicist.org/
http://www.currentepigraphy.org/



More information about the tei-council mailing list