Indeed - thank you Ori on behalf of the entire technical organization.
Dariusz - I'd ask that you consider the assumptions that you listed in your
email more closely. Ori, myself and others would be very happy to work with
you this.
-Toby
On Thursday, February 18, 2016, Moiz Syed <msyed(a)wikimedia.org> wrote:
Wow, thank you Ori. +1 to everything you said.
That line from Dariusz disappointed me to, but I just chalked it up to just
another case of a board member downplaying community/staff concerns and
plea for help.
On Thu, Feb 18, 2016 at 10:33 AM, Ori Livneh <ori(a)wikimedia.org
<javascript:;>> wrote:
On Thu, Feb 18, 2016 at 4:47 AM, Dariusz
Jemielniak <darekj(a)alk.edu.pl
<javascript:;>>
wrote:
> There is way too much blaming/bashing/sour expectations
> working both ways - we almost forget how unique we are, irrespective of
> many slips and avoidable failures we make (and WMF is definitely
leading
here,
too! ;)
No, we're not. My peers in the Technology department work incredibly hard
to provide value for readers and editors, and we have very good results
to
show for it. Less than two years ago it took an
average of six seconds to
save an edit to an article; it is about one second now. (MediaWiki
deployments are currently halted over a 200-300ms regression!). Page load
times improved by 30-40% in the past year, which earned us plaudits in
the
press and in professional circles. The analytics
team figured out how to
count unique devices without compromising user anonimity and privacy and
rolled out a robust public API for page view data. The research team is
in
the process of collecting feedback from readers
and compiling the first
comprehensive picture of what brings readers to the projects. The TechOps
team made Wikipedia one of the first major internet properties to go
HTTPS-only, slashed latency for users in many parts of the world by
provisioning a cache pop on the Pacific Coast of the United States, and
is
currently gearing up for a comprehensive test of
our failover
capabilities,
which is to happen this Spring.
That's just the activity happening immediately around me in the org, and
says nothing of engineering accomplishments like the Android app being
featured on the Play store in 93 countries and having a higher user
rating
than Facebook Messenger, Twitter, Netflix,
Snapchat, Google Photos, etc.
Or
the 56,669 articles that have been created using
the Content Translation
tool.
This is happening in spite of -- not thanks to -- dysfunction at the top.
If you don't believe me, all you have to do is wait: an exodus of people
from Engineering won't be long now. Our initial astonishment at the
Board's
unwillingness to acknowledge and address this
dysfunction is wearing off.
The slips and failures are not generalized and diffuse. They are local
and
specific, and their location has been indicated
to you repeatedly.
_______________________________________________
Wikimedia-l mailing list, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l(a)lists.wikimedia.org <javascript:;>
Unsubscribe:
https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
<mailto:wikimedia-l-request@lists.wikimedia.org <javascript:;>
?subject=unsubscribe>
_______________________________________________
Wikimedia-l mailing list, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l(a)lists.wikimedia.org <javascript:;>
Unsubscribe:
https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
<mailto:wikimedia-l-request@lists.wikimedia.org <javascript:;>
?subject=unsubscribe>