Steven, from the very beginning of Beta Features we acknowledged their would be Beta Features that were only for experimenting and exploring, that they wouldn't graduate. So this isn't a concern of mine. I think the only way we'll be able to get a good solid review of the controls, both internally and from users is to package it up as a beta feature and let people use the real production site with all the new controls in place. Matt's test instance is great but won't serve the same purpose.
*Jared Zimmerman * \\ Director of User Experience \\ Wikimedia Foundation M +1 415 609 4043 \\ @jaredzimmerman <http://loo.ms/g0> On Thu, Aug 21, 2014 at 1:55 PM, Steven Walling <[email protected]> wrote: > > On Tue, Aug 19, 2014 at 3:29 PM, Jared Zimmerman < > [email protected]> wrote: > >> Ok, I've been thinking about this for a bit. my suggestion is this… >> >> >> We create 3 more controls >> >> - Dropdown <https://trello.com/c/bdpbPSZT/4-drawer-menu> >> (can Juliusz's work on compact person bar be componentized?) >> - Search Field <https://trello.com/c/MC8ovuyw/2-advanced-input-fields> >> - Radio Button <https://trello.com/c/df2N2KJx/8-radio-buttons> >> >> Finalize 2 controls >> >> - Check box (disabled state, disabled checked) >> - Vform (vertical padding) >> >> Then let's make a Beta feature to allow people to test and see >> medaiwiki.ui in context in vector(at least) and report problems. >> >> I'd love to be able to provide a fixed element on screen that allows >> someone to quickly and easily report problems with a control on a >> particular page (isn't using mediawiki.ui style, isn't using right type >> (progressive, constructive, destructive) and right style normal, quiet, >> etc. and any issues around order or logic, e.g. on WTE Save should be the >> rightmost according to mediawiki.ui guidelines and there are too many >> Primary style buttons. >> >> *Jon*, perhaps you could brainstorm a fixed header element that allows >> someone to report an issue on their current page that generates bug reports >> or emails or something along those lines? >> >> Is there any way we could accelerate fixes reported by users more than >> our normal time span of 2-3 weeks? cc'ing *Greg* for his thoughts here >> about a way to do this without breaking things. >> >> This won't be our first Beta feature that is more for learning and >> testing with no plans to graduate but we should be clear that that's what >> its for in the description on the beta page, so people can give helpful and >> constructive feedback knowing that it will be an iterative process. >> > > Like Erik said, we need to not be in a rush here. This thing is kind of a > mess and needs some basic design review first, before we charge ahead with > expanding the scope into new controls or a reporting tool like you > suggested. I also am very uncomfortable saying we should release a Beta > Feature we don't intend to graduate. > > -- > Steven Walling, > Product Manager > https://wikimediafoundation.org/ > > _______________________________________________ > Design mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/design > >
_______________________________________________ Design mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/design
