[tei-council] automated oxygen update

[James Cummings]

On 24/01/13 16:16, Sebastian Rahtz wrote:
>
> On 24 Jan 2013, at 16:11, James Cummings
> <James.Cummings at it.ox.ac.uk> wrote:
>>> yes, but signed by who?
>>
>> TEI-C as a consortium perhaps?
>
> isn't the _point_ of signing that its traceable to a trusted
> _person_? maybe I misunderstand what oxygen folks mean

Dunno.  It might be a role (Council Chair, or Release Technician) 
can be viewed as trusted for oXygen's point of view.  I've 
emailed them, CC'ing you.

> I had kind of thought right up at http://www.tei-c.org/release
> - its a meta file, not documentation, I think.

I agree... just worry about either cluttering things up or 
appearing to endorse only oXygen.

> and yes, it would change if we decided to repackage the same
> TEI P5 release with a later stylesheets (as in fact I will do
> shortly for the new oxygen release)

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'?

-James

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