Last modified: 2013-12-03 21:15:07 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T59917, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 57917 - Bugzilla should have Flow as a separate Product, not hidden under "extensions"
Bugzilla should have Flow as a separate Product, not hidden under "extensions"
Status: RESOLVED WONTFIX
Product: Wikimedia
Classification: Unclassified
Bugzilla (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-12-03 11:03 UTC by Wikifram@gmail.com (Account disabled)
Modified: 2013-12-03 21:15 UTC (History)
3 users (show)

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


Attachments

Description Wikifram@gmail.com (Account disabled) 2013-12-03 11:03:12 UTC
Currently, bugs about Flow are shelved under Mediawiki extensions, unlike e.g. VisualEditor or less important things like QRpedia. Considering the probable serious influx of Flow bugs in the near future, I would propose that it gets its own "level", so that e.g. in the search box it is selectable (I mean that if you select "search bugs" on the left side, under "Product", you should be able to choose "Flow" directly.
Comment 1 Andre Klapper 2013-12-03 11:13:41 UTC
Flow is technically speaking an extension, and Bugzilla's taxomony is not primarily based on visibility. 
(However there have been exceptions from rules, e.g. when the codebase is rather complex and requires subcomponents, like in case of VisualEditor.)
Comment 2 Wikifram@gmail.com (Account disabled) 2013-12-03 14:58:29 UTC
So, translated, "fuck everyone wanting to find something, Bugzilla is not for you"? Very user-friendly reply. What's the advantage of keeping Flow buried among the other extensions like "AbsenteeLandlord", "Desysop", and so on? I hope yu will reconsider once you get lots of Flow bugs here, which will probably be soon.
Comment 3 Andre Klapper 2013-12-03 17:02:45 UTC
I wouldn't translate it to that, however Bugzilla is primarily a tool for developers and tech-savvy users (though I try to make it more user-friendly, e.g. by the guided bug entry form which is now linked from the very top of https://bugzilla.wikimedia.org/enter_bug.cgi?product=Wikimedia since yesterday).

If you don't feel comfortable on https://bugzilla.gnome.org/enter_bug.cgi and don't know that Flow is a "MediaWiki extension" (and can be found under that product), http://www.mediawiki.org/wiki/Extension:Flow and especially https://www.mediawiki.org/wiki/Flow_Portal#Contact_and_links provide links how to provide feedback and also where exactly to find and create new bug reports or feature requests. 

Furthermore, once Flow has seen wider deployment, I expect the Flow team and involved Communication folks to set up similar Feedback channels like for VisualEditor at https://en.wikipedia.org/wiki/WP:VE/F which do not necessarily require to interact with Bugzilla.
Comment 4 Wikifram@gmail.com (Account disabled) 2013-12-03 21:15:07 UTC
Yeah, sorry about my earlier remark, I was pissed off at a WMF representative (for a oomment made at Mediawiki, not on Bugzilla) and your comment came for me at the wrong time. I shouldn't have replied so strongly. I still think it isn't user friendly to not have it separately, but I appreciate that you try to make it easier for everyone involved anyway.

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


Navigation
Links