Revision 77 as of 2009-04-15 15:27:06

Clear message

(!) Next Python Bug Day: Saturday, April 25, 2009

Time: all day. Participants are most likely to be around between 9AM to 3PM according to their local time.

Join us for an effort at closing some Python bugs and patches. Get quick feedback on your patches and bugfixes, or learn how to submit and examine patches.

How are we doing? Try a Roundup search for bugs closed over the weekend.

Participating Online

Participants will meet in the #python-dev IRC channel on irc.freenode.net. To learn more about IRC and to find links to IRC clients for various platforms, see http://www.irchelp.org.

Finding Bugs

Using the bug tracker, you can perform various searches to look for candidate issues:

There are various things MissingFromDocumentation; these tasks mostly require writing and editing, not programming.

Procedures

The goal of the bug day is to process bug reports in the Python bug tracker, trying to fix and close issues. Bugs should be processed in the fashion described by PEP 0003, "Guidelines for Handling Bug Reports".

At PyCon 2008, Brett Cannon provided a slideshow educating new contributors to the Python code.

What to do:

For later committing

Questions?

If you have questions about the bug day, please add them to this section.

Previous bug days

Date

Accomplishments

2004-06-05

44 bugs

2004-07-10

18 bugs, 21 patches

2004-08-07

19 bugs, 12 patches

2004-11-07

12 bugs, 10 patches

2005-06-25

10 bugs, 7 patches

2005-12-04

11 bugs+patches

2006-03-31

19 bugs, 9 patches

2008-01-19

37 bugs+patches

2008-02-23

48 bugs+patches

2008-05-10 & 11

34 bugs+patches

Bug days for other projects

The Zope bug day has a good description of what to do, though the details of the bug tracker are specific to the Zope project.

The GNOME community holds regular Bug Days; the procedures are described in their FAQ.

Preparatory Tasks

Unable to edit the page? See the FrontPage for instructions.