]>
Commit | Line | Data |
---|---|---|
752c0602 | 1 | |
836676ca | 2 | Contributing to this project |
752c0602 | 3 | ---------------------------- |
4 | ||
5 | ||
6 | This project accepts contributions. In order to contribute, you should | |
7 | pay attention to a few things: | |
8 | ||
9 | 1 - your code must follow the coding style rules | |
683c720b | 10 | 2 - the format of the submission must be email patches |
752c0602 | 11 | 3 - your work must be signed |
12 | ||
13 | ||
14 | Coding Style: | |
15 | ------------- | |
16 | ||
17 | The coding style follows the Linux kernel coding style. | |
18 | ||
19 | The coding style is defined in the 'CodingStyle' file, available in | |
20 | the directory 'Documentation' of the Linux kernel source tree. | |
21 | ||
e81c7f2c | 22 | It can be accessed online too: |
752c0602 | 23 | |
24 | http://lxr.linux.no/linux+v2.6.27/Documentation/CodingStyle | |
25 | ||
26 | Submitting Modifications: | |
27 | ------------------------- | |
28 | ||
29 | The contributions should be email patches. The guidelines are the same | |
30 | as the patch submission for the Linux kernel except for the DCO which | |
31 | is defined below. The guidelines are defined in the | |
32 | 'SubmittingPatches' file, available in the directory 'Documentation' | |
33 | of the Linux kernel source tree. | |
34 | ||
e81c7f2c | 35 | It can be accessed online too: |
752c0602 | 36 | |
37 | http://lxr.linux.no/linux+v2.6.27/Documentation/SubmittingPatches | |
38 | ||
36193502 GT |
39 | You can submit your patches to the lxc-devel@lists.sourceforge.net mailing |
40 | list. Use https://lists.sourceforge.net/lists/listinfo/lxc-devel to subscribe | |
41 | to the list. | |
42 | ||
752c0602 | 43 | Developer Certificate of Origin: |
44 | -------------------------------- | |
45 | ||
46 | To improve tracking of contributions to this project we will use a | |
47 | process modeled on the modified DCO 1.1 and use a "sign-off" procedure | |
48 | on patches that are being emailed around or contributed in any other | |
49 | way. | |
50 | ||
51 | The sign-off is a simple line at the end of the explanation for the | |
52 | patch, which certifies that you wrote it or otherwise have the right | |
53 | to pass it on as an open-source patch. The rules are pretty simple: | |
54 | if you can certify the below: | |
55 | ||
56 | By making a contribution to this project, I certify that: | |
57 | ||
58 | (a) The contribution was created in whole or in part by me and I have | |
59 | the right to submit it under the open source license indicated in | |
60 | the file; or | |
61 | ||
62 | (b) The contribution is based upon previous work that, to the best of | |
63 | my knowledge, is covered under an appropriate open source License | |
64 | and I have the right under that license to submit that work with | |
65 | modifications, whether created in whole or in part by me, under | |
66 | the same open source license (unless I am permitted to submit | |
67 | under a different license), as indicated in the file; or | |
68 | ||
69 | (c) The contribution was provided directly to me by some other person | |
70 | who certified (a), (b) or (c) and I have not modified it. | |
71 | ||
72 | (d) The contribution is made free of any other party's intellectual | |
73 | property claims or rights. | |
74 | ||
75 | (e) I understand and agree that this project and the contribution are | |
76 | public and that a record of the contribution (including all | |
77 | personal information I submit with it, including my sign-off) is | |
78 | maintained indefinitely and may be redistributed consistent with | |
79 | this project or the open source license(s) involved. | |
80 | ||
81 | ||
82 | then you just add a line saying | |
83 | ||
836676ca | 84 | Signed-off-by: Random J Developer <random@developer.org> |
752c0602 | 85 | |
836676ca | 86 | using your real name (sorry, no pseudonyms or anonymous contributions.) |