At the danger of derailing/forking the conversation...
My preference with bugzilla is to only raise bugs when the outcome is clear. The test I use is if I gave a bug to a newbie could they pick it up and fix it without any questions. If it's not clear I'd start a mailing list conversation with the outcome of cutting a new bug with decisions made.
My worry with using bugzilla as the place of discussion is that a bug can get extremely confusing - especially when people have differing views.
The result of this is a manageable bug list for the mobile site [1] which could one day be empty and is much more manageable.
[1] https://bugzilla.wikimedia.org/buglist.cgi?list_id=147228&field0-0-0=bug...
On Tue, Sep 18, 2012 at 1:31 PM, Quim Gil quimgil@gmail.com wrote:
Hi,
On Tue, Sep 18, 2012 at 1:11 PM, Rob Lanphier robla@wikimedia.org wrote:
My 2c: the "Wikimedia developer hub" page on meta should be the starting point. Let's not create yet another "central" page.
If the primary target are app developers then http://www.mediawiki.org/wiki/API:Main_page + improvements is probably a better target. http://www.mediawiki.org/wiki/Developer_hub
See full reasoning at https://bugzilla.wikimedia.org/show_bug.cgi?id=33464#c8
PS: when a bug report is advertized in a mailing list it is more useful to have the discussion archived around the bug report - do you agree?
-- Quim
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l