[tei-council] automated oxygen update

[Sebastian Rahtz]

On 24 Jan 2013, at 16:43, James Cummings <james.cummings at it.ox.ac.uk> wrote:

> 
> Then definitely outside the lower down release tree but inside 
> /release/ I guess.  though we could do 
> /release/someDirectoryName/updateSite.oxygen of course, where 
> 'someDirectoryName' is something that means 'configuration files 
> for any third-party tools we want to support'?
> 
could be in /oxygen/ or /release/oxygen/ ?

once we decide that, we can ask for more testers, and write documentation.
but obviously better to stick with a destination if we can

for those who haven't looked at the source, it pulls the distribution from
https://code.google.com/p/oxygen-tei/  - which goes, of course, some way
towards paciifying Martin Mueller's complaints about unfriendliness,
at almost no cost to us (since we do the thing at oxygen-tei anyway,
we just have to maintain this one simple config file)

--
Sebastian Rahtz      
http://www.justgiving.com/SebastianRahtz
Director (Research Support) of Academic IT Services 
University of Oxford IT Services
13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431