Python 3 porting team
Contents
Usertags
Bugs related to this project have usertags applied to them to help track the progress of this task that crosses over many different packages (more about usertags).
user |
usertag |
what it means |
upstream supports py3k, but we don't ship the deb |
||
project needs help porting to py3k |
To apply the usertags to a new bug, add the following lines to the top of the bug report in the pseudo-headers section:
User: py3porters-devel@lists.alioth.debian.org Usertags: patchme-python3
To apply the usertags to existing bugs, use the bts command from the devscripts package:
bts user 'py3porters-devel@lists.alioth.debian.org' , usertags 999999 patchme-python3
The normal tags that the bug tracker uses can also be applied to the bugs. The particularly relevant ones and what they would mean in the context of the Python 3 porting project are:
patch |
a patch to add Python 3 support is attached to the bug |
help |
the porting looks particularly complicated and the maintainer would like assistance |
newcomer |
the porting looks particularly easy and would be suitable for a new contributor |
fixed-upstream |
the porting work is done in a new upstream release |
wontfix |
bug will not be fixed: hopefully we don't see any of these! |
Who is working on what?
Project |
Porter(s) name on ML / IRC |
Workspace |
Status |
Comment |
Depends on (only packages that are not yet py3 ready) |
|
Bernhard Janetzki, ierror |
ongoing |
|
||||
- |
planning |
will be ported from Pylons to either Flask or Django |
|
|||
Matt Singleton (xcolour), Justin Ryan (justizin) |
planning |
Porting to Flask |
|
|||
Bernhard Janetzki (tbd) |
tbd |
first contact to pkg maintainer via ML |
|
|
Resources for new folks
IRC Channels
These are on irc.oftc.net (not Freenode, sorry!)
Channel |
What help to ask for |
#debian-mentors |
Help building packages, testing debs, using the bug tracker, whatever |
#debian-python |
Help with the Debian Python ecosystem, and/or discuss Python 3 porting issues |
Debian Bug Tracking System
Debian's bug tracking system keeps up with all the bugs in the 46k binary packages (23k source packages) and handles both synchronous and asynchronous querying both within a package and across packages. For more information on the BTS, including how to manipulate the metadata of the bugs, see the BTS documentation.
The easiest way to report a bug (and include your porting patches) is with the reportbug tool -- that is the reportbug command from the reportbug package. If you don't have a working mailer daemon (MTA) on your machine, be sure to tell it that when you first run reportbug. If you've got a set of patches to send named 000?-* (say from git format-patch), then:
reportbug --source sourcepackagename --attach '000*'
and then answer the questions about severity (should be wishlist) and indicate that there is a patch. Alternatively, if you like long command lines you can do it all in one step (tab completion also works for these options):
reportbug --source sourcepackagename --attach '000*' --tag patch --severity wishlist
A couple of other useful bits of information:
For submitters: You will not be automatically subscribed to bugs that you report. Use bts subscribe 999999 to subscribe if you want to receive updates to your bugs.
For triage: The submitter won't necessarily be subscribed to their bugs so if you want to ask questions of the reporter, make sure to include them in the email along with the bug's own email address. You can do that by just emailing 999999-submitter@bugs.debian.org and 999999@bugs.debian.org.
- The 'reply' link on each page in the BTS works well to set a nice subject, set the correct addresses, give you quoted-context in the email and preserves threading.
Other mailing lists
Online resources
Python 3 porting Quick Reference Guide (with lots of help and links!)