yading@10: Google Summer of Code and similar project guidelines
yading@10: 
yading@10: Summer of Code is a project by Google in which students are paid to implement
yading@10: some nice new features for various participating open source projects ...
yading@10: 
yading@10: This text is a collection of things to take care of for the next soc as
yading@10: it's a little late for this year's soc (2006).
yading@10: 
yading@10: The Goal:
yading@10: Our goal in respect to soc is and must be of course exactly one thing and
yading@10: that is to improve FFmpeg, to reach this goal, code must
yading@10: * conform to the development policy and patch submission guidelines
yading@10: * must improve FFmpeg somehow (faster, smaller, "better",
yading@10:   more codecs supported, fewer bugs, cleaner, ...)
yading@10: 
yading@10: for mentors and other developers to help students to reach that goal it is
yading@10: essential that changes to their codebase are publicly visible, clean and
yading@10: easy reviewable that again leads us to:
yading@10: * use of a revision control system like git
yading@10: * separation of cosmetic from non-cosmetic changes (this is almost entirely
yading@10:   ignored by mentors and students in soc 2006 which might lead to a surprise
yading@10:   when the code will be reviewed at the end before a possible inclusion in
yading@10:   FFmpeg, individual changes were generally not reviewable due to cosmetics).
yading@10: * frequent commits, so that comments can be provided early