Hi all,
I wanted to share a short video that illustrates some ideas for the user
experience improvement of the Translate extension.
The video is available at http://youtu.be/xKfaLyJE4ow?hd=1 (links to
different language-specific versions of the prototypes are available at the
video description)
Arun and I are organizing usability testing sessions these weeks. Anybody
can volunteer for participation in the usability tests at
http://goo.gl/E5dvO
The only requirement is to speak more than one language, but no previous
experience with translation is required.
Feel free to provide any comment on the prototype, or join the testing
sessions.
Pau
--
Pau Giner
Interaction Designer
Wikimedia Foundation
Hi Brandon,
I was wondering if you could talk to us a little bit/ or tell us about a
few folks in the community who are voices that can help us and
tend to provide design feedback more than the others.
I think this might help with conversations a little bit..
Thoughts?
Vibha
I think the UX is pretty good here already (thanks to anyone on the
list who contributed), but additional feedback is appreciated.
In the long run it would be good to generalize the "Add from Flickr"
into a generalized "Add from [source 1|source 2|...]" UI, but I think
it's fine for now.
Erik
---------- Forwarded message ----------
From: Erik Moeller <erik(a)wikimedia.org>
Date: Wed, Aug 29, 2012 at 6:10 PM
Subject: Testing Upload Wizard Flickr import feature
To: Wikimedia Commons Discussion List <commons-l(a)lists.wikimedia.org>
Hi,
Kaldari has been polishing the work done during Google Summer of Code
by Ankur Anand to support importing correctly licensed Flickr
photo(-sets) using Upload Wizard. You specify a photoset URL, and
Upload Wizard should treat it like a batch upload. You can test the
feature here:
http://mwreview.wmflabs.org/wiki/index.php/Main_Page (you'll need to
make a new test user account)
Just click the "Import from Flickr" button on the first page to get started.
Since UW performs a license check, UW will also add a
"VerifiedByUploadWizard" template which should help with the long term
validation of licenses for Flickr imported content.
Known issues:
* Getting a better 'source' value for each image - ideally we want the
regular Flickr URL, not the farm server URL
* Getting the description for each image, this may require separate
calls to the Flickr API.
* Making the 'author' value a link to the Flickr account
* Supporting the feature to copy metadata across a whole batch, which
is shown for regular batch uploads
Now's a good time to start playing with it. You can leave feedback
here: http://mwreview.wmflabs.org/wiki/index.php/Talk:Flickr_testing -
or file in Bugzilla against the UploadWizard extension.
Thanks!
Erik
--
Erik Möller
VP of Engineering and Product Development, Wikimedia Foundation
Support Free Knowledge: https://wikimediafoundation.org/wiki/Donate
--
Erik Möller
VP of Engineering and Product Development, Wikimedia Foundation
Support Free Knowledge: https://wikimediafoundation.org/wiki/Donate
Thanks Oliver and Vibha, and its good to see that the wiki pages got some
cleanup :)
Can I also suggest that we have a common etherpad that is used to note down
things related to the project? Pau and I have been coordinating work this
way for the translation ux improvements[1] and it works quite well for
staying in sync with each other.It can also give an external person a quick
view of any recent activity that has not yet gone on mediawiki. If you guys
already have existing etherpads, can you share the link on the MW page?
[1] http://etherpad.wikimedia.org/l10n-translation-ux
--
Arun Ganesh
(planemad) <http://en.wikipedia.org/wiki/User:Planemad>
Geography.Information.Design
Arun, thanks for your enthusiasm on this :). If you've got any ideas,
suggestions or comments, the Talk page on Mediawiki.org for the Micro
Design Improvements project is probably the best place to put them.
Alternately you *can* go directly to me, but I'd prefer to have ideas
discussed publicly whenever possible: as you note, it's hard for remote
contractors to get involved in discussions, and I see greater transparency
as a way of making this easier :). I'm a remote worker myself. I'll be
encouraging people to use the MW.org pages as more than just an etherpad or
features spec: it's a good venue to publicly have the discussions about
what we're including, why we're including it and what we've got coming up.
Thanks!
From: Vibha Bamba <vbamba(a)wikimedia.org>
> Date: Tue, Aug 28, 2012 at 9:29 PM
> Subject: Re: [Design] Remote participation in ongoing design projects
> To: "A list for the design team." <design(a)lists.wikimedia.org>
>
>
> Hi Arun,
> MDI is something I started because there is a lot of small low hanging
> fruit that we can try to address with with the community (Like you
> stated)
> Its also bits and pieces that may never be roadmap priorities because
> they are too small.
>
> I believe they can cumulatively contribute to a better UX.
> Please feel free to log your ideas on the wiki and connect with
> Oliver. Oliver is the community liason on this project.
> We are testing the waters with one starter project to see how
> implementation might pan out and if this approach will fly.
>
> Thanks
> Vibha
>
> On Tue, Aug 28, 2012 at 12:06 PM, Arun Ganesh <arun.planemad(a)gmail.com>
> wrote:
> >
> > As a contractor working on UX improvement, I realize there is a lot of
> work that the wmf design team is upto which I can involve myself with. I'm
> particularly interested in the low hanging fruits [1] where I think a lot
> of the random ideas I have can fit in. Being remote however means that it
> is not always easy to attend design discussion meetings and am cut off from
> any offline conversation that takes place when the lid is down.
> >
> > In the interest of me and other remote participants interested in
> providing feedback to critical wmf design projects, what would be the
> recommended channel to keep an eye on to follow the activity on different
> projects? I would think mediawiki is where all documentation should be
> eventually consolidated, but in reality is not updated often enough to be
> of much use.
> >
> > Hopefully i'm not missing the party somewhere where i've not looked, in
> which case you should toss me in the pool :)
> >
> > [1] http://www.mediawiki.org/wiki/Micro_Design_Improvements
>
--
Oliver Keyes
Community Liaison, Product Development
Wikimedia Foundation
--
Oliver Keyes
Community Liaison, Product Development
Wikimedia Foundation
Cross-posting
---------- Forwarded message ----------
From: Erik Moeller <erik(a)wikimedia.org>
Date: Tue, Aug 28, 2012 at 1:44 AM
Subject: [Echo] Bubble notifications
To: WMF Editor Engagement Team <ee(a)lists.wikimedia.org>
Echo team & designers,
Trevor recently made some improvements to MediaWiki's UI library for
generating simple on-wiki notification messages, in order to make the
system more useful for the Visual Edtior. This basic change [1] is now
live on en.wp and can be seen when you add a page to your watchlist --
where previously you got a big, centered message, you now get a bubble
notification in the top right corner that disappears after a while,
unless your mouse is over it.
Daniel Friesen, a volunteer, is currently working on improving this
system further into a more general notification message front-end. [2]
This change has not been merged yet. You can find a video of the
system in action here:
https://www.mediawiki.org/wiki/File:Mw-notification.ogv
NB: This is purely a front-end, it doesn't know anything about the
notifications it displays.
Have the implications of this UI approach for Echo been considered
already? Specifically:
- Under what circumstances would a bubble notification be appropriate,
as opposed to the "just increment a number" approach? Right now
they're used for application messages ("You just added this article to
your watchlist"), not for service notifications ("The article Foo on
your watchlist has just been modified by User:Bar").
Different users likely have different preferences here (yay,
preferences), but I can see this type of real-time notification being
potentially very engaging and actually reducing the distraction
factor, compared with an increasing notification counter which forces
you to click on it to see what's going on.
- If we use this style of notification, how would we indicate the
connection between the bubble notification and the list of all
notifications to the user? Would we still increment a number?
Presumably yes, as the user may not be watching her browser tab while
it's displaying the notification. But then we'd have an odd mix of
application messages ("You have performed action X with result Y")
which don't increment the notification counter vs. service messages
which do.
- Is this design appropriate for touch devices (where we can't do the
mouseover detection to halt the timer), and if not, what changes would
make it more useful?
Some food for thought & considerations as we get further into echo,
Erik
[1] https://gerrit.wikimedia.org/r/#/c/17605/
[2] https://gerrit.wikimedia.org/r/#/c/19199/
--
Erik Möller
VP of Engineering and Product Development, Wikimedia Foundation
Support Free Knowledge: https://wikimediafoundation.org/wiki/Donate
--
Erik Möller
VP of Engineering and Product Development, Wikimedia Foundation
Support Free Knowledge: https://wikimediafoundation.org/wiki/Donate
As a contractor working on UX improvement, I realize there is a lot of work
that the wmf design team is upto which I can involve myself with. I'm
particularly interested in the low hanging fruits [1] where I think a lot
of the random ideas I have can fit in. Being remote however means that it
is not always easy to attend design discussion meetings and am cut off from
any offline conversation that takes place when the lid is down.
In the interest of me and other remote participants interested in providing
feedback to critical wmf design projects, what would be the recommended
channel to keep an eye on to follow the activity on different projects? I
would think mediawiki is where all documentation should be eventually
consolidated, but in reality is not updated often enough to be of much use.
Hopefully i'm not missing the party somewhere where i've not looked, in
which case you should toss me in the pool :)
[1] http://www.mediawiki.org/wiki/Micro_Design_Improvements
--
Arun Ganesh
(planemad) <http://en.wikipedia.org/wiki/User:Planemad>
Geography.Information.Design
I wrote a handy FAQ on usability tests that can be reused if anyone is
making a call for volunteers.
Translate UX Participate FAQ:
http://www.mediawiki.org/wiki/Translation_UX/Participate
For the translate UX improvements Pau and I are working on, considerable
time was spent in managing communications and test schedules with
volunteers. Because no volunteer had participated in such a test before,
they often asked for clarifications on preparations they have to make and
the duration. We now point them to this faq and it seems to have helped
resolve common queries and make the tests something to look forward to,
rather than a 'test'.
Feel free to extend this for future tests and pop some feedback for
improvements.
--
Arun Ganesh
(planemad) <http://en.wikipedia.org/wiki/User:Planemad>
Geography.Information.Design
<http://j.mp/ArunGanesh>
