Sounds like the right thing to do, yeah. I believe we can close the product to new bugs fairly easily.
On the one hand, if we WONTFIX all the bugs and remove the component, we've got a clean break. It makes it clear that we are not officially supporting the app now.On the other hand, if we leave the bugs open, it would make it easier for a community maintainer to pick up where we left off and take over maintenance. But, it would suck to have people still reporting issues with the expectation that they'll be fixed, when there's no chance we'll look at them.I think we should WONTFIX the bugs and prevent the filing of new bugs against the Commons app somehow, so that people can't file new ones with the expectation of fixes. But all the WONTFIXed bugs should remain in Bugzilla so a community maintainer can access them if he desires.Unless there are any objections or better ideas, I'll ask Andre to implement something to this effect on Monday.DanOn 17 September 2014 00:59, Andre Klapper <email@example.com> wrote:On Tue, 2014-09-16 at 13:32 -0700, Brion Vibber wrote:
> Ok, I've killed the iOS version as well.
There's a "Commons App" product in bugzilla.wikimedia.org with 213
tickets, 82 of them open.
There is also an "Unofficial Apps" product in Bugzilla:
What would you like to see happen in Bugzilla? Move tickets from
'Commons App' to a new component under 'Unofficial'? All lowest
priority? Should Brion really be default assignee for all those
Andre Klapper | Wikimedia Bugwrangler
Mobile-l mailing list
--Dan GarryAssociate Product Manager, Mobile AppsWikimedia Foundation