https://bugzilla.wikimedia.org/show_bug.cgi?id=38994
--- Comment #21 from MZMcBride <[email protected]> 2012-11-20 00:46:04 UTC --- (In reply to comment #19) > I don't think you can tell Bugzilla to add keyword X by default when filing a > bug report against product/component Y. So? There seems to be this great wall of resistance against adding keywords (tags, if you will...) to bugs. In any sane system, adding tags like this would be a non-issue. I think the crux of the issue is that people don't want the bugspam. Why don't we just switch the default to off for the keywords field and then those interested in tagging bugs (with whatever keywords they want...) can. I guess that's a secondary issue with this flawed Bugzilla keywords design: you need an administrator to make a new keyword. This has hampered keyword usage _for years_ without any good reason. The ability to add arbitrary, searchable metadata to bugs is invaluable and I don't really feel it's necessary to defend that practice here. It just is. If Bugzilla's keywords implementation won't work, let's find something that will. > Plus I still challenge if there is a real need to have this for *every* > family. > Any idea how many people would likely use such a categorization? I see that > *some* families might consider it helpful (bug 35925: wikisource; bug 37883: > commons; bug 28486: incubator) though I'm not sure if the creations of such > tracker bugs had some justification or if somebody "just did it by creating > the > tracker bug" because s/he thought it might be helpful at some point, and now > we > all spend time marking items as blocking though nobody really cares in the > end. Only Wikipedia gets resources from the Wikimedia Foundation currently. You could fairly rename the Wikimedia Foundation the Wikipedia Foundation. And it's been this way for years and anyone with discernible levels of clue understands and acknowledges this. It's not a secret. It's just the way it is right now. However, the sister projects (or Global South projects, as I've taken to calling them) still exist. Wiktionary, Wikinews, Wikiversity, etc. And they still need resources, some of them desperately. So, as a means of high-level triage, I'd like to be able to tag these bugs (using any system really that doesn't require me to build my own separate database of these bugs) so that I can see how many bugs we have in various areas (for example, Wiktionary). And point developers at bugs in these areas. And sort bugs in these areas by priority and votes and importance (and find bugs with high keyword overlap to conserve/maximize finite resources...) to see where that project is and where it needs to be. I'm not asking for anyone to, God forbid, work on any of these bugs or focus on the Global South projects. I'm just asking that we able to sort through the pile of bugs related to these projects at a very high level. > Plus I think I'm afraid that half of my bugmail will be notifications on > keyword changes (though I could switch off bugmail when "The keywords field > changes"). Right. Bugspam. We all hate it. The default value for this user preference can be switched, right? Or in the worst case, someone can futz with the database? I don't see an issue here. -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
