https://bugzilla.wikimedia.org/show_bug.cgi?id=38994

--- Comment #25 from MZMcBride <b...@mzmcbride.com> 2012-11-20 02:19:04 UTC ---
(In reply to comment #24)
> Comment 14 has a proposal to identify which components are used for which 
> wiki.

Even if you could attach components to wiki project families magically, this
doesn't solve the problem. Krinkle makes the assertion that if you can figure
out which extensions and components apply to a wiki family, you can index by
that family. However, this doesn't seem to take into account bugs about
JavaScript hacks being used in lieu of a proper MediaWiki extension, which is
common on these projects (these non-Wikipedias). Or what about requests to
create a new extension or add some functionality that doesn't exist yet
(because Wikipedia doesn't need it)? How do you index bugs based on this? Using
Bugzilla components alone won't work.

> It likely requires Bugzilla hacking as you cannot define default keywords for
> newly entered reports in a specific component (and I couldn't find an upstream
> bug report either, so seems not to be a popular construction).

I'm not sure why you keep mentioning default keywords. This seems to presume a
component <--> wiki family correlation that I'll go ahead and argue does not
and cannot exist (cf. the preceding reply directly above). We don't need
default keywords; a small (finite) number of keywords (listed below) need to be
added to Bugzilla. In addition, we possibly need to adjust how much noise is
generated by the modification of a bug's keywords.

This seems like a fairly straightforward job for Bugzilla keywords. This would
be a finite set of trackable keywords:

* wikipedia
* wiktionary
* wikibooks
* wikinews
* wikiquote
* wikisource
* wikiversity
* wikivoyage
* wikidata (already exists)

And then we can examine whether it's necesary to simply disable bugspam for
keyword changes. Fair?

-- 
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
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l

Reply via email to