Council agenda 2013-11

Monday 11 November 2013

 * 09:00 - 10:30 Morning Discussion Session
 * Topics Including:
 * Add here
 * 10:30 - 10:45 Break
 * 11:45 - 12:30 SourceForge Tickets
 * 12:30 - 14:00 Lunch Break (in Meeting Room)
 * 14:00 - 15:30 Afternoon Discussion Session
 * Topics Including:
 * Add here
 * 15:30 - 15:45 Break
 * 15:45 - 17:30 SourceForge Tickets

Tuesday 12 November 2013

 * 09:00 - 10:30 Morning Discussion Session
 * Topics Including:
 * Add here
 * 10:30 - 10:45 Break
 * 11:45 - 12:30 SourceForge Tickets
 * 12:30 - 14:00 Lunch Break (in Dining Room)
 * 14:00 - 15:30 Afternoon Discussion Session
 * Topics Including:
 * Add here
 * 15:30 - 15:45 Break
 * 15:45 - 17:30 SourceForge Tickets

Wednesday 13 November 2013

 * 09:00 - 10:30 Morning Discussion Session
 * Topics Including:
 * Add here
 * 10:30 - 10:45 Break
 * 11:45 - 12:30 SourceForge Tickets
 * 12:30 - 14:00 Lunch Break (in Meeting Room)
 * 14:00 - 15:30 Afternoon Discussion Session
 * Topics Including:
 * Add here
 * 15:30 - 15:45 Break
 * 15:45 - 17:30 SourceForge Tickets

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?


 * P6 and Release structure


 * Request from Ontology SIG [SR]. See paper at  http://wiki.tei-c.org/index.php?title=Council_agenda_2013-11-OntologySIG


 * 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 [MH]