Difference between revisions of "Council agenda 2013-11"

From TEIWiki
Jump to navigation Jump to search
m (→‎Tuesday 12 November 2013)
m
Line 1: Line 1:
 
Map of locations: https://mapsengine.google.com/map/edit?mid=z5kNNI17e3DU.kEaB-XyBbZ-A  
 
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
  
 
== Sunday 10 November 2013 ==
 
== Sunday 10 November 2013 ==
Line 34: Line 35:
 
**Topics Including:
 
**Topics Including:
 
** Text Directionality Workgroup: look at [[Text Directionality Draft|first draft of new Guidelines sections]] and [[Text Directionality Draft Questions|questions]] [MH]
 
** Text Directionality Workgroup: look at [[Text Directionality Draft|first draft of new Guidelines sections]] and [[Text Directionality Draft Questions|questions]] [MH]
−
** LingSIG Meeting and Modelling / Serializing standoff (c.f. http://sourceforge.net/p/tei/feature-requests/378/ )
+
** Into the blue yonder: is it time to have a TEI P6 discussion again? [SR]
−
** Terminology Chapter, TBX, and https://sourceforge.net/p/tei/feature-requests/482/
 
 
* 15:30 - 15:45 Break
 
* 15:30 - 15:45 Break
 
* 15:45 - 17:30 SourceForge Tickets
 
* 15:45 - 17:30 SourceForge Tickets
Line 51: Line 51:
 
* 14:00 - 15:30 Afternoon Discussion Session
 
* 14:00 - 15:30 Afternoon Discussion Session
 
**Topics Including:
 
**Topics Including:
−
** Into the blue yonder: is it time to have a TEI P6 discussion again? [SR]
+
** 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:30 - 15:45 Break
 
* 15:45 - 16:30 SourceForge Tickets  
 
* 15:45 - 16:30 SourceForge Tickets  

Revision as of 17:57, 10 November 2013

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

Sunday 10 November 2013

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)
    • 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
  • 11: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
    • TEI Roma Replacement Specification
  • 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]
  • 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
  • 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


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 <standoff> -- have Javier join the discussion?
  • i18n: how to take forward updating of the translations
  • 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]
  • 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
Retrieved from "https://wiki.tei-c.org/index.php?title=Council_agenda_2013-11&oldid=12580"