Difference between revisions of "Winter 2013 DPS911 and OSD700 Project Info"
(→Communications) |
|||
Line 1: | Line 1: | ||
− | |||
==Goals== | ==Goals== | ||
Line 26: | Line 25: | ||
* W3C | * W3C | ||
** http://www.w3.org/community/texttracks/ consider joining the public mailing list | ** http://www.w3.org/community/texttracks/ consider joining the public mailing list | ||
+ | |||
+ | ==Drivers== | ||
+ | |||
+ | Each student is expected to drive (i.e., lead, manage) one or more areas of the project. A project of this scale and scope doesn't get finished without people watching, and caring about, all its various aspects. An initial list of major areas (please add those not included): | ||
+ | |||
+ | * Build System, Build Automation, CI: ''name'' | ||
+ | * Issues, Bugs, Triage: ''name'' | ||
+ | * Documentation - External: ''name'' | ||
+ | * Documentation - Internal: ''name'' | ||
+ | * DOM Interface Implementation(s): ''name'' | ||
+ | * WEBVTT Parser Implementation: ''name'' | ||
+ | * WEBVTT Parser Integration within Gecko: ''name'' | ||
+ | * WEBVTT Spec Tests: ''name'' | ||
+ | * DOM Tests: ''name'' | ||
+ | * Spec Change, Conformance, etc. Management: ''name'' |
Revision as of 12:01, 7 January 2013
Contents
Goals
- Implement a stand-alone C implementation of http://dev.w3.org/html5/webvtt/
- Implement the track element (see bug 629350) in Firefox, such that it can use the aforementioned parser
- Complete this work in 2013, have it land in mozilla-central, ship in Firefox.
Repos
- Dev (Seneca): https://github.com/humphd/webvtt
- Upstream: https://github.com/mozilla/webvtt
For Seneca students, patches should land in the humphd repo first, from which the mozilla repo will get updated.
Communications
- Seneca
- webvtt-dev mailing list for students in DPS911 and OSD700 for course, project co-ordination
- Mozilla
- dev-media mailing list, for async contact with Mozilla media developers
- #media irc channel, for real-time contact with Mozilla media developers. Ralph is 'rillian' on irc.
- #introduction irc channel, for real-time help with general Mozilla development
- #seneca irc channel, for course/project back-channel communication
- W3C
- http://www.w3.org/community/texttracks/ consider joining the public mailing list
Drivers
Each student is expected to drive (i.e., lead, manage) one or more areas of the project. A project of this scale and scope doesn't get finished without people watching, and caring about, all its various aspects. An initial list of major areas (please add those not included):
- Build System, Build Automation, CI: name
- Issues, Bugs, Triage: name
- Documentation - External: name
- Documentation - Internal: name
- DOM Interface Implementation(s): name
- WEBVTT Parser Implementation: name
- WEBVTT Parser Integration within Gecko: name
- WEBVTT Spec Tests: name
- DOM Tests: name
- Spec Change, Conformance, etc. Management: name