Bug management/Bug of the week

Planning table
Wikimedia developer teams: Add your team and your three favorite easy boogs here!

Recurring tasks once we run this

 * How and who to communicate the bug of the week: Microblogging; also mailing lists?
 * Want to fix an easy Wikimedia bug? Try https://bugs.wikimedia.org/98765 - more info: https://www.mediawiki.org/wiki/Annoying_little_bugs
 * Remind team or the two main devs a few days before? CC myself on ticket?

Email draft to teams announcing this idea
"Easy bug of the week"

Based on open tickets with the "easy" keyword set in Bugzilla, Engineering Community Team has the idea to expose and advertise a dedicated "bug of the week" for newcomers who want to contribute to code.

Newcomers will be pointed to https://www.mediawiki.org/wiki/Annoying_little_bugs to understand and learn our infrastructure (Bugzilla, Gerrit, general workflows and expectations).

Every week a different development team (rotating) would offer one bug to fix (via a bug report in Bugzilla). If that bug of the week already has a patch attached/linked, contributors can try a different easy bug from the bucket (explained on https://www.mediawiki.org/wiki/Annoying_little_bugs where there are also Bugzilla queries to find these bug reports).

For each development team, this would require commitment to watch that bug report, help contributors with problems on the ticket and on IRC, and review patches in a timely manner. Having two developers of your team who feel a bit responsive listed plus your three favorite easy bugs (so we have fallbacks if someone fixed that bug in the meantime) would be pretty awesome.

Does that sound like an experiment you could imagine to try out?

We'd like to start this in about four weeks.

Cheers, andre

PS: Of course you are always encouraged to tag more Bugzilla tickets which are suitable for newcomers with the "easy" keyword.

Projects to start with

 * Pywikibot
 * L10N
 * Multimedia
 * Parsoid/VE
 * Wikidata

List to be expanded once we're in the flow.

Open questions to still sort out

 * How would a newbie understand which team/project listed under Annoying_little_bugs is responsible for the bug of this week? - Hope my recent edits to Annoying_little_bugs made the connection between product/component in Bugzilla, Git repository, and development team clearer.