Differences between revisions 1 and 26 (spanning 25 versions)
Revision 1 as of 2010-01-23 10:23:41
Size: 3558
Editor: SandroTosi
Comment:
Revision 26 as of 2020-11-19 16:54:45
Size: 3289
Editor: ?JochenSprickerhof
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= How To Join DPMT & PAPT Teams = = How To Join Python Team =
Line 3: Line 3:
This document describes the steps needed to join [[http://wiki.debian.org/Teams/PythonModulesTeam|Python Modules (DPMT)]] and/or [[http://wiki.debian.org/Teams/PythonAppsPackagingTeam|Python Applications (PAPT)]] teams This document describes the steps needed to join [[Teams/PythonTeam]]. It assumes that you already read [[https://www.debian.org/doc/packaging-manuals/python-policy/index.html|Debian Python Policy]] and agree with it.

== How to Request to Join the Team ==

This is described in [[https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst#joining-the-team]]. That page says:

To be added on the team, please send your request on ``debian-python@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 Salsa login!

If you don't already have an Salsa account, please register on [[https://signup.salsa.debian.org/|Salsa's signup page]].

In your email please state that you have read [[https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst]] and that you accept it.

Your request will be approved once an admin examines it; you'll receive notification when it happens.
Line 12: Line 24:
== Request Access to Alioth Teams ==

If you don't have one already, register an account on [[http://alioth.debian.org/|Alioth]]. Then go to [[https://alioth.debian.org/projects/python-modules/|DPMT]] and/or [[https://alioth.debian.org/projects/python-apps/|PAPT]] projects page and click on the "Request to join" link at the bottom/right of the page.

It's also nice if you can describe your request of joining, in particular what packages you want to maintain with us (is already in the team, new or such) and other things that may describe your interest in modules/apps stuff. You can also present yourself (after having requested to join) sending an email to the mailing list mentioned above, so the whole team knows you're coming.

Your request will be approved once an admin examines it; you'll receive notification when it happens.
Line 22: Line 26:
There is already a guide about basic tasks with packages in DPMT/PAPT teams [[http://wiki.debian.org/PAPT_Howto|here]] (just replace `python-apps` with `python-modules` if you're working with DPMT instead of PAPT). There is already a guide about basic tasks with packages in the Python team [[Python/GitPackaging|here]].
Line 24: Line 28:
Some remarks:

 * use `-o` option to `svn-inject`, this will avoid storing the upstream source code in the repo, but only the Debian packaging;
 * check that `.diff.gz` doesn't contain any direct changes to the upstream files (they will end up with some ''mess'' on the repo); if you need to change them, use a patch system;
 * (as for the time being) it seems `svn-inject` still doesn't support format 3.0, so you have to prepare a 1.0 format source package, inject it in the repo, then re-convert it to 3.0;
Line 32: Line 31:
There is a ''unwritten'' policy about the usage of `Maintainer` and `Uploaders` field, you might be interested to know about:
Usage of `Maintainer` and `Uploaders` field is defined in [[https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst#L47|Maintainership]] section in policy document.
Line 39: Line 39:
If the team is in `Maintainer` field, remember to subscribe appropriate [[http://lists.alioth.debian.org/mailman/listinfo/python-apps-team|mailing]] [[http://lists.alioth.debian.org/mailman/listinfo/python-modules-team|list]] or at least `bts` and `contact` keywords on [[http://packages.qa.debian.org/cgi-bin/pts.cgi?what=advanced&package=source_package_name&email=your@email.com|this]] page.
Line 41: Line 43:
There are several ways you can as for a review and (hopefully) for a sponsorship of your package: There are several ways you can ask for a review and (hopefully) for a sponsorship of your package:
Line 43: Line 45:
 * mail the debian-python@l.d.o mailing list RFS the package
 * use the TODO page for [[http://wiki.debian.org/Teams/PythonModulesTeam/TODO|DPMT]] and [[http://wiki.debian.org/Teams/PythonAppsPackagingTeam/TODO|PAPT]]
 * add you package to the topic of #debian-python IRC channel
 * bother someone on the same IRC channel :)
 * add your package to the topic of #debian-python IRC channel
 * mail the debian-python@lists.debian.org mailing list RFS the package
 * use the [[Teams/PythonTeam/TODO|TODO]] page.
 * bother someone on #debian-python IRC channel :)

How To Join Python Team

This document describes the steps needed to join Teams/PythonTeam. It assumes that you already read Debian Python Policy and agree with it.

How to Request to Join the Team

This is described in https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst#joining-the-team. That page says:

To be added on the team, please send your request on debian-python@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 Salsa login!

If you don't already have an Salsa account, please register on Salsa's signup page.

In your email please state that you have read https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst and that you accept it.

Your request will be approved once an admin examines it; you'll receive notification when it happens.

How To Contact Us

You can use this places to ask us questions about packaging (not programming problems, please, for that uses #python on Freenode network) of Python modules and/or applications.

Work With The Packages

There is already a guide about basic tasks with packages in the Python team here.

Policy About Maintainer and Uploaders Fields

Usage of Maintainer and Uploaders field is defined in Maintainership section in policy document.

  • If the team is in the Maintainer field (and you are in Uploaders field) then every member of the team can apply changes to the package and upload it freely;

  • if you are in the Maintainer field (and the team is in Uploaders field) then every member of the team can apply changes to the package but any upload should be acknowledged by you (there are some exceptions, like uploads to fix RC bugs, but are infrequent).

As a general rule of thumb, just set Maintainer to the team; there might be some exceptions, like in situations where the package is so complex that a check from a knowledgeable person is welcome before an upload but they are very rare.

If the team is in Maintainer field, remember to subscribe appropriate mailing list or at least bts and contact keywords on this page.

Request For Sponsorship

There are several ways you can ask for a review and (hopefully) for a sponsorship of your package:

  • add your package to the topic of #debian-python IRC channel
  • mail the debian-python@lists.debian.org mailing list RFS the package

  • use the TODO page.

  • bother someone on #debian-python IRC channel :)