RepoMirrors
/
ffmpeg
mirror of https://git.ffmpeg.org/ffmpeg.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

editorial changes 

Originally committed as revision 5942 to svn://svn.ffmpeg.org/ffmpeg/trunk
This commit is contained in:
Diego Biurrun 2006-08-07 09:59:21 +00:00
parent 4f9807d8f8
commit a67a96a053
1 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
doc/soc.txt
View File

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