|
Size: 1970
Comment:
|
Size: 6951
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | 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. | '''Global Python Sprint Weekend: Saturday, May 10-11, 2008''' |
| Line 3: | Line 3: |
| = Proposed schedule = | Time: all day. Participants are most likely to be around between 9AM to 3PM according to their local time. |
| Line 5: | Line 6: |
| The bug day will be on June XXX, 2004, from 9AM to 9PM EDT. (XXX need to convert to GMT.) | 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 7: | Line 10: |
| Participants will convene in the #python IRC channel on irc.freenode.net. (XXX should we use a different channel?) |
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-12&%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]. 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? * [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], at the [http://geeks.livra.com Livra]/[http://www.devego.com Devego] offices. * 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] 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 54: |
| 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. Bugs should be processed in the fashion described by PEP PEP:0003, "Guidelines for Handling Bug Reports". |
| Line 14: | Line 58: |
| 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. 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? |
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 22: | Line 62: |
| * 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 2.6 SVN tree. See [http://www.python.org/dev/faq/#subversion-svn 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]. * 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. |
| Line 26: | Line 73: |
| you, and post your results to the bug. | you, and add your results to the bug. |
| Line 28: | Line 75: |
| This is usually the most time-consuming step in the bug fixing process, so reading patches is very useful. |
|
| Line 29: | Line 78: |
| 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 can be added to the text of PEP PEP:0042 or classified as type 'feature request' in the bug tracker. |
| Line 32: | Line 82: |
| = For later committing = | |
| Line 33: | Line 84: |
| = Other processes = | SF:1222 (need to test on non-MacOS, non-Mandriva, non-Debian platform) |
| Line 35: | Line 86: |
| 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. | SF:1204 (needs up-to-date autoconf) SF: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. |
| Line 39: | Line 113: |
| = Preparatory Tasks = | |
| Line 40: | Line 115: |
| * Need to set up log of python-dev channel * Send announcements (python-announce, python-dev, PSF weblog, personal web log. python-list?) |
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-12&%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].
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?
[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], at the [http://geeks.livra.com Livra]/[http://www.devego.com Devego] offices.
- 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:
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:
Grab a copy of the Python 2.6 SVN tree. See [http://www.python.org/dev/faq/#subversion-svn 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].
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 0042 or classified as type 'feature request' in the bug tracker.
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
- Need to set up log of python-dev channel
- Send announcements (python-announce, python-dev, PSF weblog, personal web log. python-list?)