blob: 54e116c8cd12f10613a3c694c1b85c6100f770c0 [file] [log] [blame]
Robert Hak40bafc52002-08-21 10:19:23 +00001$Id$
2
Robert Hak465ba3e2002-08-21 10:29:58 +00003 __________ __ ___.
4 Open \______ \ ____ ____ | | _\_ |__ _______ ___
5 Source | _// _ \_/ ___\| |/ /| __ \ / _ \ \/ /
6 Jukebox | | ( <_> ) \___| < | \_\ ( <_> > < <
7 Firmware |____|_ /\____/ \___ >__|_ \|___ /\____/__/\_ \
8 \/ \/ \/ \/ \/
9 Contribution Policies
10
11
Robert Hak40bafc52002-08-21 10:19:23 +000012In order for the project to run as smoothly as possible, it's best if all
13contributors adhere to a few simple conventions:
14
15Language
16--------
17Write all code in C. Sometimes assembly is faster, but C is always more
18readable and maintainable.
19
20Language features
21-----------------
22Write normal C code. Don't redefine the language. No new types (structs are
Björn Stenberg83b8ede2004-11-11 09:40:48 +000023structs, not typedefs), no C++isms or Javaisms.
Robert Hak40bafc52002-08-21 10:19:23 +000024
25Names
26-----
27Variables and function names should be all lower case.
28Preprocessor symbols should be all uppercase.
29
Daniel Stenberg071898e2003-03-04 15:06:53 +000030Comments
31--------
32We only use plain old /* C standard comments */.
33
Robert Hak40bafc52002-08-21 10:19:23 +000034Style
35-----
36When changing code, follow the code style of the file you are editing.
37
38When writing new files, you may use the brace placement style of your choice.
39
40Always indent your code with four spaces. Don't use TAB characters, as that
41will mess up code display in CVS, printing, and a zillion other places.
42
43Keep lines below 80 columns length. Use whitespace and newlines to make the
44code easy to browse/read.
45
46Text format
47-----------
48Use "unix style" line feeds: "LF" only. Do not use "CR+LF".
49
Daniel Stenberg95cde0b2005-10-28 10:44:50 +000050Use ISO-8859-1 character set, but try to refrain from using any non-ascii
51letters as they will only appear weird in some camps no matter what.
52
Robert Hak40bafc52002-08-21 10:19:23 +000053Patches
54-------
55Create a patch using 'cvs diff -ub'.
56Trim your patches so they only contain relevant changes.
Robert Hak40bafc52002-08-21 10:19:23 +000057
Daniel Stenberge17abad2003-07-24 11:46:51 +000058Submit your patch to the project via Sourceforge's patch tracker:
59http://sourceforge.net/tracker/?group_id=44306&atid=439120