Sounds great to me. One question, though. What need to be done, when several issues are dicussed at the same time making it hard to participate in the dicussion? Make a branch-channel? Or it just doesn't happen? How did Zope people solve it? Regards, jiwon. A.M. Kuchling wrote: >For the impending 2.4alpha1 release, a coordinated effort to reduce >the bug backlog would be good. Several other projects (Zope, GNOME, >Mozilla) have "bug days" in which people meet on IRC and go through >the bug database, closing irrelevant or incorrect reports, writing >small test cases for vague reports, etc. > >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? > >If the details can get sorted out in time, perhaps we can have a bug >day as soon as this weekend. Is a weekend day better than a weekday >for people who are interested in participating? > >--amk > >_______________________________________________ >Python-Dev mailing list >Python-Dev at python.org >http://mail.python.org/mailman/listinfo/python-dev >Unsubscribe: http://mail.python.org/mailman/options/python-dev/jiwon%40softwise.co.kr > > > >
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4