FFmpeg Summer Of Code 2007
From MultimediaWiki
| Revision as of 12:40, 7 March 2007 Bcoudurier (Talk | contribs) (remove aac as it was done last year) ← Previous diff |
Revision as of 12:41, 7 March 2007 Bcoudurier (Talk | contribs) (add MXF muxer) Next diff → |
||
| Line 63: | Line 63: | ||
| === PAFF decoding for H.264/AVC === | === PAFF decoding for H.264/AVC === | ||
| + | |||
| + | |||
| + | === MXF Muxer === | ||
Revision as of 12:41, 7 March 2007
Google is sponsoring their third annual Summer of Code for the summer of 2007. This entails sponsoring students to work on assorted open source projects as well as sponsoring mentors in those same projects. Everyone wins.
FFmpeg was a Summer of Code participant in the summer of 2006 (here is the corresponding Wiki page) and hopes to be accepted again this year.
Mike Melanson (mike -at- multimedia.cx) is the administrator and main point of contact for matters relating to the FFmpeg Summer of Code.
Contents |
Current Status
- March 5-12, 2007: Application period for mentoring organizations.
- March 6, 2007: Mike Melanson submitted FFmpeg mentoring application.
Waiting for acceptance...
Project Proposals
Overview
Qualifications for a good Summer of Code proposal:
- discrete, well-defined, modular
- comprised of a series of measurable sub-goals
- based on open specs that are available free of charge
- based on complete specs
An example of a good proposal is the implementation of a decoder or demuxer for an as yet unsupported multimedia format, or an encoder or muxer for a format that can already be demuxed/decoded by FFmpeg.
An example of a less desirable proposal is one that's not as measurable, such as refactoring APIs. Bad proposals tend to be ones that would require touching a lot of core code.
To re-iterate:
- Localized/isolated code projects = good
- Global code refactoring = bad
