Hey all, the Timeless grant has wrapped up and I've submitted the final
report for the project. Please check it out if you're interested:
https://meta.wikimedia.org/wiki/Grants:Project/Timeless/Post-deployment_sup…
A couple of things to highlight:
* The associated learning pattern is likely going to be relevant to a lot
of us:
https://meta.wikimedia.org/wiki/Learning_patterns/Developing_intercompatibl…
* Part of the purpose of the grant was to investigate into what we would
actually need from a new skin on Wikimedia projects, should anyone
decide to go that route. Here's what we found:
> All we really need from a new skin is for everything that went wrong
> with Minerva and Timeless, as far as readers and editors are concerned,
> to not happen this time:
>
> * We need gadgets to work.
> * We need content to display properly, and tools to be available.
> * We need to properly reuse core interfaces so things remain consistent.
> * We need to not distract users with unnecessary colours and affordances
> that aren't relevant to whatever they're doing, and provide options
> that suit their differing situations and needs.
> * We need to not do dumb things, like reinvent random wheels or ignore
> standard hooks and DOM expectations.
I don't know if that's all that likely to help anyone, but... yeah.
Anyway, I'll still be working on maintenance and some feature development
in a volunteer capacity, mind you, so as always if you run into issues or
whatever, please file them on phabricator or come yell at me! I just make
absolutely no promises whatsoever as to when I (or whoever) will actually
deal with it, but it's still really helpful to at least have them tracked.
https://phabricator.wikimedia.org/tag/timeless/
(See, it's even sort of organised! I even renamed the 'Aaaaaaa' column!)
-I
Hi all,
I am doing an edit-a-thon and I have a strange behaviour with an user.
He allows the use of Oauth for the Dashboard but he does the login and he is
not redirected to the Dashboard. The page remains empty even if he is
logged.
Do you have an idea?
Kind regards
Ilario Valdelli
Hello,
The CoC committee had a meeting with four members out of five (Lucie, Tony,
Tonina, and Amir were at Wikimania and MusikAnimal wasn't present). These
notes are the public outcomes of the meeting.
* The committee chose Amir as the chair (Amir requested to be the table but
it got rejected)
* The committee is currently composing the anonymized report of its cases
and will be published soon.
* The committee soon will decide on the two amendments currently under
discussion. Feel free to comment on these two:
** Public logging of bans:
https://www.mediawiki.org/wiki/Topic:Uikcu1emvmw6e4z8
** Modifications on the appeal process:
https://www.mediawiki.org/wiki/Topic:Uay0vz6no8ayac3m
* The committee is willing to introduce a new internal role which for lack
of better term, we call it secretary for now. The role's main
responsibility is to help the committee on organizational bookkeeping. Like
reports, documentation of cases, etc.
* At the end, the committee wants to remind people that its role is
reactionary and we won't interfere when there's no report. If you see a
behaviour you find unacceptable, stand up and send us a report and don't
wait for the committee to jump in.
Regards,
Amir on behalf of the committee
📘 Read on Phabricator at
https://phabricator.wikimedia.org/phame/post/view/164
-------
How’re we doing on that strive for operational excellence? Read this first
anniversary edition to find out!
#### 📊 Month in numbers
- 5 documented incidents. [1]
- 53 new Wikimedia-prod-error reports. [2]
- 44 closed Wikimedia-prod-error reports. [3]
- 218 currently open Wikimedia-prod-error reports in total. [4]
The number of recorded incidents over the past month, at five, is equal to
the median number of incidents per month (2016-2019). – Explore the data at
https://codepen.io/Krinkle/full/wbYMZK
To read more about these incidents, their investigations, and pending
actionables; check
https://wikitech.wikimedia.org/wiki/Incident_documentation#2019
-------
#### *️⃣One year of Excellent adventures!
Exactly one year ago [5] this periodical started to provide regular
insights on production stability. The idea was to shorten the feedback
cycle between deployment of code that leads to fatal errors and the
discovery of those errors. This allows more people to find reports earlier,
which (hopefully) prevents them from sneaking into a growing pile of
“normal” errors.
576 reports were created between 15 July 2018 and 31 July 2019 (tagged
Wikimedia-prod-error). 425 reports got closed over that same time period.
-------
#### 📉 Outstanding reports
Take a look at the workboard and look for tasks that might need your help.
The workboard lists error reports, grouped by the month in which they were
first observed.
→ https://phabricator.wikimedia.org/tag/wikimedia-production-error/
Or help someone who already started with their patch:
→ https://phabricator.wikimedia.org/maniphest/query/pzVPXPeMfRIz/#R
Breakdown of recent months (past two weeks not included):
- November: 1 report left (unchanged). ⚠️
- December: 3 reports left (unchanged). ⚠️
- January: 1 report left (unchanged).
- February: 2 reports left (unchanged).
- March: 4 reports left (unchanged).
- April: 10 of 14 reports left (unchanged).
- May: 2 reports got fixed! (4 of 10 reports left). ✨
- June: 2 reports got fixed! (9 of 11 reports left). ✨️
- July: 18 new reports from last month remain unsolved.
-------
#### 🎉 Thanks!
Thank you to Aaron Schulz, Ariel Glenn, Brad Jorsch, CScott, Daimona, David
Barratt, David Causse, EBernhardson, Gergő Tisza, James Forrester, Jeena
Huneidi, MarcoAurelio, Roan Kattouw, Stephane Bisson, Tchanders, Tim
Starling, Urbanecm; and everyone else who helped by finding, investigating,
or resolving error reports in Wikimedia production. Thanks!
Until next time,
– Timo Tijhof
-------
Footnotes:
[1] Incidents. –
https://wikitech.wikimedia.org/wiki/Special:PrefixIndex?prefix=Incident+doc…
[2] Tasks created. –
https://phabricator.wikimedia.org/maniphest/query/9m.NNvBAvuHF/#R
[3] Tasks closed. –
https://phabricator.wikimedia.org/maniphest/query/6sekLiUhHCmq/#R
[4] Open tasks.
https://phabricator.wikimedia.org/maniphest/query/47MGY8BUDvRD/#R
[5] The initial e-mail. –
https://lists.wikimedia.org/pipermail/wikitech-l/2018-July/090363.html
Dear all,
I thank you for your efforts. I am managing to begin writing a survey about wiki sites and publish it in an appropriate journal... This survey will involve the software used (Mediawiki or other), the size, reference support, topic... I am looking for contributors to this project. Anyone who has published two papers about wikis in a research journal is invited to join the initiative.
Yours Sincerely,
Houcemeddine Turki (he/him)
Medical Student, Faculty of Medicine of Sfax, University of Sfax, Tunisia
Undergraduate Researcher, UR12SP36
GLAM and Education Coordinator, Wikimedia TN User Group
Member, WikiResearch Tunisia
Member, Wiki Project Med
Member, WikiIndaba Steering Committee
Member, Wikimedia and Library User Group Steering Committee
Co-Founder, WikiLingua Maghreb
Founder, TunSci
_____________________
+21629499418
Hi Community Metrics team,
This is your automatic monthly Phabricator statistics mail.
Accounts created in (2019-07): 290
Active Maniphest users (any activity) in (2019-07): 967
Task authors in (2019-07): 521
Users who have closed tasks in (2019-07): 293
Projects which had at least one task moved from one column to another on
their workboard in (2019-07): 312
Tasks created in (2019-07): 2573
Tasks closed in (2019-07): 2403
Open and stalled tasks in total: 42433
Median age in days of open tasks by priority:
Unbreak now: 2
Needs Triage: 522
High: 944
Normal: 1139
Low: 1552
Lowest: 1531
(How long tasks have been open, not how long they have had that priority)
Active Differential users (any activity) in (2019-07): 12
To see the names of the most active task authors:
* Go to https://wikimedia.biterg.io/
* Choose "Phabricator > Overview" from the top bar
* Adjust the time frame in the upper right corner to your needs
* See the author names in the "Submitters" panel
TODO: Numbers which refer to closed tasks might not be correct, as
described in https://phabricator.wikimedia.org/T1003 .
Yours sincerely,
Fab Rick Aytor
(via community_metrics.sh on phab1003 at Tue Aug 27 14:32:03 UTC 2019)
Hello everyone,
We are looking for a senior full-stack developer to work with us as a
contractor on Scribe.
Scribe is a Wikimedia Foundation funded software and research project. We
are building a tool to support newcomer Wikipedia editors in creating new
articles in under-resourced languages (e.g. Arabic, Hindi). The project is
open-source and will be integrated on low-resource Wikipedias so you will
be working on a great cause of making knowledge accessible to everyone.
Plus your work will have great visibility and impact on the community.
*You:*
We are looking for a senior software engineer contractor to realize the
Scribe project in a part-time position for 9 months starting on the 14th of
October.
You will work remotely with us. We are looking for someone with *3+ years
of experience in Full-stack development and community-focused applications*.
*Your future team:*
The project leads are Lucie and Hady, researchers in Computer Science. So
you will be part of our three-person team and able to influence the project
itself.
Lucie is a PhD researcher at the University of Southampton and TIB
Hannover. She previously worked at Wikimedia Germany. Hady holds a PhD in
Natural Language Processing and Machine Learning and currently works as a
researcher in Naver Labs Europe. We live in France and Germany/UK
respectively, so we are used to working remotely and effective
communication.
*How to apply: *
*Make sure to read the full job description here:*
https://meta.wikimedia.org/wiki/Scribe/Job
Then drop us an email (scribe.wikimedia(a)gmail.com) showing your interest in
the project with your *CV* and *portfolio attached*.
We also appreciate *any other kind of information in any format* that shows
your relevant experience, creativity and problem-solving skills.
Note: Interviews will be scheduled on a first come first served basis until
the position gets filled, so please consider to submit your profile as soon
as possible.
Looking forward to hearing from you,
Lucie-Aimée Kaffee and Hady Elsahar
--
Lucie-Aimée Kaffee
Sorry for cross-posting!
Reminder: Technical Advice IRC meeting this week **Wednesday 3-4 pm UTC**
on #wikimedia-tech.
Questions can be asked in English!
The Technical Advice IRC Meeting (TAIM) is a weekly support event for
volunteer developers. Every Wednesday, two full-time developers are
available to help you with all your questions about MediaWiki, gadgets,
tools and more! This can be anything from "how to get started" over "who
would be the best contact for X" to specific questions on your project.
If you know already what you would like to discuss or ask, please add your
topic to the next meeting:
https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting
Hope to see you there!
--
Raz Shuty
Engineering Manager
Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Phone: +49 (0)30 219 158 26-0
https://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.