Last modified: 2014-09-24 00:32:26 UTC
https://trello.com/c/Sdacc61j/11-complex-buttons
Please clarify here how you envision this working. Mockups attached to this bug may be helpful. That card has no description and the only mockup is apparently unrelated to this.
This bug is not actionable and lacks a use case. Judging on the photo this looks like it might be good to be implemented as part of Multimedia viewer.
Jon, not all bugs are targeted to developers first. This is a bug for design. Once assets are created and uploaded to trello or bugzilla someone from dev can prioritize. Someone on the design team needs to provide this design. This component will be used in Flow (submit post) and login as well.
All bugs should be actionable and clear to people that are outside Wikimedia. As pointed out by Matt and myself this is not clear at all. The trello card linked to is very ambiguous. It also confuses the meaning of "MediaWiki UI" which is why it is becoming a buzz word. Please remember, Bugzilla is a public tool and primarily serves as a way for community members to contribute to our project. We should be more responsible in how we use it, please do not use it as a dumping ground (a private team trello board seems better for the use case for design). Developers shouldn't be prioritizing bugs. That's what product managers are for... but if you have a clear bug, any developer can pick it up in their free time. Please do flesh this out some more if you want to keep it on Bugzilla with view of the above. I'm marking as enhancement on that basis, as this is about building something new.
It is fine to make a bug for designers (when we have Phabricator, bugs, enhancements, design requests, etc. will all be called "tasks"). However, that needs to be made clear (whether it's an implementation request or a design task) in the description. Please also clarify (in the future, the description is a good place for this) what exactly the design task is.
