[Piuparts-commits] [piuparts] 01/01: TODO: explain in CONTRIBUTING how to contribute non-code. cleaned TODO further.

[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 db3b7cee413ffa9cc9a6d9fdb4bdbde3fbfdcb78
Author: Holger Levsen <holger at layer-acht.org>
Date:   Tue May 20 01:46:08 2014 +0200

    TODO: explain in CONTRIBUTING how to contribute non-code. cleaned TODO further.
---
 CONTRIBUTING |  8 ++++++--
 TODO         | 36 +++++++++++++++++++++---------------
 2 files changed, 27 insertions(+), 17 deletions(-)

diff --git a/CONTRIBUTING b/CONTRIBUTING
index 9395f1e..f3c7d84 100644
--- a/CONTRIBUTING
+++ b/CONTRIBUTING
@@ -1,5 +1,5 @@
-Contributing to this project
-----------------------------
+Contributing code 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).
@@ -24,3 +24,7 @@ One possible workflow:
   reportbug piuparts
   <describe the issue, attach the patch>
 
+Contributing bugs to other projects
+-----------------------------------
+Another very useful type of contributions are filing bug reports based
+on piuparts runs. This is described in FIXME and will soon be linked here.
diff --git a/TODO b/TODO
index 48177c8..d3f796b 100644
--- a/TODO
+++ b/TODO
@@ -7,26 +7,31 @@ wishlist!
 
 for 0.5x:
 
-- make piuparts-master + piuparts-slave packages work with documented steps:
-  - document how to setup '~piupartsm/.ssh/authorized_keys'
-    + remove the current method...
-
 - Documentation related:
-  - examples are duplicated in piuparts.1.txt and README.txt - only keep one copy.
-  - link wiki:piuparts/UseCases||UsageTips in README_1st (after we agreed on a name)
+  - make piuparts-master + piuparts-slave packages work with documented steps,
+    that is document how+where to deploy '~piupartsm/.ssh/authorized_keys'
+  - examples are duplicated in piuparts.1.txt and README.txt - only keep one
+    copy.
+  - link wiki:piuparts/UseCases||UsageTips in README_1st (after we agreed on
+    a name)
+  - fix the FIXME in CONTRIBUTING
+  - cleanup README_pejacevic.txt from info not related to pejacevic (eg. how
+    to file bugs, how to run the slaves, etc)
 
 - more stats and graphs:
-  - packages processed per day and section
-    - master writes submissions.txt per section since 0.45
-  - generate simple diagrams: number of source + binary package in all single distros:
-    squeeze, wheezy, jessie, sid.
+  - packages processed per day and section, master writes submissions.txt
+    since 0.45 for all sections.
+  - generate simple diagrams: number of source + binary packages in all single
+    distros: lenny, squeeze, wheezy, jessie, sid.
   - move counts.txt from htdocs to master.
-  - generate https://piuparts.debian.org/stable/states.png + testing.png from
-    existing data
 
 
 for 0.6x:
 
+- more stats and graphs:
+  - generate https://piuparts.debian.org/stable/states.png + testing.png from
+    existing data
+
 - piuparts.conf.pejacevic: maybe use mirror via nfs (faster)
 
 - also test packages from security.d.o and squeeze-lts
@@ -37,8 +42,8 @@ for 0.6x:
   too, to avoid hardcoding a specific mirror in distros.conf
 
 - really support multiple architectures:
-  - piuparts-report should have a list of available arch and list packages only
-    available on untested archs in a new state
+  - piuparts-report should have a list of available arch and list packages
+    only available on untested archs in a new state
     "(depends-)not-available-on-tested-archs"
   - master should (per default) only schedule packages which are not available
     on the master arch to slaves of different archs ->
@@ -61,7 +66,8 @@ for 0.6x:
   http://andialbrecht.wordpress.com/2009/03/17/creating-a-man-page-with-distutils-and-optparse/
   - though this seems pretty complicated... maybe rather grep for
     parser.add_option and help= in piuparts.py ?!
-    - requires merging all the additional infomation in piuparts.1.txt into piuarts.py
+    - requires merging all the additional infomation in piuparts.1.txt into
+      piuarts.py
     - parsing piuparts --help output may be easier than parsing piuparts.py
 
 - check the logfiles (especially pass/) for

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