Differences between revisions 76 and 77
Revision 76 as of 2008-11-15 14:00:30
Size: 7081
Editor: localhost
Comment: converted to 1.6 markup
Revision 77 as of 2009-04-15 15:27:06
Size: 6910
Editor: host56
Comment: Update for next bug day
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
'''Global Python Sprint Weekend: Saturday, June 21-22, 2008''' ''' (!) Next Python Bug Day: Saturday, April 25, 2009'''
Line 10: Line 10:
How are we doing? Try a [[http://bugs.python.org/issue?%40search_text=&title=&%40columns=title&id=&%40columns=id&creation=&creator=&activity=from+2008-06-21+to+2008-06-23&%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]]. 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]].
Line 12: Line 12:
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]], 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!
##= 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!
Line 50: Line 48:
The [[http://code.google.com/p/google-highly-open-participation-psf/wiki/StudentPage|task list for GHOP]] contains many small projects of reasonable difficulty. ##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 63: Line 61:
   * 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    * 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
Line 65: Line 63:
   * See also [[http://www.python.org/dev/setup|Getting Set Up]] and [[http://www.python.org/dev/workflow|Issue Workflow]].
Line 84: Line 83:
SF:1222 (need to test on non-MacOS, non-Mandriva, non-Debian platform)

SF:1204 (needs up-to-date autoconf)

SF:1291 (needs a non-x86 Linux)

(!) Next Python Bug Day: Saturday, April 25, 2009

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 Roundup search for bugs closed over the weekend.

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:

There are various things MissingFromDocumentation; these tasks mostly require writing and editing, not programming.

Procedures

The goal of the bug day is to process bug reports in 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 slideshow educating new contributors to the Python code.

What to do:

  • Grab a copy of the Python 2.6 SVN tree. 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 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

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

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

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

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