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