Here's a small summary about our first Bug Day which took place on June 27th.
Benjamin Mack and myself were responsible for that first Bug Day. Although we didn't announce it too far in advance we see the outcome of the Bug Day as a big success. Another side advantage of the late announcement was that we could test how the event works out at all - even with just a few people participating.
The focus was on bug triage, cleaning up the Bugtracker, identifying bugs etc. For that we closed long resolved bugs, checked bug reports that were fixed long ago but the reports were duplicates or forgotten, and the community helped in checking if the report is really a bug or just a bad extension that was installed on the reporters' system.
So... many open bug reports could be closed, some were reproducable and over 100 (left open) bug reports were checked and ready to be patched. We're now down to 2233 bug reports for the core after having started the Bug Day with over 3000 bug reports - it's getting less and less! See the Bugtracker tag "bugday" for that.
We think it's quite cool to do such collaborations, and we also think it's cool to continue the Bug Day event every last Friday of the month (also with different focuses and tasks). To do this it would be good if we could find two core developer each month to be responsible for that.
If you want to participate in one or more of the next Bug Days, here are the dates to mark in your calendar:
- July 25th, 2008
- August 29th, 2008
- September 26th, 2008
- October 31th, 2008
- November 28th, 2008
Any comments or ideas are of course welcome. And, yeah, the announcement for the next Bug Days will come more in advance than for this first TYPO3 Bug Day.
