Under the tag of WP:BOLD I took the liberty of copying the "Page security extension disclaimer" that is put on extension pages whenever an extension uses a legit hook like "usercan" .
While I get why the disclaimer is added, the words used in the disclaimer are certainly up for improvements.
It now states, whenever you need security, use another package, not MediaWiki. It also brands an extension using legit hooks to be a hack.
So I made a simple template "Page security extension disclaimer 2021" that still shares the sames bottomline message : "MediaWiki is not responsible for exposed content", but using words that are more appropriate.
I would like people to review the original disclaimer and the text I have used to come up with a suitable solution.
This is a belated summary of *last week*'s deployment of the 1.37.0-wmf.4
train. The primary train conductor for the week was Brennen Bearnes, with
Lars Wirzenius as backup in European timezones and considerable assistance
from Ahmon Dancy.
The blocker task for the week was: https://phabricator.wikimedia.org/T281145
== Stats ==
* 422 patches
* 2 risky patches identified
* 1 rollback
* 19 hours spent rolled back
* group2 was delayed by 1 day
* 10 train blockers were added, 6 were resolved, 4 were determined to not
be blockers
== 🚂😻 ==
It takes a village[0] to release a train. Thank you to the folks that
helped us this past week:
* Marius Hoch
* DannyS712
* Petr Pchelko
* Tim Starling
* Eric Gardner
* The inimitable Timo Tijhof
* The one and only James Forrester
* Majavah
* RhinosF1
* Urbanecm
* AntiCompositeNumber
And anyone else whose brain was occupied by thoughts of the train this past
week: thanks and sorry.
XOXO
– Train Gang
[0]: <https://en.wikipedia.org/wiki/It_takes_a_village>
Hi all,
The 1.37.0-wmf.5[0] train is currently blocked at group0 by the
following issue:
* Wikimedia\Rdbms\DBQueryError: Error 1048: Column 'gt_page_id' cannot
be null (db1138)Function: GeoData\Hooks::doLinksUpdateQuery: INSERT
INTO `geo_tags`
(gt_page_id,gt_id,gt_lat,gt_lon,gt_globe,gt_primary,gt_dim,gt_type,gt_name,gt_country,gt_region)
VALUES
(NULL,NULL,'45.811666666667','4.9194444444444','earth',1,1000,'camera',NULL,NULL,NULL)
- https://phabricator.wikimedia.org/T282735
If this issue is resolved before the 19:00 UTC train deployment window,
the train will proceed as normal to group1.
As ever, you can follow train progress on Freenode's
#wikimedia-operations as well as on the blocker task[0].
Regards,
-- Your lovely train crew
[0]. <https://phabricator.wikimedia.org/T281146>
[1]. <
https://wikitech.wikimedia.org/wiki/Deployments/Holding_the_train#Issues_th…>
https://www.mediawiki.org/wiki/Scrum_of_scrums/2021-05-12
= 2021-05-12 =
== Callouts ==
* …
Fundraising-Tech => Releng
* a little help from releng to push through an update to our CivCRM CI job
would be hugely appreciated! Patch is here
https://gerrit.wikimedia.org/r/c/integration/config/+/688350/
== Gerrit patches or GitHub Pull Requests for reviews or feedback ==
*
=== No updates ===
CommTech, AHT, Editing, Growth, iOS, Android, Parsing, Language, Analytics,
Cloud Services, Platform, Performance, Security
== SoS Meeting Bookkeeping ==
* Updates:
** future of the synchronous meeting
== Product ==
=== Web ===
* Blocked by:
* Blocking:
* Thank yous:
** Belated thanks to Sam Reed for submitting the Voice & Tone issues, e.g.
https://phabricator.wikimedia.org/T277955
* Updates:
** Prep for the language switcher treatment A/B test
** Started work on the new user links (personal tools) treatment:
https://phabricator.wikimedia.org/T266536
** QA'ing/analysing data from the search autocomplete widget treatment A/B
test
=== Product Infrastructure ===
* Blocked by:
** Need input from Language Team on
https://phabricator.wikimedia.org/T277059#6976371
* Blocking:
* Thank yous:
* Updates:
=== Structured Data ===
* Blocked by:
* Blocking:
* Thank yous:
* Updates:
** No significant updates, continuing to make improvements to MediaSearch
and to work on the image recommendations testing tool
=== Abstract Wikipedia ===
* Blocked by:
** None.
* Blocking:
** None known.
* Thank yous:
* Updates:
** We finished Phase δ (delta) this week; hurrah.
** Now working on Phase ε (epsilon) – wiring up user-written code to the
evaluator: https://meta.wikimedia.org/wiki/Abstract_Wikipedia/Phases
** Security & Performance reviews scheduled to end this Phase; our thanks
to them!
=== Inuka ===
* Blocked by:
* Blocking:
* Thank yous:
* Updates:
** Working on the Wikipedia Preview Wordpress Plugin:
https://phabricator.wikimedia.org/T278383
** Improving Wikipedia Preview gallery feature:
https://phabricator.wikimedia.org/T269787
=== Library ===
* Blocked by:
* Blocking:
* Thank yous:
* Updates:
** The Wikipedia Library Extension is now live on Beta!
** Finished work on making tags translatable, we just need to add extra
configuration on TranslateWiki
** Finished setting up Matomo
** Starting work on the Library homepage redesign
=== Vue.js ===
* Blocked by:
* Blocking:
* Thank yous:
* Updates:
** Rethinking the Icon component in WVUI (
https://phabricator.wikimedia.org/T282625)
** Working on a Radio component and introducing the composition API plugin
to WVUI (https://phabricator.wikimedia.org/T281186)
== Technology ==
=== Fundraising Tech ===
* Blocked by:
** a little help from releng to push through an update to our CivCRM CI job
would be hugely appreciated! Patch is here
https://gerrit.wikimedia.org/r/c/integration/config/+/688350/
* Blocking:
* Thank yous:
* Updates:
** Deployed new email preferences center wiki
** Started integration work for backup processor's new API
=== Engineering Productivity ===
==== Quality and Test Engineering ====
* Blocked by:
* Blocking:
* Thank yous:
* Updates:
** Blog post by John Bolorinos - Improvements to Email QA
https://phabricator.wikimedia.org/phame/post/view/239/improvements_to_email…
==== Release Engineering ====
* Blocked by:
** Web: Upgrading or dropping the legacy Ruby selenium jobs in MinervaNeue
blocks the CI-wide upgrade from stretch to buster. T280901
** Wikibase: Upgrading or dropping the legacy Ruby selenium jobs in
Wikibase blocks the CI-wide upgrade from stretch to buster. T280491
* Blocking:
* Thank yous:
** Thank you to C. Scott for his support and patience waiting for T271863
to be resolved!
* Updates:
** [All] Deployments/Covid-19
https://wikitech.wikimedia.org/wiki/Deployments/Covid-19
** Train Health
*** Last week: 1.37.0-wmf.4 [[phab:T281145]] <!--
https://phabricator.wikimedia.org/T281145 -->
*** This week: 1.37.0-wmf.5 [[phab:T281146]] <!--
https://phabricator.wikimedia.org/T281146 -->
*** Next week: 1.37.0-wmf.6 [[phab:T281147]] <!--
https://phabricator.wikimedia.org/T281147 -->
=== Search Platform ===
* Blocked by:
* Blocking:
* Thank yous:
* Updates:
** Data missing from WCQS - https://phabricator.wikimedia.org/T280022
** Get baseline measurements/expectations for splitting lexemes from
Wikidata graph - https://phabricator.wikimedia.org/T275068
=== Site Reliability Engineering ===
* Blocked by:
** None
* Blocking:
** None
* Thank yous:
* Updates:
** work on getting mw in k8s picking up, shellbox soon to be deployed.
=== WMDE Technical Wishes ===
* Blocked by:
** by a failing reportupdater query,
https://phabricator.wikimedia.org/T273748#7051951
* Blocking:
* Thank yous:
* Updates:
** Reference Previews deployment in some wikis was successful:
https://phabricator.wikimedia.org/T271206
** Suggested Values feature (TemplateData) enabled everywhere:
https://phabricator.wikimedia.org/T273857
** Currently working on template search improvements:
https://phabricator.wikimedia.org/T271802
== Cross-cutting ==
* Blocked by:
** [long term] Search Platform: PHP 8.0 work is long-term blocked on the
migration to ElasticSearch 7.0 https://phabricator.wikimedia.org/T263142
(or at least 6.7).
* Blocking:
** None known.
* Thank yous:
* Updates:
** REL1_36 release process:
*** 1.36 RC.0 was released. Only a small handful of bugs found so far, all
now fixed. If you have a release blocker, please file it urgently:
https://phabricator.wikimedia.org/tag/mw-1.36-release/
** CI tools:
*** mediawiki-codesniffer v36 upgrade going slowly (lots of manual fixes);
67% of repos updated so far.
*** CI tools' upgrade status:
https://libraryupgrader2.wmcloud.org/status?branch=master
** PHP 8.0:
*** No changes this week.
*** Our target is REL1_35 (and thus also REL1_36), as well as master.
*** Upstream libraries: Elastica-related PHP code is theoretically the last
one.
*** Core: Some unit and integration tests still fail; thank you to everyone
working on fixing them.
[[Category:Scrum of scrums{{#translation:}}|*]]
Hello,
I am a maintainer of a third-party wiki and the wiki is run on a machine with restricted resources. Our wiki is running its own Mathoid on the same machine and has a demand for Citoid.
Recently, I have known the REST API of Wikimedia is open to the public[1]. I wonder if the public API is available and the usage is encouraged for third-party wikis like instant commons[2]. If so, I would make a plan to replace the Mathoid run on our machine with Wikimedia's one and add support for Citoid.
Best regards,
lens0021
[1]: https://en.wikipedia.org/api/rest_v1/
[2]: https://www.mediawiki.org/wiki/InstantCommons
Hello all,
The Wikimedia hackathon
<https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2021> is coming up in a
few weeks, on May 22-23! We’re very excited to gather online with you all
and hack together.
On top of the informal hacking, we would like to build a light, community
powered program, with sessions and discussions about the technical
environment in the Wikimedia movement. We will have two different “tracks”,
each of them having its own setup:
1.
The main track, a livestream of sessions that will be recorded and
available for replay, hopefully using a fully open source set up. This will
be great for presentations, talks and demos.
2.
The open rooms: two Jitsi rooms will be available to schedule your
sessions. This is perfect for informal discussions, Q&As and workshops.
If you’re interested in running a session in the hackathon’s program, it’s
easy: please create a task on the Phabricator board
<https://phabricator.wikimedia.org/project/board/5303/>, using this template
<https://phabricator.wikimedia.org/maniphest/task/edit/form/1/?title=[Sessio…>,
that will give you all the required information. The coordination team will
come back to you to help you prepare and schedule your session.
You will also find the different formats that we are offering:
presentation, discussion, workshop or lightning talk. All topics are
welcome, as long as they are connected to the technical environment of the
Wikimedia projects. We are particularly interested in sessions that are
useful for newcomers, and connected to the main topics of this year’s
hackathon: open source tools for events, documentation and finding
co-maintainers.
Because we will need some time to schedule the proposed sessions and to
make technical tests with the speakers, please note that the deadline to
submit a session for the main track is May 9th. For the open rooms, you
will have a bit more time, until May 19th.
You will find more information and details about the call for proposals on
the how-to page
<https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2021/How_to>. If you
have any questions, feel free to ask on the discussion page
<https://www.mediawiki.org/wiki/Talk:Wikimedia_Hackathon_2021>. If you want
to brainstorm ideas or find a co-speaker for your session, feel free to ask
the crowd on the hackathon social channels
<https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2021/Discussions>.
Feel free to share the word anywhere you find it useful, and talk about it
with your contacts! Thanks in advance,
For the coordination team,
--
Léa Lacroix
Community Engagement Coordinator
Wikimedia Deutschland e.V.
Tempelhofer Ufer 23-24
10963 Berlin
www.wikimedia.de
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/029/42207.
Hi all,
Would you like to get more people taking part in the Wikimedia Foundation’s
Board of Trustees election?
The Wikimedia Foundation Board of Trustees announced the plan for the 2021
Board elections
<https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Board_noticeboard/2021…>.
That plan includes outreach and communication support for the Board
elections. The Board election facilitators will:
- Inform communities of the trustee selection process
- Invite communities to engage in voting
- Encourage people representing emerging Wikimedia communities to run as
candidates
Voter turnout in prior elections was about 10% globally. It was better in
communities with volunteer election support. Some of those communities
reached over 20% voter turnout. We know we can get more voters to help
assess and promote the best candidates, but to do that, we need your help.
We are looking for volunteers to serve as Election Volunteers. Election
Volunteers should have a good understanding of their communities. The
facilitation team sees Election Volunteers as doing the following:
- Promote the election in their communities’ channels
- Organize discussions about the election in their communities
- Translate messages for their communities
*Who are the Election Volunteers to connect your community with this
movement effort? Is it you? Or someone you know?* *Check out more details
about Election Volunteers*
<https://meta.wikimedia.org/wiki/Wikimedia_Foundation_elections/2021/Electio…>
and
add your name next to the community you will support in this table
<https://meta.wikimedia.org/wiki/Wikimedia_Foundation_elections/2021/Electio…>
or get in contact with a facilitator
<https://meta.wikimedia.org/wiki/Wikimedia_Foundation_elections/2021#Team>.
We aim to have at least one Election Volunteer for Wiki-projects in the top
30 for eligible voters. Even better if there are two or more sharing the
work.
Best,
Krishna Chaitanya
Communications Facilitator, Board Governance