Design audit

List overview All Threads
Download

newer

older

Poping up video

Invitation to UX designers for...

Steven Walling

3 Jul 2013 3 Jul '13

3:48 a.m.

Hi all, In a recent meeting, a bunch of us discussed the various design styles specified in skins, jQuery.ui, the newer mediawiki.ui library, and in other places. There was general agreement that we're shooting for consistency as the ideal, but that we've got a lot of work ahead to standardize on any one look and feel, even just for Vector users. One step agreed on was doing an audit of all the places and ways Vector, jQuery.ui, or mediawiki.ui are applied today. To that end, S Page started http://www.mediawiki.org/wiki/Design_audit and an associated category today. Normally I try to upload screenshots to Commons, but it's kind of a pain in the butt to upload MediaWiki screenshots there because you have use custom licensing templates every time. So if you just want to upload locally to MediaWiki.org like S was doing I think that works. We also considered just opening a Dropbox folder, since this stuff doesn't necessarily need to be permanent. Anyway, this is a good place to start. Thanks to S for kicking it off. -- Steven Walling https://wikimediafoundation.org/

Attachments:

attachment.htm (text/html — 1.3 KB)

Show replies by date

Mathieu Stumpf

3 Jul 3 Jul

7:57 a.m.

Le 2013-07-03 05:48, Steven Walling a écrit :

...

Hi all, In a recent meeting, a bunch of us discussed the various design styles specified in skins, jQuery.ui, the newer mediawiki.ui library, and in other places. There was general agreement that we're shooting for consistency as the ideal, but that we've got a lot of work ahead to standardize on any one look and feel, even just for Vector users. One step agreed on was doing an audit of all the places and ways Vector, jQuery.ui, or mediawiki.ui are applied today. To that end, S Page started http://www.mediawiki.org/wiki/Design_audit [1] and an associated category today. Normally I try to upload screenshots to Commons, but it's kind of a pain in the butt to upload MediaWiki screenshots there because you have use custom licensing templates every time. So if you just want to upload locally to MediaWiki.org like S was doing I think that works. We also considered just opening a Dropbox folder, since this stuff doesn't necessarily need to be permanent.

I don't like this idea, because: * you make information less gathered and so for a new contributor, it become harder to get the subject * history * as far as I know, dropbox is a non-free tool, which to my mind is not consistent with the free/libre culture we are promoting.

...

Anyway, this is a good place to start. Thanks to S for kicking it off. -- Steven Walling https://wikimediafoundation.org/ [2] Links: ------ [1] http://www.mediawiki.org/wiki/Design_audit [2] https://wikimediafoundation.org/ _______________________________________________ Design mailing list Design(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/design

-- Association Culture-Libre http://www.culture-libre.org/

bawolff

5:19 p.m.

...

Normally I try to upload screenshots to Commons, but it's kind of a pain in the butt to upload MediaWiki screenshots there because you have use custom licensing templates every time. So if you just want to upload locally to MediaWiki.org like S was doing I think that works. We also considered just opening a Dropbox folder, since this stuff doesn't necessarily need to be permanent.

Brandon Harris

5:22 p.m.

For a project like this, I'd prefer it to go onto the wiki (and mediawiki.org is fine; we [developers] control it). For bulk uploads, get a copy of the Commonist and just point it at mw.org Internally, we use dropbox for the storage of asset files (.psd, .ai, etc.) because they aren't allowed to be uploaded to our mediawiki instances. On Jul 3, 2013, at 10:19 AM, bawolff <bawolff+wn(a)gmail.com> wrote:

...

Please don't just use dropbox. Transparency and all... I don't understand why mediawiki.org would be easier to upload than commons. Just use https://commons.wikimedia.org/wiki/Special:Upload instead of uploadwizard and put your custom license tag in the permissions field (and have the license drop down set to none). --bawolff _______________________________________________ Design mailing list Design(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/design

--- Brandon Harris, Senior Designer, Wikimedia Foundation Support Free Knowledge: http://wikimediafoundation.org/wiki/Donate

bawolff

5:39 p.m.

...

Internally, we use dropbox for the storage of asset files (.psd, .ai, etc.) because they aren't allowed to be uploaded to our mediawiki instances.

Historically we put such things in svn [1] so they don't get lost (and many of the older original assets did get lost). Why can't these sorts of things go in git? Having them in some dropbox somewhere seems to be just begging for the original assets to get lost 5 years from now. [1] https://svn.wikimedia.org/viewvc/mediawiki/trunk/artwork/ --bawolff On Wed, Jul 3, 2013 at 2:22 PM, Brandon Harris <bharris(a)wikimedia.org> wrote:

...

--- Brandon Harris, Senior Designer, Wikimedia Foundation Support Free Knowledge: http://wikimediafoundation.org/wiki/Donate

Steven Walling

5:49 p.m.

On Wed, Jul 3, 2013 at 10:39 AM, bawolff <bawolff+wn(a)gmail.com> wrote:

...

Why can't these sorts of things go in git?

Important assets get added to git as they become a part of the repo in a commit by a developer. Important mockups and other non-production assets that need to be documented long term get uploaded to a wiki, preferably Commons. It's frankly not realistic to say that designers are going to commit every random psd or ai file they might create to a git repo. Many of them have never even used it. -- Steven Walling https://wikimediafoundation.org/

Brion Vibber

6:19 p.m.

On Wed, Jul 3, 2013 at 10:49 AM, Steven Walling <swalling(a)wikimedia.org>wrote;wrote:

...

On Wed, Jul 3, 2013 at 10:39 AM, bawolff <bawolff+wn(a)gmail.com> wrote:

Why can't these sorts of things go in git?

Important assets get added to git as they become a part of the repo in a commit by a developer.

I've seen a *lot* of raster images get added without any vector originals, though, especially when the originals were created in proprietary tools like Photoshop or AI instead of using standard SVGs. Then a year or two later we come by, want to fix something for retina display or change colors around, and have to start from scratch.

...

Important mockups and other non-production assets that need to be documented long term get uploaded to a wiki, preferably Commons. It's frankly not realistic to say that designers are going to commit every random psd or ai file they might create to a git repo. Many of them have never even used it.

Well, it'd be nice for the employees to be trained on the tools the organization uses... -- brion

Steven Walling

6:47 p.m.

On Wed, Jul 3, 2013 at 11:19 AM, Brion Vibber <bvibber(a)wikimedia.org> wrote:

...

Well, it'd be nice for the employees to be trained on the tools the organization uses...

Engineer toolset != organizational toolset. Different strokes for different folks. -- Steven Walling https://wikimediafoundation.org/

Bartosz Dziewoński

7:01 p.m.

On Wed, 03 Jul 2013 20:47:24 +0200, Steven Walling <swalling(a)wikimedia.org> wrote:

...

On Wed, Jul 3, 2013 at 11:19 AM, Brion Vibber <bvibber(a)wikimedia.org> wrote:

Well, it'd be nice for the employees to be trained on the tools the organization uses...

Engineer toolset != organizational toolset. Different strokes for different folks.

Revision control is something even accountants should be trained in. -- Matma Rex

Federico Leva (Nemo)

8:02 p.m.

Bartosz Dziewoński, 03/07/2013 21:01:

...

Revision control is something even accountants should be trained in.

Still, WMF accountants probably do have some way to share files and documents in a permanent fashion (LDAP or anything). At worst, that can be used too. Nemo

Brion Vibber

8:10 p.m.

On Jul 3, 2013 11:48 AM, "Steven Walling" <swalling(a)wikimedia.org> wrote:

...

On Wed, Jul 3, 2013 at 11:19 AM, Brion Vibber <bvibber(a)wikimedia.org>

wrote:

...

> > Well, it'd be nice for the employees to be trained on the tools the

organization uses...

...

Engineer toolset != organizational toolset. Different strokes for

different folks. Fair enough! Lemme think on what it is I really mean to say, I know I didn't come across well there... -- brion

...

-- Steven Walling https://wikimediafoundation.org/ _______________________________________________ Design mailing list Design(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/design

Matthew Flaschen

4 Jul 4 Jul

3:45 a.m.

On 07/03/2013 02:47 PM, Steven Walling wrote:

...

On Wed, Jul 3, 2013 at 11:19 AM, Brion Vibber <bvibber(a)wikimedia.org <mailto:bvibber@wikimedia.org>> wrote: Well, it'd be nice for the employees to be trained on the tools the organization uses... Engineer toolset != organizational toolset. Different strokes for different folks.

With the new very friendly git UIs (e.g. GitHub's are http://windows.github.com/ and http://mac.github.com/, but there are others), I don't think it's asking too much for designers to use git for the source files of assets that are actually being committed/deployed. If they use the GitHub UI, we can use Yuvi's tool to sync with Gerrit. If people want further guidance on git (and its UIs), it is worth setting up a tutorial/walkthrough. Version control is important for anyone working on something that changes over time, whether it's code or art. As Brion says, committing only the PNGs (or other rasters) quite commonly leads to repeated work. Matt

Thehelpfulone

3 Jul 3 Jul

8:38 p.m.

On 3 Jul 2013, at 18:39, bawolff <bawolff+wn(a)gmail.com> wrote:

...

Internally, we use dropbox for the storage of asset files (.psd, .ai, etc.) because they aren't allowed to be uploaded to our mediawiki instances.

Don't we allow these sorts of file types on foundation wiki for this purpose too? --- Thehelpfulone https://meta.wikimedia.org/wiki/User:Thehelpfulone

Matthew Flaschen

4 Jul 4 Jul

3:46 a.m.

On 07/03/2013 04:38 PM, Thehelpfulone wrote:

...

Don't we allow these sorts of file types on foundation wiki for this purpose too?

The Foundation wiki is for the WMF as an entity, not MW (+ extensions, etc.) work. Matt

S Page

3:38 a.m.

On Wed, Jul 3, 2013 at 10:19 AM, bawolff <bawolff+wn(a)gmail.com> wrote:

...

I don't understand why mediawiki.org would be easier to upload than commons.

The design audit categories need to apply to existing mediawiki.org design pages as well as screenshots. mediawiki.org can reference screenshots from commons, but AFAICT it can't apply a local categorization such as [[Category:Inconsistent buttons]] to them. Also, Commons images have different norms, e.g. date is not part of the file name and people replace with improved versions. Regards, -- =S Page software engineer on E3

Bartosz Dziewoński

8:41 a.m.

On Thu, 04 Jul 2013 05:38:09 +0200, S Page <spage(a)wikimedia.org> wrote:

...

mediawiki.org can reference screenshots from commons, but AFAICT it can't apply a local categorization such as [[Category:Inconsistent buttons]] to them.

It can do it just fine, just create local file page. (I agree it's awkward, though.) -- Matma Rex

S Page

12:16 a.m.

On Tue, Jul 2, 2013 at 8:48 PM, Steven Walling <swalling(a)wikimedia.org>wrote;wrote:

...

One step agreed on was doing an audit of all the places and ways Vector, jQuery.ui, or mediawiki.ui are applied today. To that end, S Page started http://www.mediawiki.org/wiki/Design_audit and an associated category today.

Explore https://www.mediawiki.org/wiki/Category:Design_audit . I think subcategories work well to group UI elements. I hope it's useful. -- =S Page software engineer on E3

Matthew Flaschen

3:35 a.m.

On 07/02/2013 11:48 PM, Steven Walling wrote:

...

I think that's fine for now. We can set up a process for migrating to Commons if that's desired by someone later. I would prefer to keep it on wiki, though, rather than using Dropbox for this. Matt

3964

days inactive

3965

days old

design@lists.wikimedia.org

Manage subscription

17 comments

10 participants

tags (0)

participants (10)

Bartosz Dziewoński
bawolff
Brandon Harris
Brion Vibber
Federico Leva (Nemo)
Mathieu Stumpf
Matthew Flaschen
S Page
Steven Walling
Thehelpfulone