Just some explanations for other readers of TEI-L:
This is a good example of the kind of community development that
the TEI relies on. Stuart (as a previous member of Council)
happened to already have write access to the TEI subversion
repository. If he hadn't, he could have submitted changes to be
done as a ticket on the SourceForge website (http://tei.sf.net/).
The 'Jenkins' he mentions is a continuous integration server that
rebuilds the whole TEI universe of guidelines, schemas, etc.
whenever someone checks in a change. As part of that, of course,
it tests for some of the more predictable problems, checks
validity, etc. You can see Jenkins do its thing at (for example):
on the version that Martin Holmes runs. There is also another one
here in Oxford, and some others, and if you wanted to have your
own you could follow the instructions at:
(correcting them if you encounter any problems). We'd be
interested to know of any problems people encounter in doing so.
Looking at the version of the TEI on the Jenkins server shows you
the latest version of everything as generated from the TEI
SourceForge subversion repository. On a release day we often
have to go through several rebuilds and it is a bit like watching
a pot/kettle boil (but with more cryptic error messages).
In the next release of the TEI we're planning on actively asking
members of TEI-L to review it and alert us to any bugs/typos/etc.
they find before we make the release public. (A beta-test of the
TEI outputs if you will.) I hope this is a welcome improvement in
both outreach and transparency for the TEI community.
(with 'Chair of TEI Technical Council' hat on)
On 21/01/13 04:51, stuart yeates wrote:
> On 21/01/13 09:14, Sebastian Rahtz wrote:
>> On 20 Jan 2013, at 20:06, stuart yeates <[log in to unmask]>
>>> On 21/01/13 01:22, Sebastian Rahtz wrote:
>>>> How would we distinguish the bits you added from the bits
>>>> which came from the TEI?
>>> You don't need to. You use a statement such as "TEI materials
>>> are licensed under..." and not an explicit claim that
>>> everything in the file is a TEI material.
>> true. do you fancy adding that to the relevant files?
> It turns out that there was already some proper licensing info in
> Exemplars/tei_tite.odd, which I've made uniform across the rest.
> It seems to work and hasn't broken anything in any way that
> Jenkins detects.
Dr James Cummings, [log in to unmask]
Academic IT Services, University of Oxford