[med-svn] [Debian Wiki] Update of "DebianMedQAWorkflow" by ThorstenAlteholz

[Debian Wiki]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Debian Wiki" for change notification.

The "DebianMedQAWorkflow" page has been changed by ThorstenAlteholz:
http://wiki.debian.org/DebianMedQAWorkflow?action=diff&rev1=1&rev2=2

- = Workflow for Debian Med packages =
- 
  Currently there are about 300 packages in the Debian Med svn repository, 
  but only 50 active uploaders. So in order to make live easier for 
  everybody, a uniform workflow should be established for maintainig packages.
  Thus all information will be at a familiar place and nobody
  has to waste time searching something.
  
+ <<TableOfContents>>
+ 
- == Tasks List ==
+ = Tasks List =
  
  All software that shall be part of Debian Med should have an entry in
- the Tasks List (http://debian-med.alioth.debian.org/tasks/). If you
+ the [[http://debian-med.alioth.debian.org/tasks/|Tasks List]]. If you
  stumble over new software, please add it to the task list. As a result
  a central point of information will be created. Anybody interested in
  Debian Med will see already processed packages or where there is work in
  progress.
  
- == SVN and git repositories ==
+ = SVN and git repositories =
  
  The Tasks List contains information about all packages, but the real work is
  done in either the SVN- or git-repository:
@@ -28, +28 @@

  This can be done with debian/changelog and a file called README.status
  
  
- === debian/changelog ===
+ == debian/changelog ==
  
  Creating a good package sometimes needs a fairly long time and incomplete work
  might be available in the repository. On the other side it is better
@@ -36, +36 @@

  In order to distinguish these cases debian/changlog might be used.
  In case of a generic maintainer line like:
   -- DMPT <debian-med-packaging at lists.alioth.debian.org> <date>
- no specific person takes care of it. You are welcome to improve the package
+ no specific person takes care of that package at the moment. You are welcome to improve the package as much as you want.
- as much as you want.
+ A maintainer line like:
+  -- Hubert von Schulzemeier <hvs at example.com> <date>
+ indicates that there is someone having interest in that package. Of course priorities might change and interest in that package vanishes. In that case the rules for an [[DebianMedQAWorkflow#Inactive_Maintainer|inactive maintainer]] become effective.
  
  
- === README.status ===
+ == README.status ==
  
  Normally each package should have a status of active, thus somebody takes
  care of bugs and uploads new versions.
  In case of unusual situations the status of a package might change. For example
  at a future time it might be maintained with git instead of svn, the package 
- has been 
- removed from Debian or it is just a first version and needs some more work.
+ has been removed from Debian or it is just a draft and needs some more work.
  In order to tell everybody about that situation, a file 'README.status' should
  be added to 'debian-med/trunk/packages/<package>/trunk/README.status'.
  It should be a yaml-file whose contents can be verified by:
-    kwalify -f README.status.schema.yaml README.status
+    kwalify -f [[http://debian-med.alteholz.de/support/README.status.schema.yaml|README.status.schema.yaml]] README.status
  or:
     perl -MYAML -e '$/=""; Load(<STDIN>)' < README.status
+ 
  Examples can be found in:
    * debian-med/trunk/packages/abyss/trunk/README.status
    * debian-med/trunk/packages/perlprimer/README.status
    * debian-med/trunk/packages/ball/trunk/README.status
  
  
- == New Packages ==
+ = New Packages =
  
  These are the steps to add new packages to the repository.
  
+  1. check whether there is an entry for that software in the [[http://debian-med.alioth.debian.org/tasks/|tasks list]] and maybe add one
-  1. check whether there is an entry for that software in the task list 
-  (http://debian-med.alioth.debian.org/tasks/) and maybe add one
   1. create directories in svn:
    * debian-med/trunk/packages/<package>/trunk
    * debian-med/trunk/packages/<package>/tags
    * if you like also add a 'branches' directory
+  1. add all files to debian-med/trunk/packages/<package>/trunk/debian/* and don't forget the file debian-med/trunk/packages/<package>/trunk/README.status
+  1. please create your files (especially debian/rules and debian/watch) in such a way that only the following commands are needed to build the package:
-  1. add all files to debian-med/trunk/packages/<package>/trunk/debian/*
-   and don't forget the file 
-   debian-med/trunk/packages/<package>/trunk/README.status
-  1. please create your files in such a way that only the following commands
-   are needed:
    1. ./debian/rules get-orig-source
    2. svn-buildpackage [--svn-ignore-new]
  
-  1. as long as the package is not ready for upload, set the following
+  1. as long as the package is not ready for upload, set the following informations:
-    values:
     * debian/changelog: set the maintainer line to either
        -- Debian Med <debian-med-packaging at lists.alioth.debian.org> <date>
       or your normal line
        -- Hubert von Schulzemeier <hvs at example.com> <date>
     * debian/changelog: distribution = UNRELEASED 
-  1. After everything is ready for upload, set the distribution and maintainer
+  1. After everything is ready for upload, set the distribution and maintainer accordingly and upload package.
-   accordingly and upload package.
   1. If you are not able to do the upload, set distribution = SPONSOR
  
  
- == Already Available Packages ==
+ = Already Available Packages =
  
- These are the steps to upload packages that are already available in the 
+ These are the steps to work on packages that are already available in the 
  archive.
  
+  1. check whether there is an entry for that software in the [[http://debian-med.alioth.debian.org/tasks/|tasks list]] and maybe add one
+  1. add your improvements to all files but bear in mind our [[http://debian-med.alioth.debian.org/docs/policy.html|policy]]
-  1. check whether there is an entry for that software in the task list 
-  (http://debian-med.alioth.debian.org/tasks/) and maybe add one
-  1. change files accordingly
-  1. as long as the package is not ready for upload, set the following
+  1. as long as the package is not ready for upload, set the following informations:
-   values:
     * debian/changelog: set the maintainer line to either
        -- Debian Med <debian-med-packaging at lists.alioth.debian.org> <date>
       or your normal line
        -- Hubert von Schulzemeier <hvs at example.com> <date>
     * debian/changelog: distribution = UNRELEASED 
-  1. After everything is ready for upload, set the distribution and maintainer
+  1. After everything is ready for upload, set the distribution and maintainer accordingly and upload package.
-   accordingly and upload package.
   1. If you are not able to do the upload, set distribution = SPONSOR
  
- === Inactive Maintainer ===
+ == Inactive Maintainer ==
  
- After a bug report or a new upstream version, a new entry in 
+ After bug reports or new upstream versions, a new entry in debian/changelog has
+ to be created. This is normally done by the last person who uploaded that package as indicated by the maintainer line of debian/changelog. In case the maintainer does not act on this issue for about a month (XXX length of period needs to be discussed), this new entry should be added by someone else. In doing so the maintainer line should be replaced by the generic maintainer line.
- debian/changelog has
- to be created. In case the maintainer does not act on this for about a month
- (XXX length of period needs to be discussed), this entry containing a 
- generic maintainer line should be added.