Council agenda 2013-11

Map of locations: https://mapsengine.google.com/map/edit?mid=z5kNNI17e3DU.kEaB-XyBbZ-A

Open Google Doc Minutes at: https://docs.google.com/document/d/1F0pOZ5PkWvIfnPgAKCONRdrDZhl4dkig_zqCiPvUG8A/edit?usp=sharing (final minutes at http://www.tei-c.org/Activities/Council/Meetings/tcm56.xml)

Sunday 10 November 2013

 * Evening plans: From 6pm JamesC will be in The Royal Oak http://www.theroyaloakoxford.co.uk/ 42-44 Woodstock Road, Oxford, OX2 6HT
 * And a good time was had by Kevin, Syd, Paul, Martin, and Martin’s brother Nick. Thank you, James; you’re a great pub-host!

Monday 11 November 2013

 * 09:00 - 10:30 Morning Discussion Session
 * Topics Including:
 * EEBO TCP: Reaching consensus with EEBO TCP [SR] (see http://tei.oucs.ox.ac.uk/EEBO/ for summary of problem, and links to tickets)
 * Although the above link does have links to tickets and what I think is probably a set of summaries of particular problems, it does not provide a summary of the problem. Could someone (SR, JC, PS?) explain the big picture, here — what is the exact task (making sure EEBO TCP is TEI P5 conformant?), and why is it important?
 * Report on specification and estimated cost for XPointer resolver [HC/SB]
 * Report on specification and estimated cost for oXygen front end for ODD [SB/EM]
 * 10:30 - 10:45 Break
 * 10:45 - 12:30 SourceForge Tickets
 * 12:30 - 14:00 Lunch Break (in Meeting Room)
 * 14:00 - 15:30 Afternoon Discussion Session
 * Topics Including:
 * Pure ODD is there a link for what pure ODD entails? yes, at the bottom of the Wiki
 * TEI Roma Replacement Specification see https://docs.google.com/a/blushingbunny.net/document/d/1766WTJV2xcfANh8HRZW5m520yrC1nCzQJzUgKpwiylI/edit
 * 15:30 - 15:45 Break
 * 15:45 - 17:30 SourceForge Tickets
 * 19:00 -- "Sojo", Szechuan/Shanghainese/Cantonese restaurant, website at http://www.sojooxford.co.uk/ claims vegetarian menu on request. SoJo (Chinese) http://www.sojooxford.co.uk/ 6/9 Hythe Bridge Street, Oxford, OX1 2EW

Tuesday 12 November 2013

 * 09:00 - 10:30 Morning Discussion Session
 * Topics Including:
 * Release Process (see below)
 * Ideas on how to run an experimental TEI Hackathon [SR]
 * i18n: take forward updating translations
 * Attributes without examples.
 * 10:30 - 10:45 Break
 * 10:45 - 12:30 SourceForge Tickets
 * 12:30 - 14:00 Lunch Break (in Dining Room)
 * 14:00 - 15:30 Afternoon Discussion Session
 * Topics Including:
 * Text Directionality Workgroup: look at first draft of new Guidelines sections and questions [MH]
 * Into the blue yonder: is it time to have a TEI P6 discussion again? [SR]
 * 15:30 - 15:45 Break
 * 15:45 - 17:30 SourceForge Tickets


 * Evening: A meal chez Rahtz, 8pm directions and description to follow.

Wednesday 13 November 2013

 * 09:00 - 10:30 Morning Discussion Session
 * Cheatsheets: Short best/recommended practice documents
 * From 09:30: Discussion with Torsten Schassan (via skype) about need for Object Description Chapter (see http://wiki.tei-c.org/index.php/Council_agenda_2013-11-OntologySIG)


 * 10:30 - 10:45 Break
 * 10:45 - 12:30 SourceForge Tickets
 * 12:30 - 14:00 Lunch Break (in Meeting Room)
 * 14:00 - 15:30 Afternoon Discussion Session
 * Topics Including:
 * LingSIG Meeting and Modelling / Serializing standoff (c.f. http://sourceforge.net/p/tei/feature-requests/378/ )
 * Terminology Chapter, TBX, and https://sourceforge.net/p/tei/feature-requests/482/
 * 15:30 - 15:45 Break
 * 15:45 - 16:30 SourceForge Tickets


 * Evening -- The Rickety Press http://www.thericketypress.com, 67 Cranham Street, Oxford, OX2 6DE

More Details on Agenda topics

 * Discuss possible revisions to step-by-step instructions in release procedure
 * Should step 1 (creating P5/ReleaseNotes/readme-X.X.X.xml) happen at the same time as step 4 (freeze on commits)?
 * Should we do steps 1 through 5 farther in advance so we can check that the version numbers etc. show up in the right places in files resulting from the build process?
 * Immediately after a release, should we change the version number in the repository to next release number (e.g., "2.5a", with "a" for "alpha") so people won't be confused looking at the last successful build and seeing the old version number. Then immediately before a release, when we put out the call to TEI-L to look for typos, we can change the "a" to "b" (e.g., "2.5b") and then when we actually release, remove the "b".
 * Should we have the date of a build be auto-generated? It will make it clearer that people are looking at something that's evolving, and it will also make it easier to diagnose the occasional case where one of the Jenkins servers stops updating.
 * proposals for &lt;standoff&gt; -- have Javier join the discussion?


 * i18n: how to take forward updating of the translations


 * Development of Pure ODD [LB and SR]. See paper at http://tei.oucs.ox.ac.uk/Talks/2013-09-acmdoceng/rahtzburnard.pdf and the code at https://github.com/TEIC/pureodd


 * Ideas on how to run an experimental TEI Hackathon [SR]


 * Into the blue yonder: is it time to have a TEI P6 discussion again? [SR]


 * Reaching consensus with EEBO TCP [SR] (see http://tei.oucs.ox.ac.uk/EEBO/ for summary of problem, and links to tickets)


 * Report on new Roma Specification [JC]


 * Report on specification and estimated cost for XPointer resolver [HC/SB]


 * Report on specification and estimated cost for oXygen front end for ODD [SB/EM]


 * Cheatsheets: Short best/recommended practice documents


 * Text Directionality Workgroup: look at first draft of new Guidelines sections and questions [MH]