Revision 69 as of 2008-05-10 12:01:46

Clear message

Global Python Sprint Weekend: Saturday, May 10-11, 2008

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 [http://bugs.python.org/issue?%40search_text=&title=&%40columns=title&id=&%40columns=id&creation=&creator=&activity=from+2008-05-10+to+2008-05-11&%40columns=activity&%40sort=activity&actor=&nosy=&type=&components=&versions=&severity=&dependencies=&assignee=&keywords=&priority=&%40group=priority&status=2&%40columns=status&resolution=&%40pagesize=50&%40startwith=0&%40queryname=&%40old-queryname=&%40action=search Roundup search for bugs closed over the weekend].

Upcoming sprint weekends: May 10-11 (a few days after 2.6alpha3 and 3.0alpha5 are scheduled for release), and June 21st-22nd (about a week before 2.6beta2 and 3.0beta2 are released)

Participating at Your User Group

Some Python user groups will meet up in person during the weekend.

The organizers suggest Saturday as the day for PUGs to meet up in person, with Sunday geared more towards an online collaboration day via IRC, where we can take care of all the little things that got in our way of coding on Saturday (like finalising/preparing/reviewing patches, updating tracker and documentation, writing tests ;-).

Is your local user group participating?

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 [http://bugs.python.org 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.

The [http://code.google.com/p/google-highly-open-participation-psf/wiki/StudentPage task list for GHOP] contains many small projects of reasonable difficulty.

Procedures

The goal of the bug day is to process bug reports in [http://bugs.python.org/ 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 [http://www.cs.ubc.ca/~drifty/pycon/sprint_tutorial.pdf slideshow educating new contributors] to the Python code.

What to do:

For later committing

1222 (need to test on non-MacOS, non-Mandriva, non-Debian platform)

1204 (needs up-to-date autoconf)

1291 (needs a non-x86 Linux)

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

Bug days for other projects

The [http://dev.zope.org/CVS/BugDays 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 [http://developer.gnome.org/projects/bugsquad/triage/faq.html their FAQ].

Preparatory Tasks

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