| 1 |
========================================
|
| 2 |
Python Modules Packaging Team - Policy
|
| 3 |
========================================
|
| 4 |
|
| 5 |
:Author: Gustavo Franco <stratus@debian.org>, Raphaël Hertzog <hertzog@debian.org>
|
| 6 |
:License: GNU GPL v2 or later
|
| 7 |
|
| 8 |
:Introduction:
|
| 9 |
Python Modules Packaging Team aims to improve the python modules situation
|
| 10 |
in Debian, by packaging available modules that may be useful and providing
|
| 11 |
a central location for packages maintained by a team, hence improving
|
| 12 |
responsiveness, integration and standardization.
|
| 13 |
|
| 14 |
PMPT or just python-modules is hosted at alioth.debian.org, the Debian
|
| 15 |
GForge installation. We currently have a SVN repository and a mailing list
|
| 16 |
whose email address can be used in the Maintainer field on co-maintained
|
| 17 |
packages.
|
| 18 |
|
| 19 |
For more information send a message to: debian-python@lists.debian.org
|
| 20 |
|
| 21 |
.. contents::
|
| 22 |
|
| 23 |
----------------
|
| 24 |
Joining the team
|
| 25 |
----------------
|
| 26 |
|
| 27 |
The team is open to any python-related package maintainer. To be added on
|
| 28 |
the team, please send your request on debian-python@lists.debian.org
|
| 29 |
indicate why you want to join the team: maintain your current packages
|
| 30 |
within the team, help maintain some specific packages, etc.
|
| 31 |
Don't forget to indicate your Alioth login !
|
| 32 |
|
| 33 |
Any Debian developer who wishes to integrate his packages in the team can do so
|
| 34 |
without requesting access (as the repository is writable by all DD). If one
|
| 35 |
wants to be more involved in the team, we still recommend requesting_ access
|
| 36 |
so that he appears in the public member list displayed on Alioth's project page.
|
| 37 |
|
| 38 |
The team accepts all contributors and is not restricted to Debian developers.
|
| 39 |
Several Debian developers of the team will gladly sponsor packages of non-DD
|
| 40 |
who are part of the team. Sponsorship requests can be sent on the main
|
| 41 |
discussion list or on #debian-python IRC channel (OFTC network).
|
| 42 |
|
| 43 |
All team members should of course follow the main discussion list:
|
| 44 |
debian-python@lists.debian.org
|
| 45 |
|
| 46 |
--------------
|
| 47 |
Maintainership
|
| 48 |
--------------
|
| 49 |
|
| 50 |
A package maintained within the team should have the name of the team either
|
| 51 |
in the Maintainer field or in the Uploaders field.
|
| 52 |
|
| 53 |
Maintainer: Debian Python Modules Team <python-modules-team@lists.alioth.debian.org>
|
| 54 |
|
| 55 |
This enables the team to have an overview of its packages on the DDPO_website_.
|
| 56 |
|
| 57 |
Thus if you bring some packages into the team, you can keep your name in
|
| 58 |
the Maintainer field. You will receive bug reports and handle your package
|
| 59 |
as usual except that other team members may help from time to time and/or
|
| 60 |
take over when you're too busy.
|
| 61 |
|
| 62 |
If you put the team in the Maintainer field, the package will be handled
|
| 63 |
completely by the team and every member is invited to work on any
|
| 64 |
outstanding issue.
|
| 65 |
|
| 66 |
Team members who have broad interest should subscribe to the mailing list
|
| 67 |
python-modules-team@lists.alioth.debian.org whereas members who are only
|
| 68 |
interested in some packages should use the Package Tracking System to
|
| 69 |
follow the packages.
|
| 70 |
|
| 71 |
---------------------
|
| 72 |
Subversion Procedures
|
| 73 |
---------------------
|
| 74 |
|
| 75 |
We're using a Subversion repository to maintain all the packages, then if you're not
|
| 76 |
already using it you will need to install svn-buildpackage.
|
| 77 |
|
| 78 |
*The repository layout:*
|
| 79 |
|
| 80 |
metainfo/
|
| 81 |
Ignore this directory (reserved for future usage).
|
| 82 |
|
| 83 |
packages/
|
| 84 |
The source packages are here.
|
| 85 |
|
| 86 |
package-foo
|
| 87 |
branches
|
| 88 |
If you or someone wants to play with a package possible breaking the trunk, give it a name and do it here.
|
| 89 |
tags
|
| 90 |
For each release, a tag. More information below.
|
| 91 |
trunk
|
| 92 |
That's where the main development happens, it should contain only the debian/ subdirectory part of a package.
|
| 93 |
|
| 94 |
www/
|
| 95 |
Documents and stuff that will be or are being published online in our website.
|
| 96 |
|
| 97 |
|
| 98 |
Hints:
|
| 99 |
======
|
| 100 |
* To keep your package tree clean as pointed out above, always ``svn-inject`` your packages using -o argument.
|
| 101 |
* If you svn-inject'ed a package without -o you should remove upstream sources and run ``svn propset mergeWithUpstream 1 debian/``.
|
| 102 |
* 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/.
|
| 103 |
* After upload, tag the latest revision running ``svn-buildpackage --svn-tag-only`` into 'package-foo' directory.
|
| 104 |
* You can revert the changelog changes after tagging, running ``svn revert debian/changelog``.
|
| 105 |
* If you're a pbuilder user, you can invoke it using ``svn-buildpackage --svn-builder pdebuild <args>``.
|
| 106 |
|
| 107 |
For more information on how to maintain packages within the repository with svn-buildpackage:
|
| 108 |
http://pkg-perl.alioth.debian.org/subversion.html
|
| 109 |
|
| 110 |
Please note that python-modules URLs are different than pkg-perl ones:
|
| 111 |
|
| 112 |
* svn+ssh://login@svn.debian.org/svn/python-modules/packages/
|
| 113 |
* svn://svn.debian.org/python-modules/packages/
|
| 114 |
* http://svn.debian.org/wsvn/python-modules/
|
| 115 |
|
| 116 |
Moreover, python-modules still use the default layout: don't pass ``-l 2`` to ``svn-inject``.
|
| 117 |
|
| 118 |
-----------------
|
| 119 |
Quality Assurance
|
| 120 |
-----------------
|
| 121 |
|
| 122 |
The goal of the team is to maintain all packages as best as possible.
|
| 123 |
Thus every member is encouraged to do general QA work on all the
|
| 124 |
packages: fix bugs, test packages, improve them to use the latest python
|
| 125 |
packaging tools, etc.
|
| 126 |
|
| 127 |
-------
|
| 128 |
License
|
| 129 |
-------
|
| 130 |
|
| 131 |
Copyright (c) 2005-2007 Python Modules Packaging Team. All rights reserved.
|
| 132 |
This document is free software; you may redistribute it and/or modify
|
| 133 |
it under the same terms as GNU GPL v2 or later.
|
| 134 |
|
| 135 |
.. _requesting: https://alioth.debian.org/project/request.php?group_id=30714
|
| 136 |
.. _DDPO_website: http://qa.debian.org/developer.php?login=python-modules-team@lists.alioth.debian.org
|
Parent Directory
| 
Revision Log