From: Ferruh Yigit <ferruh.yigit@intel.com>
To: spp@dpdk.org
Subject: [spp] [PATCH] doc: add contribution guide
Date: Sat, 10 Dec 2016 05:05:01 +0000 [thread overview]
Message-ID: <20161210050501.19071-1-ferruh.yigit@intel.com> (raw)
Signed-off-by: Ferruh Yigit <ferruh.yigit@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@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@intel.com>
--
2.9.3
next reply other threads:[~2016-12-10 5:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-10 5:05 Ferruh Yigit [this message]
2016-12-10 5:07 ` Ferruh Yigit
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161210050501.19071-1-ferruh.yigit@intel.com \
--to=ferruh.yigit@intel.com \
--cc=spp@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).