Differences between revisions 90 and 91
⇤ ← Revision 90 as of 2010-11-21 15:03:52 →
Size: 6958
Editor: c-24-62-201-65
Comment:
← Revision 91 as of 2010-12-26 22:57:43 → ⇥
Size: 1177
Editor: z09-02
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
''' (!) 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 [[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]].

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

= 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.
## 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]].

What to do:

   * 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.
   * 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 || [[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?)		 <?xml version="1.0"?>
<Nef-token xmlns="http://ns.nokia.com/Nef-token/1.0/">
   <Nef-token-details device-id="355718020844799" device-name="DefaultPhone">
   </Nef-token-details>
   <folder-listings>
      <log-folders dev-log-folder="\Data\NEF\log\" card-log-folder="\Data\NEF\log\">
      </log-folders>
      <folder-listing media-type="Images" memory-type="Dev" dev-originated-folder-name="\Data\Images\" ext-store-originated-folder-name="\Data\Images\External\" excluded-folder-name="\Data\Images\TransShrunk\">
      </folder-listing>
      <folder-listing media-type="Images" memory-type="Card" dev-originated-folder-name="\Images\" ext-store-originated-folder-name="\Images\External\" excluded-folder-name="\Images\TransShrunk\">
      </folder-listing>
      <folder-listing media-type="Videos" memory-type="Dev" dev-originated-folder-name="\Data\Videos\" ext-store-originated-folder-name="\Data\Videos\External\">
      </folder-listing>
      <folder-listing media-type="Videos" memory-type="Card" dev-originated-folder-name="\Videos\" ext-store-originated-folder-name="\Videos\External\">
      </folder-listing>
   </folder-listings>
</Nef-token>
XSLT option disabled, please look at HelpOnConfiguration.
<?xml version="1.0"?>
<Nef-token xmlns="http://ns.nokia.com/Nef-token/1.0/">
   <Nef-token-details device-id="355718020844799" device-name="DefaultPhone">
   </Nef-token-details>
   <folder-listings>
      <log-folders dev-log-folder="\Data\NEF\log\" card-log-folder="\Data\NEF\log\">
      </log-folders>
      <folder-listing media-type="Images" memory-type="Dev" dev-originated-folder-name="\Data\Images\" ext-store-originated-folder-name="\Data\Images\External\" excluded-folder-name="\Data\Images\TransShrunk\">
      </folder-listing>
      <folder-listing media-type="Images" memory-type="Card" dev-originated-folder-name="\Images\" ext-store-originated-folder-name="\Images\External\" excluded-folder-name="\Images\TransShrunk\">
      </folder-listing>
      <folder-listing media-type="Videos" memory-type="Dev" dev-originated-folder-name="\Data\Videos\" ext-store-originated-folder-name="\Data\Videos\External\">
      </folder-listing>
      <folder-listing media-type="Videos" memory-type="Card" dev-originated-folder-name="\Videos\" ext-store-originated-folder-name="\Videos\External\">
      </folder-listing>
   </folder-listings>
</Nef-token>

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

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