[spp] [PATCH] doc: add contribution guide

[Ferruh Yigit]

Signed-off-by: Ferruh Yigit <ferruh.yigit at intel.com>
---
 CONTRIBUTING.txt | 51 +++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 51 insertions(+)
 create mode 100644 CONTRIBUTING.txt

diff --git a/CONTRIBUTING.txt b/CONTRIBUTING.txt
new file mode 100644
index 0000000..01e1b65
--- /dev/null
+++ b/CONTRIBUTING.txt
@@ -0,0 +1,51 @@
+Contributors Guide
+==================
+
+This document outlines how to contribute code to the SPP project.
+
+Getting the code
+----------------
+
+The SPP code can be cloned from the repository on dpdk.org as follows:
+
+    git clone git://dpdk.org/apps/spp
+    git clone http://dpdk.org/git/apps/spp
+
+The code can be browsed at http://dpdk.org/browse/apps/spp/
+
+Submitting Patches
+------------------
+
+Contributions to SPP should be submitted as git formatted patches to the
+SPP mailing list: spp at dpdk.org
+
+Note you must first register for the mailing list at:
+http://dpdk.org/ml/listinfo/spp
+
+The commit message must end with a "Signed-off-by:" line which is added using:
+
+    git commit --signoff # or -s
+
+The purpose of the signoff is explained in the Linux kernel guidelines
+Developer's Certificate of Origin:
+http://www.kernel.org/doc/Documentation/SubmittingPatches
+
+Note:
+    All developers must ensure that they have read, understood and complied
+    with the Developer's Certificate of Origin section of the documentation
+    prior to applying the signoff and submitting a patch.
+
+The DPDK Code Contributors guidelines contain information that is
+useful for submitting patches to SPP:
+http://dpdk.org/doc/guides/contributing/index.html
+
+Coding Guidelines
+-----------------
+
+* C code should follow the DPDK coding standards.
+* Python code should follow PEP8.
+
+Maintainer
+----------
+
+The SPP maintainer is: Ferruh Yigit <ferruh.yigit at intel.com>
-- 
2.9.3