- Tei-council - lists.tei-c.org

repo
by Lou Burnard 11 Sep '15

11 Sep '15

Hugh writes > You’ll probably be better off if you grab a new clone of the data rather than trying to merge the old one. For avoidance of doubt, and for the benefit of those still struggling with gittery, could you spell out what that means in terms of command line commands? I assume I need to clone a new version of the repo if I want to change things in the trunk source (e.g. answer a ticket or two), having further assumed that the freeze on source updates is no longer in effect? And lastly (sorry to ask so many stupid questions) do I also need to refresh my current P5-Pure branch repo ?

1 0

Git Repo Update
by Hugh Cayless 10 Sep '15

10 Sep '15

Dear all, Lou pointed out that his email address was wrong in the commits imported from svn. It must have been wrong in my spreadsheet to being with. I’ve fixed the problem, but that meant a substantial rewrite of the commit history. You’ll probably be better off if you grab a new clone of the data rather than trying to merge the old one. Apologies for the inconvenience. Hugh

1 0

Changelog format
by Hugh Cayless 10 Sep '15

10 Sep '15

Hi all, I’m looking at ways to replace the current changelog generation routine for Git, and have a formatting question. It’s pretty easy to come up with something that’s close, but not identical, to the current format. My question is whether that is good enough, of if there’s some reason to stick with the old format as-is. The old format is: 2015-03-10 Lou Burnard <lou.burnard(a)retired.ox.ac.uk> Changed paths: M /trunk/P5/Source/Guidelines/en/DS-DefaultTextStructure.xml M /trunk/P5/Source/Guidelines/en/USE.xml M /trunk/P5/Source/Specs/TEI.xml clarify structure of TEI element per bug #742 And it would be replaced by: 2015-03-10 Lou Burnard <lou.burnard(a)retirees.ox.ac.uk> 9fc47c4 clarify structure of TEI element per bug #742 M P5/Source/Guidelines/en/DS-DefaultTextStructure.xml M P5/Source/Guidelines/en/USE.xml M P5/Source/Specs/TEI.xml The short-form commit hash above is an optional extra. We didn’t include svn rev numbers before. Another simple alternative is: 2015-03-10 Lou Burnard <lou.burnard(a)retirees.ox.ac.uk> 9fc47c4 clarify structure of TEI element per bug #742 P5/Source/Guidelines/en/DS-DefaultTextStructure.xml | 6 ++++-- P5/Source/Guidelines/en/USE.xml | 6 +++++- P5/Source/Specs/TEI.xml | 41 +++++++++++++++++++++++++++++++++++------ 3 files changed, 44 insertions(+), 9 deletions(-) Which gives more detail about the nature of the changes. Thoughts?

4 3

F2F scheduling in Lyon
by Hugh Cayless 10 Sep '15

10 Sep '15

Dear all, Any objections if our meeting happens on Sunday, Oct. 25, Monday, Oct. 26, and the morning of Wednesday, Oct. 28? Emmanuelle’s trying to make the schedule work out and Tuesday is currently crowded, but there’s a free room Wednesday morning. Please let me know ASAP if this presents a problem. Thanks, Hugh

9 26

Re: [tei-council] Processing Model Documentation for TEI Guidelines
by Lou Burnard 10 Sep '15

10 Sep '15

I started looking at this, but something seems to have gone wrong in the conversion to doc e.g. * *"*The <model> element is the basis of any processing model documentation. foundation The <model> element is used to document the intended processing model for a particular element in an abstract manner which separates . A required @behaviour attribute which documents the processing function and controls which processing function should be used to present this element in output. * " is gibberish. Personally I would *much* rather edit/comment on the ODD source, which must exist somewhere. On 08/09/15 16:08, James Cummings wrote: > > Hi all, > > I've been taking the documentation in the tei-pm.odd and rewriting it > to be something which could be added to the TEI Guidelines. I've put > it up as a google doc with open editing for those of you who wish to > improve it. This will (of course) be encoded in TEI, it is merely > being placed here for ease of collaborative authorship. I believe > that the appropriate place for it is either 22.4.8 shortly after > http://www.tei-c.org/release/doc/tei-p5-doc/en/html/TD.html#TDENT or > another possibility is as a new 22.5 (pushing the current one down to > 22.6). > > https://docs.google.com/document/d/1C1fw5SCrJBZxT7O7-_HLrkBQJk5YZZJzzDbA-ir… > > > Feel free to improve it, and if you have any questions or comments > please make them here on the TEI Simple mailing list. > > -James > >

2 5

Jenkins build is back to normal : Stylesheets #1967
by mholmes＠uvic.ca 09 Sep '15

09 Sep '15

See <http://teijenkins.hcmc.uvic.ca/job/Stylesheets/1967/changes>

1 0

Jenkins build is back to normal : TEIP5 #2135
by mholmes＠uvic.ca 09 Sep '15

09 Sep '15

See <http://teijenkins.hcmc.uvic.ca/job/TEIP5/2135/>

1 0

September Telecon Poll
by Hugh Cayless 08 Sep '15

08 Sep '15

Please indicate your availability at http://doodle.com/poll/4fbdufgwsyc8ruc3 Reminder: we will freeze on October 1, so in my mind, the earlier we meet before that, the better, but we'll have to see what everyone's availability is. All the best, Hugh

1 0

Processing Model Documentation for TEI Guidelines
by James Cummings 08 Sep '15

08 Sep '15

Hi all, I've been taking the documentation in the tei-pm.odd and rewriting it to be something which could be added to the TEI Guidelines. I've put it up as a google doc with open editing for those of you who wish to improve it. This will (of course) be encoded in TEI, it is merely being placed here for ease of collaborative authorship. I believe that the appropriate place for it is either 22.4.8 shortly after http://www.tei-c.org/release/doc/tei-p5-doc/en/html/TD.html#TDENT or another possibility is as a new 22.5 (pushing the current one down to 22.6). https://docs.google.com/document/d/1C1fw5SCrJBZxT7O7-_HLrkBQJk5YZZJzzDbA-ir… Feel free to improve it, and if you have any questions or comments please make them here on the TEI Simple mailing list: teisimple(a)maillist.ox.ac.uk (or teisimple-subscribe(a)maillist.ox.ac.uk to subscribe). -James -- Dr James Cummings, James.Cummings(a)it.ox.ac.uk Academic IT Services, University of Oxford

1 0

Are we jumping to GitHub or are we not?
by Martin Holmes 04 Sep '15

04 Sep '15

Hi all, My Jinks is able to build the TEI products from GitHub, thanks to some help from Hugh, and James's will also be switched today as a secondary test. The only wrinkle is that Jinks will not be able to notify committers when a build fails, because GitHub doesn't have a transparent way of automatically associating committer ids with email addresses, but we can handle this by having it notify the Council mailing list instead. I've set that up, and I think it might just work out of the box but if not Kevin will be able to allow it. We now want to start revising those "Editing the Guidelines" and similar documents to point to GitHub, and consider what we're going to do about tickets. Is there anyone at this point who objects to moving the repo to GitHub? If not, then I suggest we start updating documentation. Tickets can stay on SF until we have a comfortable migration path for them. Cheers, Martin

5 6