I recently ran across this quote[1]:
*“When I started out in my career, design was seen as a necessary evil,
especially in relation to technology. It moved into this phase where all of
the sudden people saw design as a corporate identity thing, like ‘all of
our products need to look alike.’ In the early 1990s, it moved into
innovation for innovation’s sake. And then there started being this shift,
driven somewhat by Apple, where people began to understand that design was
what made them want your technology to be part of their lives."*
- Robert Brunner, industrial designer who worked for many years at Apple
and now runs his own design studio.
It really struck me as relevant to the changes we have seen/hope to see at
the foundation, w/r/t design's role.
Have a nice weekend all,
Josh
[1] -
https://www.theatlantic.com/technology/archive/2017/06/what-apple-thought-t…
Josh Clark on design principles for addressing flaws in machine learning.
(via waxy.org)\
"The answer machines have an overconfidence problem. It’s not only a
data-science problem that the algorithm returns bad conclusions. It’s a
problem of presentation: the interface suggests that there’s one true
answer, offering it up with a confidence that is unjustified.
So this is a design problem, too. The presentation fails to set appropriate
expectations or context, and instead presents a bad answer with
matter-of-fact assurance. As we learn to present machine-originated
content, we face a very hard question: how might we add some productive
humility to these interfaces to temper their overconfidence?
I have ideas."
https://bigmedium.com/speaking/design-in-the-era-of-the-algorithm.html
Yours,
Chris Koerner
Community Liaison - Discovery
Wikimedia Foundation
I have been using Things for 8 years (Except for a year I spent in the
wilderness when I searched for a personal todo app that could also be a
shared team app as well).
It was always the best native experience on Apple platforms - they won an
Apple design award, but they were always slow to update (Another reason I
attempted to look elsewhere). Personally, it was also the most “natural”
todo app I have used. It fits my mental model extremely well with a light
but not onerous GTD model.
Last month they released version 3… and it’s absolutely amazing. The amount
of care that went into every UI element, action and animation is simply
incredible.
I admittedly hesitated to buy it for a few days as it is one of the most
expensive suite of apps to buy, but I finally obught the iPhone app today
and was blown away.
This is the app that allows me to stay organized - so if you are in the
Mac/IPhone ecosystem, I can’t recommend it enough. But even if you don’t
want to buy it, I think it is worth watching videos one the UI or at least
buying the iPhone version to play with it and study the UI.
One last thing, it is on sale right now. So if you are tempted you may want
to grab it soon.
https://culturedcode.com/things/
--
Corey Floyd
Engineering Manager
Reading
Wikimedia Foundation
cfloyd(a)wikimedia.org
Following the process described in the Code of Conduct for Wikimedia
technical spaces <https://www.mediawiki.org/wiki/Code_of_Conduct>, the
Wikimedia Foundation’s Technical Collaboration team has selected five
candidates to form the first Code of Conduct Committee and five candidates
to become auxiliary members.
Here you have their names in alphabetical order. For details about each
candidate, please check
https://www.mediawiki.org/wiki/Code_of_Conduct/Committee_members
Committee member candidates:
-
Amir Sarabadani (Ladsgroup)
-
Lucie-Aimée Kaffee (Frimelle)
-
Nuria Ruiz (NRuiz-WMF)
-
Sébastien Santoro (Dereckson)
-
Tony Thomas (01tonythomas)
Auxiliary member candidates:
-
Ariel Glenn (ArielGlenn)
-
Caroline Becker (Léna)
-
Florian Schmidt (Florianschmidtwelzow)
-
Huji
-
Matanya
This list of candidates is subject to a community review period of two
weeks starting today. If no major objections are presented about any
candidate, they will be appointed in six weeks.
You can provide feedback on these candidates, via private email to
techconductcandidates(a)wikimedia.org. This feedback will be received by
the Community
Health
<https://meta.wikimedia.org/wiki/Technical_Collaboration/Community_health>
group handling this process, and will be treated with confidentiality.
We want to thank all the people who has considered the possibility to
support the Code of Conduct with their participation in this Committee. 77
persons have been contacted during the selection process, counting
self-nominations and recommendations. From these, 21 made it to a short
list of candidates confirmed and (according to our estimation) a potential
good fit for the Committee. Selecting the five candidates for the Committee
has been hard, as we have tried to form a diverse group that could work
together effectively in the consolidation of the Code of Conduct. Selecting
the five auxiliary members has been even harder, and we know that we have
left out candidates who could have contributed just as much. Being the
first people assuming these roles, we have tended a bit towards more
technical profiles with good knowledge of our technical spaces. We believe
that future renewals will offer better chances to other profiles (not so
technical and/or not so Wikimedia veteran), adding a higher diversity and
variety of perspectives to the mix.
On Thu, Mar 9, 2017 at 12:30 PM, Quim Gil <qgil(a)wikimedia.org> wrote:
> Dear Wikimedia technical community members,
>
> https://www.mediawiki.org/wiki/Code_of_Conduct
>
> The review of the Code of Conduct for Wikimedia technical spaces has been
> completed and now it is time to bootstrap its first committee. The
> Technical Collaboration team is looking for five candidates to form the
> Committee plus five additional auxiliary members. One of them could be you
> or someone you know!
>
> You can propose yourself as a candidate and you can recommend others
> *privately* at
> techconductcandidates AT wikimedia DOT org
>
> We want to form a very diverse list of candidates reflecting the variety
> of people, activities, and spaces in the Wikimedia technical community. We
> are also open to other candidates with experience in the field. Diversity
> in the Committee is also a way to promote fairness and independence in
> their decisions. This means that no matter who you are, where you come
> from, what you work on, or for how long, you are a potential good member of
> this Committee.
>
> The main requirements to join the Committee are a will to foster an open
> and welcoming community and a commitment to making participation in
> Wikimedia technical projects a respectful and harassment-free experience
> for everyone. The committee will handle reports of unacceptable behavior,
> will analyze the cases, and will resolve on them according to the Code of
> Conduct. The Committee will also handle proposals to amend the Code of
> Conduct for the purpose of increasing its efficiency. The term of this
> first Committee will be one year.
>
> Once we have a list of 5 + 5 candidates, we will announce it here for
> review. You can learn more about the Committee and its selection process at
> https://www.mediawiki.org/wiki/Code_of_Conduct/Committee and you can ask
> questions in the related Talk page (preferred) or here.
>
> You can also track the progress of this bootstrapping process at
> https://www.mediawiki.org/wiki/Talk:Code_of_Conduct#
> Bootstrapping_the_Code_of_Conduct_Committee
>
> PS: We have many technical spaces and reaching to all people potentially
> interested is hard! Please help spreading this call.
>
> --
> Quim Gil
> Engineering Community Manager @ Wikimedia Foundation
> http://www.mediawiki.org/wiki/User:Qgil
>
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
Hello Design List,
One challenge I have in my daily work is combining the needs of beginners
and "function experts", people who are used to a specific function/UI.
The "experts" are used to a specific UI and don't like to see changes (for
understandable reasons, even if the current UI has quirks, they are used to
the current state and would have costs of relearning)
On the other hand, we know that some functions/UIs are really hard to grasp
for non-experts. This could be new members of the community, but it could
also be established members of the community who touch a function only from
time to time ("perpetuate intermediates", as Cooper says in "About Face")
and/or who transition into a new role (Editor becomes Admin and has now new
functions to use) – which I find important to mention, since it breaks the
"experts" vs. "noobs" narrative.
I wonder if you have any practices or examples that show how our UIs can be
made easy to get for beginners, efficient for experts and build and
introduced them a way that ensures that those who know an existing UI feel
it is worth to adapt to changes.
Kind Regards,
Jan
--
Jan Dittrich
UX Design/ User Research
Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Phone: +49 (0)30 219 158 26-0
http://wikimedia.de
Imagine a world, in which every single human being can freely share in the
sum of all knowledge. That‘s our commitment.
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/029/42207.
Microsoft released a design toolkit for developing inclusive designs.
There's a lot of empathy in what they've produced. It's rather inspiring
and hopefully something to learn from in our own initiatives.
https://www.microsoft.com/en-us/Design/inclusive
Yours,
Chris Koerner
Community Liaison - Discovery
Wikimedia Foundation
Dear Wikimedia technical community members,
https://www.mediawiki.org/wiki/Code_of_Conduct
The review of the Code of Conduct for Wikimedia technical spaces has been
completed and now it is time to bootstrap its first committee. The
Technical Collaboration team is looking for five candidates to form the
Committee plus five additional auxiliary members. One of them could be you
or someone you know!
You can propose yourself as a candidate and you can recommend others
*privately* at
techconductcandidates AT wikimedia DOT org
We want to form a very diverse list of candidates reflecting the variety of
people, activities, and spaces in the Wikimedia technical community. We are
also open to other candidates with experience in the field. Diversity in
the Committee is also a way to promote fairness and independence in their
decisions. This means that no matter who you are, where you come from, what
you work on, or for how long, you are a potential good member of this
Committee.
The main requirements to join the Committee are a will to foster an open
and welcoming community and a commitment to making participation in
Wikimedia technical projects a respectful and harassment-free experience
for everyone. The committee will handle reports of unacceptable behavior,
will analyze the cases, and will resolve on them according to the Code of
Conduct. The Committee will also handle proposals to amend the Code of
Conduct for the purpose of increasing its efficiency. The term of this
first Committee will be one year.
Once we have a list of 5 + 5 candidates, we will announce it here for
review. You can learn more about the Committee and its selection process at
https://www.mediawiki.org/wiki/Code_of_Conduct/Committee and you can ask
questions in the related Talk page (preferred) or here.
You can also track the progress of this bootstrapping process at
https://www.mediawiki.org/wiki/Talk:Code_of_Conduct#Bootstrapping_the_Code_…
PS: We have many technical spaces and reaching to all people potentially
interested is hard! Please help spreading this call.
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil