The team is open to any python-related package maintainer. To be added to the
team, please request to join on Alioth (you need to create alioth's account
first if you don't have one yet). Please indicate why you want to join the
team: maintain your current packages within the team, help maintain some
specific packages, etc.
Any Python Modules Packaging Team member who wishes to integrate his packages
in the team can do so without requesting access (as the repository is writable
by all PMPT members and thus 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. Debian developers: please note
if you're willing to act as a sponsor, you'll get a "sponsor" role on Alioth.
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
who are part of the team. Sponsorship requests can be sent on the main
discussion list or on #debian-python IRC channel (OFCT network).
All team members should of course follow the main discussion list:
debian-python@lists.debian.org (DP_listinfo)
A package maintained within the team should have the name of the team either in
the Maintainer field or in the Uploaders field.
Maintainer: Python Applications Packaging Team <python-apps-team@lists.alioth.debian.org>
This enables the team to have an overview of its packages on the DDPO_website.
Thus if you bring some packages into the team, you can keep your name in the
Maintainer field. You will receive bug reports and handle your package as usual
except that other team members may help from time to time and/or take over when
you're too busy.
If you put the team in the Maintainer field, the package will be handled
completely by the team and every member is invited to work on any outstanding
issue.
Team members who have broad interest should subscribe to the mailing list
python-apps-team@lists.alioth.debian.org whereas members who are only
interested in some packages should use the Package Tracking System to follow
the packages.
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.
- 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.
- To keep your package tree clean as pointed out above, always svn-inject
your packages using -o argument.
- If you svn-inject'ed a package without -o you should remove upstream sources
and run 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
svn-buildpackage --svn-tag-only into 'package-foo' directory.
- You can revert the changelog changes after tagging, running
svn revert debian/changelog.
- If you're a pbuilder user, you can invoke it using
svn-buildpackage --svn-builder pdebuild <args>.
- Do not forget to add Vcs-Svn and Scs-Browser to your debian/control file
svn-inject -o pypar2_1.4-1.dsc svn+ssh://login@svn.debian.org/svn/python-apps/packages/
The goal of the team is to maintain all packages as best as possible. Thus
every member is encouraged to do general QA work on all the packages: fix bugs,
test packages, improve them to use the latest Python packaging tools, etc.