[Wikitech-l] Production Excellence #33: June 2021

2021-07-13 Thread Krinkle 
How’d we do in our strive for operational excellence last month?
Incidents

3 documented incidents. That's lower than June in the previous five years
where the month saw 5-9 incidents. I've added a new panel ⭐️ to the Incident
statistics  tool. This one plots
monthly statistics on top of previous years, to more easily compare them.

Learn more from the Incident documents
 on Wikitech, and
remember to review and schedule Incident Follow-up
 in Phabricator,
which are preventive measures and other action items filed after an
incident.

---
Trends

In June, work on production errors appears to have stagnated a bit. Or more
precisely, the work only resulted in relatively few tasks being resolved.
15 of the 26 new tasks are still open as of writing.

Of the tasks from previous months, only 11 were resolved, leaving most
columns unchanged. See the table further down for a more detailed breakdown
and links to Phabricator queries for the tasks in question.

With the 15 remaining new tasks, and the 11 tasks resolved from our
backlog, this raises the chart from 150 to 154 tasks.

Figure 1, Figure 2: Unresolved error reports stacked by month.


Month-over-month plots based on spreadsheet data

.

---
Outstanding errors

Take a look at the workboard and look for tasks that could use your help.
→  https://phabricator.wikimedia.org/tag/wikimedia-production-error/


Summary over recent months:
Jan 2020 (1 of 7 left) ⚠️ Unchanged (over one year old).
Mar 2020 (2 of 2 left) ⚠️ Unchanged (over one year old).
Apr 2020 (4 of 14 left) ⚠️ Unchanged (over one year old).
May 2020 (5 of 14 left) ⚠️ Unchanged (over one year old).
Jun 2020 (5 of 14 left) ⚠️ Unchanged (over one year old).
Jul 2020 (4 of 24 issues) ⚠️ Unchanged (over one year old).
Aug 2020 (11 of 53 issues) ⬇️ One task resolved. -1
Sep 2020 (7 of 33 issues) ⚠️ Unchanged (over one year old).
Oct 2020 (19 of 69 issues) ⚠️ Unchanged (over one year old).
Nov 2020 (8 of 38 issues) ⚠️ Unchanged (over one year old).
Dec 2020 (7 of 33 issues) ⚠️ Unchanged (over one year old).
Jan 2021 (3 of 50 issues
) ⚠️
Unchanged (over one year old).
Feb 2021 (6 of 20 issues
) ⬇️ One
task resolved. -1
Mar 2021 (13 of 48 issues
) ⬇️ One
task resolved. -1
Apr 2021 (19 of 42 issues
) ⬇️
Four tasks resolved. -4
May 2021 (25 of 54 issues
) ⬇️
Four tasks resolved. -4
June 2021 (15 of 26 issues
) 📌 26
new issues, of which 11 were closed. +26, -11

---
Tally
150 issues open, as of Excellence #32 (May 2021)

.
-11 issues closed, of the previous 150 open issues.
+15 new issues that survived June 2021.
154 issues open as of yesterday.

---
Thanks!

Thank you to everyone who helped by reporting, investigating, or resolving
problems in Wikimedia production. Thanks!

Until next time,

– Timo Tijhof


🔗 Share or read later via
https://phabricator.wikimedia.org/phame/post/view/240/
___
Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/

[Wikitech-l] Re: Why does the train start on Tuesday?

2021-07-13 Thread Mukunda Modell 
You can already opt in to testing undployed code by using the
WikimediaDebug[1] browser extension (available for firefox[2] and chrome[3])

Maybe we should add an option to force a request to be served from the
latest branch instead of the one assigned in wikiversions.json.

[1] https://wikitech.wikimedia.org/wiki/WikimediaDebug
[2] https://addons.mozilla.org/en-US/firefox/addon/wikimedia-debug-header/
[3]
https://chrome.google.com/webstore/detail/wikimediadebug/binmakecefompkjggiklgjenddjoifbb


On Tue, Jul 13, 2021 at 12:21 AM Jeremy Baron  wrote:

> This makes me wonder if there could ever be a way to allow some requests
> to be on one group and other requests for the same wiki could be another
> group.
>
> e.g. users could opt-in to being a canary or some users could be randomly
> selected.
>
> When would this not work? If a newer version required schema change then
> have to stop using old version after applying new schema? but that isn't
> very common? any other complications?
>
> -Jeremyb
> ___
> Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
> To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
> https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
___
Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/

[Wikitech-l] Fwd: [Wikimedia-l] Wikimedia Foundation annual plan published

2021-07-13 Thread Mehrdad Pourzaki 
Hi everyone,

Platform evolution is one of three priority areas for the Wikimedia
Foundation for fiscal year 21-22. Some of you took part in related
discussions in December and January, such as around improving user
experience. There are interesting product and technology developments in
the pipeline — including great work that will continue from this year to
next and new streams of work to better support a thriving movement and
respond to a rapidly-changing world of technology. Inviting you to read
more about the Foundation's Annual Plan on Diff

and
to attend related conversations with the Product and Technology
departments, as well as others, when they happen soon.

Please see below from Wikimedia-l. Apologies for cross-posting.

Regards,
Mehrdad



*Mehrdad Pourzaki*
Senior Movement Communications Specialist
wikimediafoundation.org

*"By 2030, Wikimedia will become the essential infrastructure of the
ecosystem of free knowledge, and anyone who shares our vision will be able
to join us." *

Hello everyone,

The Wikimedia Foundation Annual Plan for this fiscal year - which runs from
July 1, 2021 until June 30, 2022 - is now published. You can read an
overview of the Annual Plan on Diff

[1], and review the full Annual Plan and its supporting materials,
including videos, on our Meta-Wiki
page.
[2] Translations of the Meta page and video subtitles into Arabic, Chinese,
French, German, Russian, and Spanish are underway and will be completed in
the next few days. The Foundation’s executive team will also be hosting a
series of live Annual Plan Conversations

at the end of the month to answer questions from communities. [3] An update
about the Annual Plan Conversations will be shared here next week.

Best,

Kelsi Stine-Rowe

Senior Project Manager

Wikimedia Foundation 

[1]
https://diff.wikimedia.org/2021/07/13/wikimedia-foundation-fy21-22-annual-plan/

[2]
https://meta.wikimedia.org/wiki/Special:MyLanguage/Wikimedia_Foundation_Medium-term_plan_2019/Annual_Plan_2021-2022

[3]
https://meta.wikimedia.org/wiki/Special:MyLanguage/Wikimedia_Foundation_Medium-term_plan_2019/Annual_Plan_2021-2022#Annual_Plan_Conversations


-- 

Kelsi Stine-Rowe (she/her)

Senior Project Manager

Wikimedia Foundation 

"Imagine a world in which every single human being can freely share in the
sum of all knowledge. That's our commitment."

___
Wikimedia-l mailing list -- wikimedi...@lists.wikimedia.org, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at
https://lists.wikimedia.org/hyperkitty/list/wikimedi...@lists.wikimedia.org/message/3325TG7636D2S4COA2BLBTLNCUGILFBJ/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org
___
Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/

[Wikitech-l] Upcoming parser HTML changes for media: Test your scripts, gadgets, bots, extensions

2021-07-13 Thread Arlo Breault 
Hello all,

We'd like to inform you of a change coming in how media is structured in the 
parser's HTML output.  It has been [in the works for quite some time][1].  The 
new structure was prototyped in Parsoid's output since its inception and 
outlined in [its specification][2].

The proposed change has gone through the [RFC process][3] and an implementation 
to output this new structure in MediaWiki's core parser was [recently 
merged][4], gated behind a flag.  So far, it has been enabled on testwiki and 
testwiki2.

There are [a number of known issues][5] but we don't expect to see many 
rendering differences since we've done some [extensive visual diff testing][6]. 
 Templates won't be impacted; the old CSS styles will remain, for now.

However, where we do expect work is needed is with code interacting with the 
page, be it user scripts, gadgets, extensions, bots, or other things.

If you'd like to help us out and get ahead of the changes before they have the 
potential to interfere with your workflow, please visit these wikis and test 
them out.  You can file tasks in Phabricator with the Parsoid-Media-Structure 
project tag.

Thanks,
The Parsing Team


[1]: https://www.mediawiki.org/wiki/Parsing/Media_structure
[2]: https://www.mediawiki.org/wiki/Specs/HTML/2.2.0#Media
[3]: https://phabricator.wikimedia.org/T118517
[4]: https://gerrit.wikimedia.org/r/c/mediawiki/core/+/507512
[5]: https://phabricator.wikimedia.org/project/board/5428/
[6]: https://phabricator.wikimedia.org/T266149
___
Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org
To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org
https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/