*I get the warning that if the host wouldn't be available within the next 2 minutes, the session will be cancelled! This happened already roughly 10 mins ago.
<scribe> scribenick: wolfgang
Terence, Uni of Minnesota Press
Terence: digital project manager
in charge of digital workflow, but not developer
tzviya: we need developer time
*Wiley has nice music :)
<tzviya> https://github.com/IDPF/epubcheck/wiki/Welcome-New-Contributor
tzviya: epubcheck wiki has a new welcome document (written by Tobias)
step by step introduction for new members
<tobias> hope we may get new coders, Romain is more or less leaving
tobias: hopefully some developers will join the task force
tzviya: romain mainly develops other DAISY progs
danger that there won't be developers for epubcheck!!!
list of contributors is "historical"
we should perhaps state that more explicitly
<tzviya> https://github.com/w3c/publ-cg/wiki/epubcheck-TF-meeting-minutes-and-summaries#2017-09-28
tzviya: maintenance release in mid-November?
tobias: won't contain EPUB 3.1 support, waiting for feedback from Romain in some issues
mid-November not realistic, still a couple of issues to be solved
tzviya: press release in preparation, explains why 3.1 won't be supported, but some important issues
<TobiasFischer> GitHub project for EPUB 3.1 support: https://github.com/IDPF/epubcheck/projects/1
tobias: matt wrote google doc about spec changes, could be a first step for a diff doc
naomi: was basing her work on matt's doc
naomi has an additional doc with more notes and plans to port that to matt's doc
<TobiasFischer> https://docs.google.com/document/d/1kgoxSEhF_iTyixj6XaZIc0cgruBNNQknaif4fyXqKto/edit
naomi: worked on package docs,
structural vocab, core media types
... should i create github issues or write issues in this
google doc
tobias: prefers github issues
tzviya: as well supports github
issues for documenting open issues
... Terence is willing to volunteer for documentation. Goal:
finish by end of November
naomi: thinks it's realistic, at least aim for the end of November
Terence agrees to that
tzviya: what else could be done?
rick: willing to go through the codebase himself
tzviya: Java knowledge needed for codebase
tobias: cleaning the tests would ideally require some Java knowledge
fixing bugs another issue, a lot of tasks available
tzviya: most important: document changes for 3.1 and urgent call for developers
This is scribe.perl Revision: 1.152 of Date: 2017/02/06 11:04:15 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Succeeded: s/nav/core media types/ Default Present: tzviya, wolfgang, Dan_Sanicola, mattg, TobiasFischer, duga Present: tzviya wolfgang Dan_Sanicola mattg TobiasFischer duga Found ScribeNick: wolfgang Inferring Scribes: wolfgang WARNING: No meeting title found! You should specify the meeting title like this: <dbooth> Meeting: Weekly Baking Club Meeting WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth WARNING: No date found! Assuming today. (Hint: Specify the W3C IRC log URL, and the date will be determined from that.) Or specify the date like this: <dbooth> Date: 12 Sep 2002 People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.)[End of scribe.perl diagnostic output]