From 1062a7f404288dc3d5773afec515a8cb0364675d Mon Sep 17 00:00:00 2001 From: Timothy Gu Date: Sat, 9 Nov 2013 15:36:36 -0800 Subject: [PATCH] doc: remove soc.txt The file was written in 2006, it was never updated nor really used as reference for SOC-like programs. Signed-off-by: Timothy Gu Signed-off-by: Stefano Sabatini --- doc/soc.txt | 24 ------------------------ 1 file changed, 24 deletions(-) delete mode 100644 doc/soc.txt diff --git a/doc/soc.txt b/doc/soc.txt deleted file mode 100644 index 2504dba553..0000000000 --- a/doc/soc.txt +++ /dev/null @@ -1,24 +0,0 @@ -Google Summer of Code and similar project guidelines - -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 ... - -This text is a collection of things to take care of for the next soc as -it's a little late for this year's soc (2006). - -The Goal: -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 -* conform to the development policy and patch submission guidelines -* must improve FFmpeg somehow (faster, smaller, "better", - more codecs supported, fewer bugs, cleaner, ...) - -for mentors and other developers to help students to reach that goal it is -essential that changes to their codebase are publicly visible, clean and -easy reviewable that again leads us to: -* use of a revision control system like git -* separation of cosmetic from non-cosmetic changes (this is almost entirely - ignored by mentors and students in soc 2006 which might lead to a surprise - when the code will be reviewed at the end before a possible inclusion in - FFmpeg, individual changes were generally not reviewable due to cosmetics). -* frequent commits, so that comments can be provided early