Hi there!
We have this thing called the Review Queue: https://www.mediawiki.org/wiki/Review_queue
Basically for things that were written by non-WMF feature teams (either volunteers or WMF staff 'other time' stuff). We need to review these things for their performance impact, security, and of course design/ux considerations.
That page links to a general document about the reviews here: https://www.mediawiki.org/wiki/Writing_an_extension_for_deployment
The section on Design: https://www.mediawiki.org/wiki/Writing_an_extension_for_deployment#Design_re...
Which links to: https://www.mediawiki.org/wiki/WMF_Project_Design_Review_Process
Is that page geared for consumption by third-party developers? Or just internal WMF documentation? Is it clear about what things you want from an eg extension author who wants their extension to be deployed on Wikimedia project sites?
Greg
On Thu, Aug 22, 2013 at 11:32 AM, Greg Grossmeier greg@wikimedia.orgwrote:
Which links to: https://www.mediawiki.org/wiki/WMF_Project_Design_Review_Process
Is that page geared for consumption by third-party developers? Or just internal WMF documentation? Is it clear about what things you want from an eg extension author who wants their extension to be deployed on Wikimedia project sites?
If you check the history you can see that Brandon made this page as a proposal back in 2011. It is not particularly up to date or a reflection of input from the entirety of the current design team. We should have something like this though, at least for outlining how design review works for volunteer extensions/patches.
Hi Designers (sorry, I'm going to continue using that ;-) ),
<quote name="Steven Walling" date="2013-08-22" time="17:29:36 -0700">
On Thu, Aug 22, 2013 at 11:32 AM, Greg Grossmeier greg@wikimedia.orgwrote:
Which links to: https://www.mediawiki.org/wiki/WMF_Project_Design_Review_Process
Is that page geared for consumption by third-party developers? Or just internal WMF documentation? Is it clear about what things you want from an eg extension author who wants their extension to be deployed on Wikimedia project sites?
If you check the history you can see that Brandon made this page as a proposal back in 2011. It is not particularly up to date or a reflection of input from the entirety of the current design team. We should have something like this though, at least for outlining how design review works for volunteer extensions/patches.
We have a number of extensions that are awaiting review and/or are starting the review process now. Having something I can point them to that says "think about these things in preparation for a formal design review" is really nice, especially given the fact that in many places we say "get the design review done as early as possible, preferably before any code is written."
Seems not nice to say that but then "we don't know what the review looks like". :/
Sorry, I'm channeling the feedback I'm getting from the community here.
Greg
Its "Hello Designers" :)
https://www.mediawiki.org/wiki/WMF_Project_Design_Review_Process feels like a great place to start, even if it is a bit verbose, we can work on simplifying it.
Are you asking what happens when someone actually needs a review to take place? the process thus far as been to log a bug as a feature request and add the design tag to it, or to email this list.
Maybe you can clarify a bit more?
Jared
* * * * *Jared Zimmerman * \ Director of User Experience \ Wikimedia Foundation M : +1 415 609 4043 | : @JaredZimmermanhttps://twitter.com/JaredZimmerman
On Tue, Aug 27, 2013 at 11:33 AM, Greg Grossmeier greg@wikimedia.orgwrote:
Hi Designers (sorry, I'm going to continue using that ;-) ),
<quote name="Steven Walling" date="2013-08-22" time="17:29:36 -0700"> > On Thu, Aug 22, 2013 at 11:32 AM, Greg Grossmeier <greg@wikimedia.org >wrote: > > > Which links to: > > https://www.mediawiki.org/wiki/WMF_Project_Design_Review_Process > > > > Is that page geared for consumption by third-party developers? Or just > > internal WMF documentation? Is it clear about what things you want from > > an eg extension author who wants their extension to be deployed on > > Wikimedia project sites? > > > > If you check the history you can see that Brandon made this page as a > proposal back in 2011. It is not particularly up to date or a reflection of > input from the entirety of the current design team. We should have > something like this though, at least for outlining how design review works > for volunteer extensions/patches.
We have a number of extensions that are awaiting review and/or are starting the review process now. Having something I can point them to that says "think about these things in preparation for a formal design review" is really nice, especially given the fact that in many places we say "get the design review done as early as possible, preferably before any code is written."
Seems not nice to say that but then "we don't know what the review looks like". :/
Sorry, I'm channeling the feedback I'm getting from the community here.
Greg
-- | Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E | | identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |
Design mailing list Design@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/design
<quote name="Jared Zimmerman" date="2013-08-27" time="11:40:15 -0700">
Its "Hello Designers" :)
Hello Designers,
https://www.mediawiki.org/wiki/WMF_Project_Design_Review_Process feels like a great place to start, even if it is a bit verbose, we can work on simplifying it.
Are you asking what happens when someone actually needs a review to take place? the process thus far as been to log a bug as a feature request and add the design tag to it, or to email this list.
Well, that part should also be included, but more: "Things to think about to ready yourself for the onslaught of a design review" :-)
For example, the corresponding security review page will have some common security mistakes (and how to avoid them, Chris S gave a good preso on this in Amsterdam).
Sorry for the ambiguity!
Greg