667
edits
Changes
no edit summary
** Get going on your 0.1 Release, see [[0.1 Release 2012 WebVTT Test Suite]]
** Setup [https://help.github.com/articles/generating-ssh-keys ssh keys on matrix] for your github account
== Weeks 5-7, Toward a Parser ==
* We have ~300 tests, now to put them to use!
* What we have in the way of existing implementations:
** C implementation (Ralph's WIP), see https://github.com/rillian/webvtt/blob/master/webvtt.c
** C++ (WebKit) implementation, see WebVTT*.{cpp|h} in https://github.com/WebKit/webkit/tree/master/Source/WebCore/html/track
** JS (validator) implementation, see https://github.com/humphd/node-webvtt/blob/master/lib/parser.js
* What we need:
** Complete C implementation, done to spec
*** Convert parsing rules into code, see https://github.com/rillian/webvtt/issues/5
*** Need to break this up into a few major sections so people can write different parts (e.g., timestamps, cue options, text, header, etc.)
*** Build HTML from cue text, see https://github.com/rillian/webvtt/issues/6
*** Deal with UTF-8, see https://github.com/rillian/webvtt/issues/2
** Build system, test harness, Travis CI to drive our work
** Fuzz Testing, see https://github.com/rillian/webvtt/issues/8
** Test the WebKit parser using our test files, file/fix bugs
** Bug fixes for JS implementation, based on our tests
** More tests, fixes for existing tests, discussions with W3C to hand our tests over to spec working group
** Rework and Move http://kyle.barnhart.ca/2012/10/web-video-text-tracks-webvtt.html to proper home: MDN, WebPlatform docs, etc.
* How we'll work:
** Everyone needs to own something--no group work. You can help each other as much as you need/want, but you must own something in the process above.
** File bugs on github where appropriate, use the wiki for things that don't belong there.
** Be present in class, on irc, in bugs, in your blogging
** Help each other.
** Ask lots of questions, don't get stuck and stop. Get stuck and make some noise, keep at it, don't give up.
* '''TODO'''
** 0.2 is due Monday Oct 29th (note: I've moved this from Oct 18th).
** By 0.2 we need to have a working parser and be on to bug fixing
** Blog weekly about what you're working on, how it's going, what you're learning
** Be active on irc
** In class we'll be discussing code, asking people to show their progress, give demos, help one another, do reviews