Last modified: 2007-09-29 22:45:09 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 8935 - Wiktionary Bugzilla component requested
Wiktionary Bugzilla component requested
Product: Wikimedia
Classification: Unclassified
Site requests (Other open bugs)
All All
: Normal normal with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
: 11497 (view as bug list)
Depends on:
  Show dependency treegraph
Reported: 2007-02-09 21:38 UTC by Andrew Dunbar
Modified: 2007-09-29 22:45 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description Andrew Dunbar 2007-02-09 21:38:19 UTC
Now that the English Wiktionary is taking its first tentative steps towards
dictionary-specific modifications and extensions to the mediawiki software, we'd
like to request a place on Bugzilla to store our pending development ideas and
track the bugs in them.
Comment 1 Rob Church 2007-02-09 21:39:22 UTC
For individual extensions, we'll create components for them. For site requests,
use the existing Wikimedia product.
Comment 2 Andrew Dunbar 2007-02-09 21:47:06 UTC
* What about feature requests at an early stage where it's not possible to know
which features might end up in which extensions?

* What if Wiktionary will consist of a set of extensions? It will be difficult
to manage bugzilla for us with nothing to unify what's related to Wiktionary.

* Is a Bugzilla keyword a better idea?
Comment 3 Rob Church 2007-02-09 21:49:34 UTC
(In reply to comment #2)
> * What about feature requests at an early stage where it's not possible to know
> which features might end up in which extensions?

Make them general feature requests, to start with, unless it's quite specific,
in which case, make them extension requests.

> * Is a Bugzilla keyword a better idea?

Comment 4 Andrew Dunbar 2007-09-29 01:34:33 UTC
See also bug 11497
Comment 5 Rob Church 2007-09-29 01:38:01 UTC
*** Bug 11497 has been marked as a duplicate of this bug. ***
Comment 6 Rob Church 2007-09-29 01:38:34 UTC
Reopening for further consideration/more authoritative WONTFIX.
Comment 7 Connel MacKenzie 2007-09-29 01:57:34 UTC
I'm glad that you have such a strong personality.  It generally is good to stick to one's guns.

However, I don't think you've given this appropriate consideration.  A separate BZ component is quite logical, for you, moreso than for me.  (And, by extension, for core developers moreso than for Wiktionary.)

While a separate component would allow Wiktionary to track future feature requests, it would also allow code devs to /ignore/ many more Wiktionary concerns.  The simple fact that we could mark bug reports as duplicates would in and of itself, be monstrously better than trying to track bugs across three (or more) domains, numerous user talk pages, [[wikt:WT:GP]], [[wikt:WT:BR]], [[wikt:WT:BP]], [[wikt:WT:ID]], [[wikt:Wiktionary talk:Main Page]], etc.

Currently, we are dropping requests left and right.  More than half can be addressed easily with Javascript, but get lost in the shuffle.  (E.g. IPA to X-SAMPA converters, Edittools widgets, {{t}} interwiki-ing, input Wizards, etc.)

Discussing this with some other devs in #wikimedia-tech, we were told not to request a separate bugzilla; instead to just ask for a component.  Why?  Well, because it makes SENSE.

I do hope you'll take a fresh look: I don't want to hear a drawn out explanation of why you WONTFIX, rather, I'd like you to consider the benefits of doing what a number of people think is reasonable here.  There is no reason not to create a separate component; there are plenty of reasons to try it out, even if only as a short-term experiment.
Comment 8 Brion Vibber 2007-09-29 22:45:09 UTC

Note You need to log in before you can comment on or make changes to this bug.