[Python-Dev] Python bug day?
chrism at plope.com
Tue Jun 1 13:37:09 EDT 2004
On Tue, 2004-06-01 at 10:32, A.M. Kuchling wrote:
> Holding a Python bug day seems worth a try. I've written up a Wiki
> page, http://www.python.org/cgi-bin/moinmoin/PythonBugDay, to begin
> planning a bug day and to figure out what tools (if any) are required.
> Please comment, particularly if you've participated in bug days for
> Zope or other projects. Do we need transcripts of the IRC channel?
> Should we use #python or a new channel?
FWIW, I would probably use a dedicated channel for bug day traffic (in
the zope world, we use #zope-dev for bug days as opposed to #zope).
This prevents crosstalk between people trying to fix bugs and people
trying to get help on specific language usage.
For Zope bug days, we set the channel topic to a "bugfix list" where we
try to keep track of all the "resolved" bugs. When someone starts
working on a particular issue, they announce it to the IRC channel ("I'm
going to work on 5416") and and "accept" the issue in the Zope
collector. When someone fixes a bug, they add its issue number to the
IRC channel topic and close the bug in the collector. The purpose of
the resolved-bugs-list in the topic is really to just get a sense of how
many bugs were fixed at the end of the day (we can't get that info out
of the Zope collector).
Bug days have been really useful in the Zope world. Besides providing a
conduit to wrap up loose ends, it's also a great excuse for people who
are currently just users to become developers as they get a sense of
ownership over a bit of the code, especially when they are able to
submit a patch and have it evaluated and maybe committed in real time.
More information about the Python-Dev