[Python-modules-commits] [python-modules] 01/09: * Updated policy to describe the use of git. * Remove all mention of subversion/svn. * Add myself to Author list. * PMPT -> DPMT

Barry Warsaw barry at moszumanska.debian.org
Mon Nov 2 22:27:35 UTC 2015 

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

barry pushed a commit to branch git-policy
in repository python-modules.

commit 46fc19cb3f000e1f20d3414a979f1e61992017ab
Author: Barry Warsaw <barry at python.org>
Date:   Mon Oct 19 12:44:54 2015 -0400

    * Updated policy to describe the use of git.
    * Remove all mention of subversion/svn.
    * Add myself to Author list.
    * PMPT -> DPMT
---
 policy.rst | 98 ++++++++++++++++++++------------------------------------------
 1 file changed, 31 insertions(+), 67 deletions(-)

diff --git a/policy.rst b/policy.rst
index c09f03a..1d121af 100644
--- a/policy.rst
+++ b/policy.rst
@@ -2,19 +2,18 @@
  Python Modules Packaging Team - Policy
 ========================================
 
-:Author: Gustavo Franco <stratus at debian.org>, Raphaël Hertzog <hertzog at debian.org>
+:Author: Gustavo Franco <stratus at debian.org>, Raphaël Hertzog <hertzog at debian.org>, Barry Warsaw <barry at debian.org>
 :License: GNU GPL v2 or later
 
 :Introduction:
-  Python Modules Packaging Team aims to improve the python modules situation
-  in Debian, by packaging available modules that may be useful and providing
-  a central location for packages maintained by a team, hence improving
-  responsiveness, integration and standardization.
+  The Debian Python Modules Team (DPMT) aims to improve the Python modules
+  situation in Debian, by packaging available modules that may be useful and
+  providing a central location for packages maintained by a team, hence
+  improving responsiveness, integration, and standardization.
 
-  PMPT or just python-modules is hosted at alioth.debian.org, the Debian
-  GForge installation. We currently have a SVN repository and a mailing list
-  whose email address can be used in the Maintainer field on co-maintained
-  packages.
+  The DPMT is hosted at alioth.debian.org, the Debian GForge installation. We
+  currently have a git repository and a mailing list whose email address can
+  be used in the ``Maintainer`` field on co-maintained packages.
 
   For more information send a message to: debian-python at lists.debian.org
 
@@ -24,16 +23,17 @@
 Joining the team
 ----------------
 
-The team is open to any python-related package maintainer. To be added on
+The team is open to any Python-related package maintainer. To be added on
 the team, please send your request on debian-python at lists.debian.org
 indicate why you want to join the team: maintain your current packages
 within the team, help maintain some specific packages, etc.
-Don't forget to indicate your Alioth login !
+Don't forget to indicate your Alioth login!
 
-Any Debian developer who wishes to integrate his packages in the team can do so
-without requesting access (as the repository is writable by all DD). If one
+Any Debian developer who wishes to integrate his packages in the team can do
+so without requesting access (as the repository is writable by all DD). If one
 wants to be more involved in the team, we still recommend requesting_ access
-so that he appears in the public member list displayed on Alioth's project page.
+so that they appear in the public member list displayed on Alioth's project
+page.
 
 The team accepts all contributors and is not restricted to Debian developers.
 Several Debian developers of the team will gladly sponsor packages of non-DD
@@ -48,71 +48,35 @@ Maintainership
 --------------
 
 A package maintained within the team should have the name of the team either
-in the Maintainer field or in the Uploaders field.
+in the ``Maintainer`` field or in the ``Uploaders`` field.
 
 Maintainer: Debian Python Modules Team <python-modules-team at lists.alioth.debian.org>
 
 This enables the team to have an overview of its packages on the DDPO_website_.
 
-* Team in Maintainers is a strong statement that fully collaborative
-  maintenance is preferred. Anyone can commit to the vcs and upload as
-  needed. A courtesy email to Uploaders can be nice but not required.
+* Team in ``Maintainers`` is a strong statement that fully collaborative
+  maintenance is preferred. Anyone can commit to the git repository and upload
+  as needed. A courtesy email to ``Uploaders`` can be nice but not required.
 
-* Team in Uploaders is a weak statement of collaboration. Help in maintaining
-  the package is appreciated, commits to vcs are freely welcomed, but before
-  uploading, please contact the Maintainer for the green light.
+* Team in ``Uploaders`` is a weak statement of collaboration. Help in
+  maintaining the package is appreciated, commits to the git repository are
+  freely welcomed, but before uploading, please contact the ``Maintainer`` for
+  the green light.
 
 Team members who have broad interest should subscribe to the mailing list
 python-modules-team at lists.alioth.debian.org whereas members who are only
 interested in some packages should use the Package Tracking System to
 follow the packages.
 
----------------------
-Subversion Procedures
----------------------
-
-We're using a Subversion repository to maintain all the packages, then if you're not
-already using it you will need to install svn-buildpackage.
-
-*The repository layout:*
-
-metainfo/
-  Ignore this directory (reserved for future usage).
-
-packages/
-  The source packages are here.
-
-  package-foo
-      branches
-         If you or someone wants to play with a package possible breaking the trunk, give it a name and do it here.
-      tags
-         For each release, a tag. More information below.
-      trunk
-         That's where the main development happens, it should contain only the debian/ subdirectory part of a package.
-
-www/
-  Documents and stuff that will be or are being published online in our website.
-
-
-Hints:
-======
-* To keep your package tree clean as pointed out above, always :code:`svn-inject` your packages using :code:`-o` argument.
-* If you svn-inject'ed a package without :code:`-o`, you should remove upstream sources and run :code:`svn propset mergeWithUpstream 1 debian/`.
-* Since you are keeping only debian/ directory in the svn tree, you need to put the 'package-foo'_'version'.orig.tar.gz in tarballs/ a directory above the package, and svn-buildpackage will do the merge for you. More information about this in the svn-buildpackage howto at /usr/share/doc/svn-buildpackage/.
-* After upload, tag the latest revision running :code:`svn-buildpackage --svn-tag-only` into 'package-foo' directory.
-* You can revert the changelog changes after tagging, running :code:`svn revert debian/changelog`.
-* If you're a pbuilder user, you can invoke it using :code:`svn-buildpackage --svn-builder pdebuild <args>`.
-
-For more information on how to maintain packages within the repository with svn-buildpackage:
-`http://pkg-perl.alioth.debian.org/subversion.html <https://web.archive.org/web/20141027193341/http://pkg-perl.alioth.debian.org/subversion.html>`_
-
-Please note that python-modules URLs are different than pkg-perl ones:
-
-* svn+ssh://login@svn.debian.org/svn/python-modules/packages/
-* svn://svn.debian.org/python-modules/packages/
-* http://anonscm.debian.org/viewvc/python-modules/
+--------------
+Git Procedures
+--------------
 
-Moreover, python-modules still use the default layout: don't pass :code:`-l 2` to :code:`svn-inject`.
+As of October 9, 2015, the DPMT uses git as the version control system for all
+packages, and git-dpm as the patch management regime.  Details of the
+procedures, standards for branches and tags, and common workflows are
+maintained on the `Debian wiki <https://wiki.debian.org/Python/GitPackaging>`_
+page.
 
 -----------------
 Quality Assurance
@@ -127,7 +91,7 @@ packaging tools, etc.
 License
 -------
 
-Copyright (c) 2005-2015 Python Modules Packaging Team. All rights reserved.
+Copyright (c) 2005-2015 Debian Python Modules Team. All rights reserved.
 This document is free software; you may redistribute it and/or modify
 it under the same terms as GNU GPL v2 or later.
 

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

More information about the Python-modules-commits mailing list