Differences between revisions 77 and 96 (spanning 19 versions)
Revision 77 as of 2009-04-15 15:27:06
Size: 6910
Editor: host56
Comment: Update for next bug day
Revision 96 as of 2013-09-03 17:38:06
Size: 5435
Comment: spam
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
''' (!) Next Python Bug Day: Saturday, April 25, 2009'''
Line 3: Line 2:
Time: all day.
Participants are most likely to be around between 9AM to 3PM according to their local time.
'''(!) Next Python Bug Day: November 3rd'''
Line 6: Line 4:
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.
Line 10: Line 5:
How are we doing? Try a [[http://bugs.python.org/issue?%40search_text=&title=&%40columns=title&id=&%40columns=id&creation=&creator=&activity=from+2009-04-25+to+2009-04-26&%40columns=activity&%40sort=activity&actor=&nosy=&type=&components=&versions=&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]]. Time: all Saturday
Line 12: Line 7:
##= 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://wiki.hacdc.org/index.php?title=Python_sprint|Washington DC]], at the [[http://www.hacdc.org|HacDC space]].
## * [[http://www.python.org.za/pugs/cape-town/PythonSprint|The Cape Town PUG]] at the [[http://www.synthasite.com|Synthasite]] Cape Town Offices.
## * [[http://www.pythonbrasil.com.br/moin.cgi/PythonBugDay|São Paulo GruPy]], at the [[http://www.ime.usp.br|USP Math Institute]] (IME).
## * [[http://www.pythonbrasil.com.br/moin.cgi/PythonBugDay|Natal PUG]], at the [[http://www.digi.com.br|Diginet ISP]] office.
## * [[http://www.python.com.ar/moin/Eventos/PythonBugDay|Argentina]], in Buenos Aires at the [[http://geeks.livra.com|Livra]]/[[http://www.devego.com|Devego]] offices, and also in Santa Fé.
## * Add your group here!

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.


To get all set up, the [[http://docs.python.org/devguide|Developer's Guide]] contains all the information you need.


There are usually a few core developers around at any time. Here are the nicknames of developers who will be present for sure:


 * merwok — Éric Araujo — American East Coast timezone
 *





= Participating at Your User Group =


The Montréal-Python user group will meet up in person to participate in the bug day. Some Python user groups will meet up in person during the weekend.


Is your local user group participating?
Line 34: Line 35:
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.

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/|http://www.irchelp.org]].
Line 40: Line 41:
Using [[http://bugs.python.org|the bug tracker]], you can perform various searches to look for
candidate issues:
Line 43: Line 42:
 * [[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]]
Using [[http://bugs.python.org/|the bug tracker]], you can perform various searches to look for candidate issues:
Line 46: Line 44:
There are various things MissingFromDocumentation; these tasks mostly require writing and editing, not programming.
Line 48: Line 45:
##The [[http://code.google.com/p/google-highly-open-participation-psf/wiki/StudentPage|task list for GHOP]] contains many small projects of reasonable difficulty.  * [[http://bugs.python.org/issue?@search_text=&title=&@columns=title&id=&@columns=id&creation=&creator=&activity=&@columns=activity&@sort=activity&actor=&nosy=&type=&components=&versions=&severity=&dependencies=&assignee=&keywords=6&priority=&@group=priority&status=1&@columns=status&resolution=&@pagesize=50&@startwith=0&@queryname=&@old-queryname=&@action=search|Bugs classified as 'easy']]
 * [[http://bugs.python.org/issue?@search_text=&title=&@columns=title&id=&@columns=id&creation=&creator=&activity=&@columns=activity&@sort=activity&actor=&nosy=&type=&components=4&versions=&severity=&dependencies=&assignee=&keywords=&priority=&@group=priority&status=1&@columns=status&resolution=&@pagesize=50&@startwith=0&@queryname=&@old-queryname=&@action=search|Documentation bugs]]
 * [[http://bugs.python.org/issue?@action=random|Random issue]] (you can use the link in the left sidebar of the bug tracker to go through random issues until you find one that you like









Line 52: Line 61:
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 PEP:0003, "Guidelines for Handling Bug Reports".
Line 56: Line 62:
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.
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.















Line 61: Line 82:
   * Grab a copy of the Python 2.6 SVN tree. 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]].
Line 65: Line 83:
   * 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 2.6 trunk, but not the 2.5 maintenance branch?  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 can be added to the text of PEP PEP:0042
   or classified as type 'feature request' in the bug tracker.

= For later committing =
 * Grab a copy of the Python codebase from Mercurial, following instructions in the [[http://docs.python.org/devguide|Developer's Guide]], and compile it.
* 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.") or on the bug report itself. 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 in the Developer's Guide before submitting a patch.
 * Does the bug appear to be gone in the Python development version (the Mercurial branch "default", that will become 3.4), but not the 3.2, 3.3 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 get committed. 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 86: Line 96:
Line 87: Line 98:
Line 90: Line 102:
|| 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 ||
Line 102: Line 103:
= Bug days for other projects =
Line 104: Line 104:
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. ||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?@columns=title&@columns=id&activity=from+2009-04-25+to+2009-04-%20%2026&@columns=activity&@sort=activity&@group=priority&status=2&@columns=status&@pagesize=50&@startwith=0&@action=search|39 bugs]] ||
||2010-11-20 & 21 ||[[http://bugs.python.org/issue?@columns=title&@columns=id&activity=from+2010-11-20+to+2010-11-22&@columns=activity&@sort=activity&@group=priority&status=2&@columns=status&@pagesize=100&@startwith=0&@action=search|55 bugs]] ||
||2012-11-03 ||[[http://bugs.python.org/issue?@columns=title&@columns=id&activity=from+2012-11-03+to+2012-11-04&@columns=activity&@sort=activity&@group=priority&status=2&@columns=status&@pagesize=100&@startwith=0&@action=search|17 bugs]] ||
Line 106: Line 119:
The GNOME community holds regular Bug Days; the procedures are described in [[http://developer.gnome.org/projects/bugsquad/triage/faq.html|their FAQ]].



















Line 110: Line 143:
Line 111: Line 145:
 * Send announcements (python-announce, python-dev, PSF weblog, personal web log.  python-list?)  * Send announcements (python-announce, python-dev, PSF weblog, personal web log. python-list?)

(!) Next Python Bug Day: November 3rd

Time: all Saturday

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.

To get all set up, the Developer's Guide contains all the information you need.

There are usually a few core developers around at any time. Here are the nicknames of developers who will be present for sure:

  • merwok — Éric Araujo — American East Coast timezone

Participating at Your User Group

The Montréal-Python user group will meet up in person to participate in the bug day. Some Python user groups will meet up in person during the weekend.

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

What to do:

  • Grab a copy of the Python codebase from Mercurial, following instructions in the Developer's Guide, and compile it.

  • 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.") or on the bug report itself. 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 in the Developer's Guide before submitting a patch.
  • Does the bug appear to be gone in the Python development version (the Mercurial branch "default", that will become 3.4), but not the 3.2, 3.3 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 get committed. 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.

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

2010-11-20 & 21

55 bugs

2012-11-03

17 bugs

Preparatory Tasks

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

PythonBugDay (last edited 2013-09-03 17:38:06 by EtienneRobillard)

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