Please comment on whether to approve the "Conflict of interest" section
of the draft Code of conduct for technical spaces. This section did not
reach not reach consensus earlier, but changes were made seeking to
address the previous concerns.
You can find the section at
https://www.mediawiki.org/w/index.php?title=Code_of_Conduct/Draft&oldid=229…
You can comment at
https://www.mediawiki.org/wiki/Talk:Code_of_Conduct/Draft#Finalize_new_vers…
.
A position and brief comment is fine.
You can also send private feedback to conduct-discussion(a)wikimedia.org .
I really appreciate your participation.
Thanks again,
Matt Flaschen
Hi everyone, a friendly reminder that if you would like to share your
perspective on the draft statement of purpose
<https://www.mediawiki.org/wiki/Design/Statement_of_purpose>, please do so
no later than this coming Sunday, 27 November, 2016.
Big thanks to everyone who has been a part of the discussion so far :)
On Thu, Nov 10, 2016 at 10:40 AM Keegan Peterzell <kpeterzell(a)wikimedia.org>
wrote:
> Hello all,
>
> Over the past few months the Design team members at the Wikimedia
> Foundation (user experience [UX] designers, design researchers, user
> experience engineers, and communications) have been working with Arthur
> Richards from the Team Practices Group to identify the high-level themes
> that motivate design at the WMF. These themes have been turned into a brief
> statement of purpose, whose intent is to articulate the vision and purpose
> behind design at the WMF. This statement will influence the future
> direction of design work.
>
> At this point the stakeholders are ready for a review of the draft
> statement. The purpose of this review is to gather a common understanding
> of its purpose, and to identify any key themes that may be missing from the
> high-level discussion. On the wiki page for the statement, you'll find
> these themes and what they encompass in the "Background" section. If you
> have an observation, comment, or concern about what is listed there, please
> bring it up on the talk page. If it is relevant to the review and
> understanding of the statement, it will be looked at for future drafts. If
> there are comments about design and the design process in general, we'll
> hold on to those until a time when they can be addressed for the broader
> discussion of design in general.
>
> All that said, here are the links:
> * <https://www.mediawiki.org/wiki/Design/Statement_of_purpose>
> * <https://www.mediawiki.org/wiki/Talk:Design/Statement_of_purpose>
>
> We look forward to seeing you on the wiki.
> --
> Keegan Peterzell
> Technical Collaboration Specialist
> Wikimedia Foundation
> _______________________________________________
> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
> New messages to: Wikimedia-l(a)lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> <mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe>
Forwarding in case you're not subscribed to the other lists.
Please feel welcome to participate in the discussion.
Volker Eckl
Sr. User Experience Engineer
Wikimedia Foundation
---------- Forwarded message ----------
From: Keegan Peterzell <kpeterzell(a)wikimedia.org>
Date: Thu, Nov 10, 2016 at 10:40 AM
Subject: [Wikitech-l] Invitation to review: Design Statement of Purpose
To: wikimediaannounce-l(a)lists.wikimedia.org, Wikimedia developers <
wikitech-l(a)lists.wikimedia.org>
Cc: Wikimedia Mailing List <wikimedia-l(a)lists.wikimedia.org>
Hello all,
Over the past few months the Design team members at the Wikimedia
Foundation (user experience [UX] designers, design researchers, user
experience engineers, and communications) have been working with Arthur
Richards from the Team Practices Group to identify the high-level themes
that motivate design at the WMF. These themes have been turned into a brief
statement of purpose, whose intent is to articulate the vision and purpose
behind design at the WMF. This statement will influence the future
direction of design work.
At this point the stakeholders are ready for a review of the draft
statement. The purpose of this review is to gather a common understanding
of its purpose, and to identify any key themes that may be missing from the
high-level discussion. On the wiki page for the statement, you'll find
these themes and what they encompass in the "Background" section. If you
have an observation, comment, or concern about what is listed there, please
bring it up on the talk page. If it is relevant to the review and
understanding of the statement, it will be looked at for future drafts. If
there are comments about design and the design process in general, we'll
hold on to those until a time when they can be addressed for the broader
discussion of design in general.
All that said, here are the links:
* <https://www.mediawiki.org/wiki/Design/Statement_of_purpose>
* <https://www.mediawiki.org/wiki/Talk:Design/Statement_of_purpose>
We look forward to seeing you on the wiki.
--
Keegan Peterzell
Technical Collaboration Specialist
Wikimedia Foundation
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Hello all,
I’m writing to this list on behalf of the Wikimedia Foundation’s Support &
Safety team <https://meta.wikimedia.org/wiki/Support_and_Safety> (SuSa).
One of the team's annual plan goals is to introduce new, translatable,
online training modules to help functionaries and affiliates better manage
issues.[1]
The Support & Safety team have begun working with
<https://meta.wikimedia.org/wiki/Training_modules> the community on Meta
wiki to discuss what the content and design of these modules should look
like, but I wanted to reach out specifically to this list because you all
are a valuable potential design expertise resource!
If you are interested in the design of these training modules, please visit
the Meta page here
<https://meta.wikimedia.org/wiki/Training_modules/Design_ideas>, which
describes some of our design concerns, and consider joining the discussion on
its talk
<https://meta.wikimedia.org/wiki/Talk:Training_modules/Design_ideas> page
to contribute your own thoughts.
If you have any questions or concerns, please feel free to ask them on
Meta’s module pages, or by emailing me at this address or my entire team at
ca(a)wikimedia.org.
Thank you for your time!
[1] Preceding sentence shamelessly copied-and-adapted from the text SuSa
wrote for the main Training Modules page
<https://meta.wikimedia.org/wiki/Training_modules>, because it does a very
efficient job of explaining what I'm talking about!
Sincerely,
Karen Brown
Community Advocate
Wikimedia Foundation Support & Safety team
--
Karen Brown
Community Advocate
Wikimedia Foundation
kbrown(a)wikimedia.org
Wikimedia is among the 17 organizations in Google Code-in (GCI) 2016!
GCI starts on November 28th. It's a contest for 13-17 year old students
working on small tasks and a great opportunity to let new contributors
make progress and help with smaller tasks on your To-Do list!
There are currently 19 open design tasks marked as easy:
https://phabricator.wikimedia.org/maniphest/query/_xoOHrMKoJ8m/#R
What we want you to do:
BECOME A MENTOR:
1. Go to https://www.mediawiki.org/wiki/Google_Code-in_2016 and add
yourself to the mentor's table.
2. Get an invitation email to register on the contest site.
PROVIDE SMALL TASKS:
We want your tasks in the following areas: code, outreach/research,
documentation/training, quality assurance, user interface/design.
1. Create a Phabricator task (which would take you 2-3h to complete) or
pick an existing Phabricator task you'd mentor.
2. Add the "Google-Code-In-2016" project tag.
3. Add a comment "I will mentor this in #GCI2016".
Looking for task ideas? Check the "easy" tasks in Phabricator:
https://www.mediawiki.org/wiki/Annoying_little_bugs offers links.
Make sure to cover expectations and deliverables in your task.
And once the contest starts on Nov 28, be ready to answer and review
contributions quickly.
Any questions? Just ask, we're happy to help.
Thank you for your help broadening our contributor base!
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/