667
edits
Changes
→Weeks 5-7, Toward a Parser
* What we need:
** Complete C implementation, done to spec. We'll have a few teams work on this in parallel, and then take the best of what we've learned from each to use in our final implementation:
*** Convert parsing rules into code, see https://github.com/rillian/webvtt/issues/5
*** [[WebVTT Parsing Sections|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
* 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. 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].
** 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