Replying to old messages to provide public status updates: On Thu, 2013-09-19 at 10:43 -0700, Quim Gil wrote: > One idea that spontaneously came out was to highlight > https://www.mediawiki.org/wiki/Annoying_little_bugs > and use these selected bugs as an entry point for new contributors. As a > specific goal we decided to promote ONE bug to solve every week. The > point of this being not only to fix that bug, but also (and mainly) to > advertise entry points to different tech projects and activities, and > Bugzilla/QA itself. > > Andre took the action of organizing a Bug Day in October to kick off > this process.
We had put this on the backburner to run Google Code-In first from November to January. > * Triage reports tagged as EASY: > https://bugzilla.wikimedia.org/buglist.cgi?keywords=easy%2C%20&keywords_type=allwords&list_id=234714&resolution=---&query_format=advanced This is mostly done now. > * Choose the annoying little bugs for the next 4 weeks, plus a backlog > of a dozen featured bugs from different areas, just in case. Not done yet, we'll probably try next month. > * Improve https://www.mediawiki.org/wiki/Annoying_little_bugs as a > landing page to be promoted through Wikimedia mainstream channels. Done now, based on common issues of contributors in Google Code-In. Also provides Bugzilla queries for specific areas. Take a look. :) > What we should do before is to document the criteria that make a bug > EASY, so we and anybody can assign that keyword consistently. Done on https://bugzilla.wikimedia.org/describekeywords.cgi Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ _______________________________________________ QA mailing list QA@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/qa
