|
Size: 4433
Comment: add bug day result
|
Size: 6958
Comment: wiped out by later change
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| It's always time for a push at closing some Python bugs and patches. | ''' (!) Next Python Bug Day: November 20th and 21st''' |
| Line 3: | Line 3: |
| When a new bug day is planned, announcements will be sent to the python-dev and python-list mailing lists. | Time: all weekend |
| Line 5: | Line 5: |
| = Next bug day = | 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: |
| Date: Friday, March 31st 2006. | 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 9: | Line 13: |
| Time: roughly 9AM to 4PM Eastern (1PM to 8PM GMT) (although the IRC channel won't close at any time ;-) ) | How are we doing? Try a [[http://bugs.python.org/issue?%40columns=title&%40columns=id&activity=from+2010-11-20+to+2010-11-22&%40columns=activity&%40sort=activity&%40group=priority&status=2&%40columns=status&%40pagesize=100&%40startwith=0&%40action=search|Roundup search for bugs closed over the weekend]]. |
| Line 11: | Line 15: |
| People on the US West Coast may want to show up from 9AM to 3PM Pacific time (12PM to 6PM Eastern), because it'll be more convenient. | = Participating at Your User Group = |
| Line 13: | Line 17: |
| = Location = | Some Python user groups will meet up in person during the weekend. |
| Line 15: | Line 19: |
| Participants will convene 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. |
##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? |
| Line 18: | Line 28: |
| = Links = | * [[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! |
| Line 20: | Line 33: |
| The list of bugs currently being worked on is recorded in the Wiki, on the PythonBugDayStatus page. | = 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 24: | Line 54: |
| The goal of the bug day is to process bug reports in [http://sourceforge.net/tracker/?group_id=5470&atid=105470 the Python bug tracker] on SourceForge, providing additional information so that the bug can be fixed and closed. 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". 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. Brian Curtin has written a [[http://docs.pythonsprints.com/core_development/beginners.html|Beginners Guide to Core Development]]. |
| Line 29: | Line 67: |
| * Grab a copy of the Python 2.5 SVN tree. See [http://www.python.org/dev/devfaq.html#subversion-svn the development FAQ] for instructions. If anonymous access isn't working, you can download a snapshot from [http://svn.python.org/snapshots/python/python/ the daily snapshot directory]. * If you have a problem that isn't logged on SF, 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/lib/reporting-bugs.html bug reporting instructions] to learn |
* 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 |
| Line 35: | Line 73: |
| * When you choose a bug to work on, announce it to the IRC channel. (e.g. "I'm working on #123456.") * Consider providing a patch that fixes the problem, or at least a simple test case that demonstrates the bug. Does the bug appear to be gone in Python 2.4.2 or 2.5 SVN? Report that, too. |
* 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 46: | Line 83: |
| the fix to go into SVN. The SF bug tracker for Python has a lot of bugs in it, and it's easy for bugs to be overlooked. * Feature requests can be added to the text of [http://www.python.org/peps/pep-0042.html PEP 42] or moved to the RFE tracker. |
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] |
| Line 54: | Line 94: |
| * Does anyone have a Win32 binary of the current svn snapshot? I'd like to help with stdlib bugs, but I don't have a compiler to build the source tree myself. * There is one kindly contributed by Alexander Schremmer at http://moin.pocoo.org/Python25a. Thanks! |
|
| Line 59: | Line 96: |
| The first bug day was held Saturday, June 5, 2004, from 9AM to 6PM EDT, ending early because SourceForge CVS stopped working. 30 bugs were closed, and 14 more bugs had enough work done to make them closable. The second bug day was held July 10 2004. 18 bugs and 21 patches were closed. The third bug day was Saturday, August 7th. 19 bugs and 12 patches were closed. The fourth bug day was held Saturday, November 7th. 12 bugs and 10 patches were closed. The fifth bug day was held Saturday, June 25th 2005. The bug day was ill-fated, as SourceForge was down at the beginning, the weather was hot around the world and the EuroPython conference took place on the same day. Nevertheless, 10 bugs and 7 patches were closed. The sixth bug day was held Sunday, December 4th 2005. 11 bugs and patches were closed. The seventh bug day was held Friday, March 31st 2006. 19 bugs and 9 patches (which were mostly submitted at the bug day itself) were closed. |
|| 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]] || |
| Line 76: | Line 111: |
| 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 [[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. |
| Line 78: | Line 113: |
| The GNOME community holds regular Bug Days; the procedures are described in [http://developer.gnome.org/projects/bugsquad/triage/faq.html their FAQ]. | 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?) |
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.
How are we doing? Try a 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.
Is your local user group participating?
DC Python Meetup Group (see Sprinting with the DCPython Meetup Group and the project plan).
- 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 |
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?)