Add guidelines for contribution to the 'lxc' project

From: Daniel Lezcano <dlezcano@fr.ibm.com>

CONTRIBUTING file give the guidelines to submit patches to this project.
MAINTAINERS contains the maintainer name and mailing list to send the patches.

Signed-off-by: Daniel Lezcano <dlezcano@fr.ibm.com>

1 files changed, 83 insertions, 0 deletions

diff --git a/CONTRIBUTING b/CONTRIBUTING
new file mode 100644
index 0000000..458c3e6
--- /dev/null
+++ b/CONTRIBUTING
@@ -0,0 +1,83 @@
+
+	Contributing to this project
+        ----------------------------
+
+
+This project accepts contributions. In order to contribute, you should
+pay attention to a few things:
+
+    1 - your code must follow the coding style rules
+    2 - the format of the submission must email patches
+    3 - your work must be signed
+
+
+Coding Style:
+-------------
+
+The coding style follows the Linux kernel coding style.
+
+The coding style is defined in the 'CodingStyle' file, available in
+the directory 'Documentation' of the Linux kernel source tree.
+
+It can be accessible online too:
+
+http://lxr.linux.no/linux+v2.6.27/Documentation/CodingStyle
+
+Submitting Modifications:
+-------------------------
+
+The contributions should be email patches. The guidelines are the same
+as the patch submission for the Linux kernel except for the DCO which
+is defined below. The guidelines are defined in the
+'SubmittingPatches' file, available in the directory 'Documentation'
+of the Linux kernel source tree.
+
+It can be accessible online too:
+
+http://lxr.linux.no/linux+v2.6.27/Documentation/SubmittingPatches
+
+Developer Certificate of Origin:
+--------------------------------
+
+To improve tracking of contributions to this project we will use a
+process modeled on the modified DCO 1.1 and use a "sign-off" procedure
+on patches that are being emailed around or contributed in any other
+way.
+
+The sign-off is a simple line at the end of the explanation for the
+patch, which certifies that you wrote it or otherwise have the right
+to pass it on as an open-source patch.  The rules are pretty simple:
+if you can certify the below:
+
+By making a contribution to this project, I certify that:
+
+(a) The contribution was created in whole or in part by me and I have
+    the right to submit it under the open source license indicated in
+    the file; or
+
+(b) The contribution is based upon previous work that, to the best of
+    my knowledge, is covered under an appropriate open source License
+    and I have the right under that license to submit that work with
+    modifications, whether created in whole or in part by me, under
+    the same open source license (unless I am permitted to submit
+    under a different license), as indicated in the file; or
+
+(c) The contribution was provided directly to me by some other person
+    who certified (a), (b) or (c) and I have not modified it.
+
+(d) The contribution is made free of any other party's intellectual
+    property claims or rights.
+
+(e) I understand and agree that this project and the contribution are
+    public and that a record of the contribution (including all
+    personal information I submit with it, including my sign-off) is
+    maintained indefinitely and may be redistributed consistent with
+    this project or the open source license(s) involved.
+
+
+then you just add a line saying
+
+	Signed-off-by: Random J Developer <random@developer.org>
+
+using your real name (sorry, no pseudonyms or anonymous
+contributions.)
\ No newline at end of file