Differences between revisions 1 and 87 (spanning 86 versions)

Next Python Bug Day: November 20th and 21st

Time: all weekend

Participants may be around at any time, we expect at a minimum people from all US continental timezones, France, and Germany. Most likely there will be others as well.

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.

Participating at Your User Group

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

Is your local user group participating?

DC Python Meetup Group (see Sprinting with the DCPython Meetup Group and the project plan).
NY Python Meetup Group.
Sao Paulo Python Users Group (GruPy-SP).
Add your group here!

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:

Procedures

The goal of the bug day is to process bug reports in the Python bug tracker, trying to fix and close issues.

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

Brian Curtin has written a Beginners Guide to Core Development.

What to do:

Grab a copy of the Python SVN trunk. See the development FAQ for instructions. If anonymous access isn't working, you can download a snapshot from the daily snapshot directory.
See also Getting Set Up and Issue Workflow.
If you have a problem that isn't in the bug tracker, announce it to the IRC channel, and if it's more than five minutes' work, create a bug report for it. See the bug reporting instructions to learn how to write bug reports.
When you choose a bug to work on, announce it to the IRC channel. (e.g. "I'm working on #123456.") This avoids accidentally duplicating work.
Consider providing a patch that fixes the problem, or at least a simple test case that demonstrates the bug. Please see the patch submission guidelines before submitting a patch.
Does the bug appear to be gone in the Python 3.x trunk, but not the 3.1 or 2.7 maintenance branchs? Report that, too.
If someone else has supplied a fix, see if this fix works for you, and add your results to the bug.
Read the text of proposed patches and assess them for correctness and code quality. This is usually the most time-consuming step in the bug fixing process, so reading patches is very useful.
If there's a working fix, feel free to add a note asking for the fix to go into SVN. The bug tracker has a lot of items in it, and it's easy for bugs to be overlooked.
Feature requests should be classified as type 'feature request' in the bug tracker.

For later committing

[add notes here as needed]

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
2009-04-25	39 bugs

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

Need to set up log of python-dev channel
Send announcements (python-announce, python-dev, PSF weblog, personal web log. python-list?)

-  ⇤ ← Revision 1 as of 2004-06-01 13:53:04 → 
  Size: 1970
  Editor: AndrewKuchling
  Comment:
+   ← Revision 87 as of 2010-11-17 03:14:14 → ⇥
  Size: 7020
  Editor: FredDrake
  Comment: more links for the DCPython local sprint
-Deletions are marked like this.
+Additions are marked like this.
 Line 1:
-The release of Python 2.4alpha1 is currently scheduled for around July 1st.  An organized effort to go through the bug database and close irrelevant bugs or apply fixes would be very useful.
+''' (!) Next Python Bug Day: November 20th and 21st'''
 Line 3:
-= Proposed schedule =
+Time: all weekend
 Line 5:
-The bug day will be on June XXX, 2004, from 9AM to 9PM EDT.  (XXX need to convert to GMT.)
+Participants may be around at any time, we expect at a minimum people
from all US continental timezones, France, and Germany.  Most likely
there will be others as well.
-Line 7:
+Line 9:
-Participants will convene in the #python IRC channel on irc.freenode.net.
(XXX should we use a different channel?)
+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.

##RDM20101116: uncomment the following at start of weekend.
##How are we doing?  Try a [[http://bugs.python.org/issue?%40columns=title&%40columns=id&activity=from+2010-11-20+to+2010-11-21&%40columns=activity&%40sort=activity&%40group=priority&status=2&%40columns=status&%40pagesize=50&%40startwith=0&%40action=search|Roundup search for bugs closed over the weekend]].

= 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?

  * [[http://meetup.zpugdc.org/calendar/15036971/|DC Python Meetup Group]] (see [[SprintingWithDCPython|Sprinting with the DCPython Meetup Group]] and the [[DCPythonNov2010Sprint|project plan]]).
  * [[http://www.meetup.com/nycpython/calendar/15455613/|NY Python Meetup Group]].
  * [[http://www.python.org.br/wiki/PythonBugWeekend|Sao Paulo Python Users Group (GruPy-SP)]].
  * Add your group here!

= 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:

 * [[http://bugs.python.org/issue?%40search_text=&title=&%40columns=title&id=&%40columns=id&creation=&creator=&activity=&%40columns=activity&%40sort=activity&actor=&nosy=&type=&components=&versions=&severity=&dependencies=&assignee=&keywords=6&priority=&%40group=priority&status=1&%40columns=status&resolution=&%40pagesize=50&%40startwith=0&%40queryname=&%40old-queryname=&%40action=search|Bugs classified as 'easy']]
 * [[http://bugs.python.org/issue?%40search_text=&title=&%40columns=title&id=&%40columns=id&creation=&creator=&activity=&%40columns=activity&%40sort=activity&actor=&nosy=&type=&components=4&versions=&severity=&dependencies=&assignee=&keywords=&priority=&%40group=priority&status=1&%40columns=status&resolution=&%40pagesize=50&%40startwith=0&%40queryname=&%40old-queryname=&%40action=search|Documentation bugs]]

##RDM20101116 The below page is currently empty
##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.
-Line 12:
+Line 55:
-Bugs should be processed in the fashion described by [http://www.python.org/peps/pep-0003.html PEP 3].
+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.
## RDM20101116 PEP 0003 is too out of date to be useful.
## Bugs should be processed in the fashion described by PEP PEP:0003, "Guidelines for Handling Bug Reports".
-Line 14:
+Line 60:
-Someone with write access to the bug database needs to be around at all times.  Having people around with CVS write access would be nice so that fixes can get checked in,but is not necessary; the primary purpose is to improve bug reports, and if the fixes are applied later, that's fine.
+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.
-Line 16:
+Line 63:
-XXX How do people indicate which bugs they're working on?  A wiki page?  A channel message?
The assigned-to field?  

XXX do we need to set up a web transcript of the channel?
+Brian Curtin has written a 
[[http://docs.pythonsprints.com/core_development/beginners.html|Beginners Guide to Core Development]].
-Line 22:
+Line 67:
-   * If a problem isn't logged on SF, log it.
   * If it's logged, consider providing a patch that fixes the problem,
   or at least a simple test case that demonstrates the bug.
+   * Grab a copy of the Python SVN trunk.  See [[http://www.python.org/dev/faq/#version-control|the development FAQ]] for instructions.  If anonymous access isn't working, you can download a snapshot
   from [[http://svn.python.org/snapshots/|the daily snapshot directory]].
   * See also [[http://www.python.org/dev/setup|Getting Set Up]] and [[http://www.python.org/dev/workflow|Issue Workflow]].

   * If you have a problem that isn't in the bug tracker, announce it to the IRC channel, and if it's more than five minutes' work, create a bug report for it.  See the [[http://docs.python.org/dev/bugs.html|bug reporting instructions]] to learn
   how to write bug reports.
   * When you choose a bug to work on, announce it to the IRC channel.  (e.g. "I'm
   working on #123456.")  This avoids accidentally duplicating work.
   * Consider providing a patch that fixes the problem, or at least a simple test case that demonstrates the bug.   Please see the [[http://www.python.org/dev/patches/|patch submission guidelines]] before submitting a patch.
   * Does the bug appear to be gone in the Python 3.x trunk, but not the 3.1 or 2.7 maintenance branchs?  Report that, too.
-Line 26:
+Line 79:
-   you, and post your results to the bug.
+   you, and add your results to the bug.
-Line 28:
+Line 81:
+   This is usually the most time-consuming step in the bug fixing process, so reading patches
   is very useful.
-Line 29:
+Line 84:
-   the fix to go into CVS. The SF bug tracker for Python has a
   _lot_ of bugs in it, and it's easy for bugs to be overlooked.
+   the fix to go into SVN. The bug tracker has a lot of items in it, and it's easy for bugs to be overlooked.
   * Feature requests should be classified as type 'feature request' in the bug tracker.
-Line 32:
+Line 87:
+= For later committing =
-Line 33:
+Line 89:
-= Other processes =
+   * [add notes here as needed]
-Line 35:
+Line 91:
-The [http://dev.zope.org/CVS/BugDays Zope bug day] has a goood description of what to do, though the details of the bug tracker are specified to the Zope project.
+= Questions? =
-Line 37:
+Line 93:
-The GNOME community holds regular Bug Days; the procedures are described in [http://developer.gnome.org/projects/bugsquad/triage/faq.html their FAQ].
+If you have questions about the bug day, please add them to this section.
-Line 39:
+Line 95:
+= Previous bug days =
-Line 40:
+Line 97:
+|| 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 ||
|| 2009-04-25 || [[http://bugs.python.org/issue?%40columns=title&%40columns=id&activity=from+2009-04-25+to+2009-04-26&%40columns=activity&%40sort=activity&%40group=priority&status=2&%40columns=status&%40pagesize=50&%40startwith=0&%40action=search|39 bugs]] ||

= 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 =

 * Need to set up log of python-dev channel
 * Send announcements (python-announce, python-dev, PSF weblog, personal web log.  python-list?)