Hello,
We (Andre and I) are organizing the first Public Bug Dayhttp://www.mediawiki.org/wiki/Bug_management/Meeting_preparationsfor this year, and we need to decide a topic We would like to hold the bug day mid-late January.
The topic could be going through "Mediawiki/General" or "Wikimedia/General" and assigning them to the to the correct product/component, assigning a priority, etc.
However, Quim suggested (and I would prefer this), to work with a dev team and triage bugs that deal with their project. Are there any dev teams that would be available and willing to participate in a Bug Day? We're going to establish monthly bug days, so if a team can't participate in January, they will have other opportunities in the future.
Thank you, Valerie
On 01/05/2013 05:05 PM, Valerie Juarez wrote:
Hello,
We (Andre and I) are organizing the first Public Bug Dayhttp://www.mediawiki.org/wiki/Bug_management/Meeting_preparationsfor this year, and we need to decide a topic We would like to hold the bug day mid-late January.
The topic could be going through "Mediawiki/General" or "Wikimedia/General" and assigning them to the to the correct product/component, assigning a priority, etc.
Not a bad idea.
Here is another. Bugs filed more than a year ago that never got a single reply. Enhancement requests excluded to make the number more digestible:
However, Quim suggested (and I would prefer this), to work with a dev team and triage bugs that deal with their project.
That idea came with the concept of aligning Bug Days with testing sprint. The next sprint we know about is the one for Echo notifications on January 30, but at least looking at the numbers the Echo team doesn't seem to have a big problem of bug handling...
Let's see whether other active teams reply. It would be worth being explicit in saying that this is not limited to Wikimedia Foundation teams.
If nobody replies (or in any case) and idea would be:
# Pick a few projects somehow related and accumulating a nice number of stalled bugs reports. # Gather the emails of maintainers, contributors and people that has been reporting / commenting on those bugs. # Organize a Bug Day to clean/update those products / components, send the call to the related people and the relevant channels.
The good thing about tackling semi-abandoned reports is that they are less demanding and more people can potentially do something good for them, even if it's only a little push to see if they are completely dead or not. Compare this with active projects like Wikimedia Mobile - Visual Editor - Article Feedback etc where you need to be quite an insider to add something where nobody did before.
Andre and me learned yesterday from Sumana that bug days were held previously on a weekly basis. This might complicate things, although maybe actually not. A possibility:
1. Pick a day e.g. "Thursday is Bug Day!"
2. Find a small task / area in Bugzilla e.g. "Let's clean MediaWiki Extensions >> Drafts" https://bugzilla.wikimedia.org/buglist.cgi?list_id=172051&resolution=---...
3. Take a chat room less noisy than #mediawiki, or create one just for the occasion.
4. Define a list of nicknames you, Andre, etc (and their availability that day. Define also 4 hours of higher intensity where all of you will be there and focusing on the Bug Day activity.
5. Announce the day before to wikitech-l, mediawiki-l and optionally to any other relevant list.
6. Keep all this up to date at https://www.mediawiki.org/wiki/Bug_management/Meeting_preparations or the alternative page of your choice.
It feels like more work, but then again choosing smaller topics is easier and if a week goes meh then it's not a big deal.
On 01/09/2013 12:02 PM, Quim Gil wrote:
Andre and me learned yesterday from Sumana that bug days were held previously on a weekly basis. This might complicate things, although maybe actually not. A possibility:
Pick a day e.g. "Thursday is Bug Day!"
Find a small task / area in Bugzilla e.g. "Let's clean MediaWiki
Extensions >> Drafts" https://bugzilla.wikimedia.org/buglist.cgi?list_id=172051&resolution=---...
- Take a chat room less noisy than #mediawiki, or create one just for
the occasion.
#wikimedia-dev is usually best, in my experience.
- Define a list of nicknames you, Andre, etc (and their availability
that day. Define also 4 hours of higher intensity where all of you will be there and focusing on the Bug Day activity.
- Announce the day before to wikitech-l, mediawiki-l and optionally to
any other relevant list.
A few days before, please!
- Keep all this up to date at
https://www.mediawiki.org/wiki/Bug_management/Meeting_preparations or the alternative page of your choice.
It feels like more work, but then again choosing smaller topics is easier and if a week goes meh then it's not a big deal.
https://www.mediawiki.org/wiki/Bug_management/Meeting_preparations does hold nearly all these best practices -- and if anything's missing, yes, please add it. Looking forward to more bug triage events (and, very importantly, FOLLOWUP on those triages, especially where individuals said "sure, I'll fix that").
wikitech-l@lists.wikimedia.org