[Piuparts-commits] [piuparts] 01/01: Clarify how to contribute

[Holger Levsen]

This is an automated email from the git hooks/post-receive script.

holger pushed a commit to branch develop
in repository piuparts.

commit b4bc68b6e4213307c40031f20fa14a883fde38cb
Author: Vince McIntyre <mci156 at shambles.windy>
Date:   Mon Sep 2 20:58:38 2013 +1000

    Clarify how to contribute
---
 CONTRIBUTING |   26 ++++++++++++++++++++++++++
 1 file changed, 26 insertions(+)

diff --git a/CONTRIBUTING b/CONTRIBUTING
new file mode 100644
index 0000000..9395f1e
--- /dev/null
+++ b/CONTRIBUTING
@@ -0,0 +1,26 @@
+Contributing to this project
+----------------------------
+
+It's helpful to track fixes or new features via wishlist bugs against the
+'piuparts' package, eg with the 'reportbug' tool ('devscripts' package).
+The BTS will ensure the developers' mailing list
+   piuparts-devel at lists.alioth.debian.org
+is notified.
+
+Patches can be submitted by mail (git format-patch, see below)
+or as requests to pull from a publicly-visible git repository.
+In either case, please make a topic branch based on the 'develop' branch.
+
+You can send patches or requests to the development list,
+or to the tracking bug: <bugnumber>@bugs.debian.org.
+
+One possible workflow:
+  git clone git://anonscm.debian.org/piuparts/piuparts.git
+  git checkout origin/develop -b <topicname>
+  <edits>
+  git commit -a
+  git format-patch -M origin/develop
+
+  reportbug piuparts
+  <describe the issue, attach the patch>
+

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/piuparts/piuparts.git