[x-posted]
Hello,
The Wikimedia Language Engineering team will be hosting the next
monthly IRC office hour on Wednesday, May 21 2014 at 1700 UTC on
#wikimedia-office. The event is delayed this month as the team was
traveling.
In this office hour we will be discussing about our recent work, which
has mostly been around the upcoming first release of the Content
Translation tool[1]. We will also be taking questions during the
session.
Please see below for event details and local time. See you at the office hour.
Thanks
Runa
[1] https://www.mediawiki.org/wiki/Content_translation
Monthly IRC Office Hour:
==================
# Date: May 21, 2014 (Wednesday)
# Time: 1700 UTC/1000PDT (Check local time:
http://www.timeanddate.com/worldclock/fixedtime.html?iso=20140521T1700)
# IRC channel: #wikimedia-office
# Agenda:
1. Content Translation project updates
2. Q & A (Questions can be sent to me ahead of the event)
--
Language Engineering - Outreach and QA Coordinator
Wikimedia Foundation
Hello everyone!
I just merged a change into the new wikibugs that will help reduce
botspam on #wikimedia-dev. wikibugs will no longer report bugs on
#wikimedia-dev that have been reported in other channels, thus
reducing duplication. The previous behavior was that wikibugs will
ping multiple channels - mobile bugs went to both #wikimedia-mobile
and #wikimedia-dev, flow bugs to both #wikimedia-corefeatures and
#wikimedia-dev, etc. Now they only go to the primary channel and
bypass -dev. So mobile bugs will only go to #wikimedia-mobile, and not
to #wikimedia-dev. This also matches the behavior of grrrit-wm.
#mediawiki-feed still gets the full firehose of all changes, if you
are interested in that.
Thanks!
--
Yuvi Panda T
http://yuvi.in/blog
Hi all, your thoughts would be appreciated on
this. It would be great to get some input from tech-focused contributors. I started the thread only on Wikimedia-l to keep the discussion
consolidated in one place.
http://lists.wikimedia.org/pipermail/wikimedia-l/2014-May/071811.html
Thanks,
Pine
This is a casual request for comments about the use of 3rd party
authentication providers for our future Wikimedia Phabricator instance.
Wikimedia Phabricator is expected to replace Bugzilla, Gerrit and many
other tools, each of them having their own registration and user account.
The plan is to offer Wikimedia SUL (your Wikimedia credentials) as the
default way to login to Phabricator -- details at http://fab.wmflabs.org/T40
However, Phabricator can support authentication using 3rd party providers
like GitHub, Google, etc. You can get an idea at
https://secure.phabricator.com/auth/start/
There are good reasons to plan for Wikimedia SUL only (consistency with the
rest of Wikimedia projects), and there are good reasons to plan for other
providers as well (the easiest path for most first-time contributors).
What do you think? Should we offer alternatives to Wikimedia login? If so,
which ones?
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
I've addressed the feedback I got in Zurich.
https://www.mediawiki.org/wiki/Performance_guidelines
I think this page is ready to have the {{draft}} tag removed. I believe
it now represents our consensus on what MediaWiki core, extensions, and
gadgets developers should do to preserve high performance. On May 23,
I'd like to move forward with making a tutorial and a poster based on
this. So, please edit, speak up, and so on, within the next week.
--
Sumana Harihareswara
Senior Technical Writer
Wikimedia Foundation
One of these feel-good emails:
Thanks to the people who are working hard on developing the new search:
Nik, Chad, Dan, and everybody who helps, tests, deploys and writes feedback.
A Hebrew Wikipedia user wrote a big and detailed thank you note[1] that
wiki's Village Pump, especially praising the instant indexing of
newly-added content.
The users are not just complaining all the time? :)
[1] http://j.mp/1g8XylW , at least until it's archived. Thanks in advance
to the people who are developing Flow, which should finally make links to
discussions permanent.
--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
“We're living in pieces,
I want to live in peace.” – T. Moore
Chad wrote:
>On Fri, May 16, 2014 at 4:38 PM, MZMcBride wrote:
>> I suppose you could rely only on global (in the CentralAuth extension
>> sense) accounts, but it really would make sense for Wikimedia to get its
>> own house in order first: we should finish fully unifying login across
>> Wikimedia wikis before delving into concurrent authentication systems.
>
>Yes, let's please. But that's another thread.
All right. What's the status of fully unified login across Wikimedia wikis?
https://meta.wikimedia.org/wiki/SUL_finalisation was marked historical in
January, but that's probably not right.
As far as I'm concerned, the ability to easily rename global wiki accounts
(or accounts across all Wikimedia wikis) and a long warning window prior
to forcible account renames both seem like hard prerequisites, but the
former is still in development and the latter hasn't been started. I
imagine this can't be done in 2014, so possibly 2015?
MZMcBride
---------- Forwarded message ----------
From: Jared Zimmerman <jared.zimmerman(a)wikimedia.org>
Date: Mon, May 12, 2014 at 1:05 AM
Subject: Abigail Ripstra joins the the User Experience team
To: wmfall(a)lists.wikimedia.org
Cc: Abbey Ripstra <aripstra(a)wikimedia.org>
Everyone,
Its my great pleasure to welcome *Abigail Ripstra* to the User Experience
team. Most recently she was working as a Design & Usability Research
Analyst at Salesforce. She is excited to be part of the Wikimedia
Foundation’s mission and ongoing task of sharing knowledge and enabling our
users to more easily do so.
*Abigail joins Wikimedia Foundation as User Researcher Lead*, and will be
working with all product teams to help build and extend our ability to do
impactful qualitative research as part of our product development cycle.
She will not only grow the research team but help train all of us to do
research in a way that is consistent, useful, neutral, and most
importantly, effective in enabling decision making. In time we'll look to
Abigail to extend the team not only through hires but also through the
creation of a research internship program in collaboration with the
Grantmaking & Analytics teams modeled after the success of the legal
internship program. Our goals for qualitative research is that it can begin
to help shape our product roadmaps as well as validate and inform our
decision making processes.
Abigail has worked as a design researcher at Cisco Systems and Salesforce
collaboratively defining, testing, and iterating software functionality for
communication and collaboration. She worked at Steelcase to understand the
context, goals and needs of remote, distributed team mates. She has also
worked with a few design consultancies on various projects. For the past 11
years, she has been studying observing, researching and defining products
for people to collaborate and communicate. In a previous life, Abigail ran
her own business as a muralist, sign painter and decorative artist in
Chicago, and had several apprenticeships in graphic printmaking.
When not at work she travels the world to satisfy her curiosity about how
people communicate and collaborate in and among various political,
technological, geographic, cultural and social contexts around the world.
She is an artist and continues to paint canvases and make drawings and
prints (with ink and paint). She’s also into cooking, yoga, running on the
beach, riding a bike to get around and having adventures with friends and
family.
Abigail will be sitting with my team in the Northwest corner of the 3rd
floor, please come and introduce yourself.
Jared Zimmerman
Director of User Experience
*Jared Zimmerman * \\ Director of User Experience \\ Wikimedia Foundation
M : +1 415 609 4043 | : @JaredZimmerman<https://twitter.com/JaredZimmerman>