Last modified: 2013-06-16 22:49:58 UTC
I failed to find it under extensions where I was expecting it to be.
The VE backend for MediaWiki, once split out, is expected to become an extension on its own (also codewise) soon, but VE itself will stay as a toplevel product. Plus Bugzilla's three levels (classification, product, component) do not allow having subcomponents under components hence not feasible.
...and Bugzilla bugs should be filed under Bugzilla. Moving.
I doubt many will understand the difference between VE and VE backend (the extension?) .I don't. They shouldn't be called the same.
I don't see why VisualEditor can't have an entry in MediaWiki extensions. It's a MediaWiki extension. This is a reasonable place to look for it. You can add a note in the description about filing the bugs under a different product, but we certainly don't to lose bugs because people can't figure out where to file them.
The visual editor backend for MediaWiki, once split out, will actually be a MediaWiki extension, and for that one a component will be created under "MediaWiki extensions" in Bugzilla. The VisualEditor product itself will be MW-independent and hence a product on its own. Like now. > I don't see why VisualEditor can't have an entry in MediaWiki extensions. Because the VE product has components in Bugzilla, and Bugzilla does not allow subcomponents (components that are part of a component). If I make the VE product a component under the "MediaWiki extensions" product in Bugzilla, VE will have to lose all its components. And we don't want that because it's complex enough to have components.
To be fair the bug summary is rather generic. It would make sense to have a placeholder under "MediaWiki extensions", or maybe a mention of the product somewhere.
(In reply to comment #6) > To be fair the bug summary is rather generic. It would make sense to have a > placeholder under "MediaWiki extensions", or maybe a mention of the product > somewhere. The plan is to split the codebase after the beta deployment in a few weeks' time into "VisualEditor core" and "a MediaWiki plug-in that uses this foreign library called VisualEditor". At that point, it might make sense to re-activate "MediaWiki extensions > VisualEditor", if only because that's where people might look for it; I'm happy to triage bugs in two places. In practice you'd likely have most bugs for MW-VE be dependent on VE-core bugs, but that's still manageable. @Andre, thoughts on this?
