667
edits
Changes
→Weeks 8-10, Common Parser, Common Tests
*** 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(example of what fuzzing can uncover: https://bugzilla.mozilla.org/show_bug.cgi?id=803924#c7)
** Test the WebKit parser using our test files, file/fix bugs, see https://github.com/WebKit/webkit/tree/master/LayoutTests/media/track and https://github.com/WebKit/webkit/tree/master/LayoutTests/media/track/captions-webvtt for WebKit vtt tests
** Opera has just donated tests to the working group, too: http://w3c-test.org/html/tests/submission/Opera/media/track/webvtt/
* How we'll work:
** Everyone needs to own something. You can help each other as much as you need/want, but you must own something in the process above. Multiple parallel implementations of the C parser will be done in a sprint, and we'll [http://c2.com/cgi/wiki?PlanToThrowOneAway plan to throw one away]. See also Dave Mandelin's great post, https://blog.mozilla.org/dmandelin/2012/10/16/did-you-write-that-code-three-times/ (Dave is the owner of Mozilla's JS engine, SpiderMonkey).
** 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
** In class we'll be discussing code, asking people to show their progress, give demos, help one another, do reviews
** '''You need to come to class so we can co-ordinate'''
== Weeks 8-10, Common Parser, Common Tests ==
* We have a solid base for a parser now (multiple in fact), and can push forward
* 0.3 due Nov 15, 0.4 due Dec 7-14th
* Everyone needs to own something in 0.3--your 0.3 needs to be a code deliverable, no "learning" only outcomes
* Things we need done:
** Many things still to do on the parser: https://github.com/humphd/webvtt/tree/seneca#todo
** Autotools (autoconf, automake, libtool) style build system, book is [http://www.sourceware.org/autobook/ here] and guide is [http://www.freesoftwaremagazine.com/books/autotools_a_guide_to_autoconf_automake_libtool here].
** All current validation tests need to get converted to Unit Tests. What about WebKit/Opera tests, can we "steal" those too?
** Test Harness
*** JS bindings for C implementation: [https://github.com/rbranson/node-ffi node-ffi], tutorial is [https://github.com/rbranson/node-ffi/wiki/Node-FFI-Tutorial here]
*** Unit Test Framework: [https://github.com/caolan/nodeunit nodeunit] for unit testing, tutorial is [http://caolanmcmahon.com/posts/unit_testing_in_node_js/ here]
*** build system integration for `make check`
*** TravisCI integration
* No class Nov 8th, 12th. Use these as work periods for your 0.3 release, get on irc, help each other.
* If you're feeling lost or confused, make sure you do something about it. Don't wait, be proactive. Ask for help, try things, experiment.