Hello potential deployers!
We're starting backport deployment training for people interested in
learning how to deploy safely
<https://commons.wikimedia.org/wiki/File:Framed_%22I_BROKE_WIKIPEDIA..._THEN…>
.
Training happens in the #wikimedia-operations IRC channel as well as in a
Google meet hangout every Thursday at both 11:00 and 23:00 UTC.
If you're interested in becoming a deployer and joining the hangout please
fill out our deployment training request form
<https://phabricator.wikimedia.org/maniphest/task/edit/form/96/> on
Phabricator to signup.
Attendance at multiple training sessions is welcome and encouraged—the goal
is for you to be comfortable doing deployments yourself.
Everyone interested in having their code run in Wikimedia's production
should learn how to deploy! Knowing how to deploy is important to unblock
yourself and to help others in the technical community. The training will
guide you step-by-step through queuing up patches, (in)validating on
MWDebug, rolling back, and pushing live.
For more information see the deployment training guide on Wikitech
<https://wikitech.wikimedia.org/wiki/Deployments/Training>.
đź’–
– Tyler
I saw a note about maintenance but I didn't think it was related to
toolforge - everything on toolforge.org seems to be down right now? When I
try to login I don't see any tools (become 'xxx' says "no such tool")
Arthur
Hello,
I'm once again asking you to vote on a logo. This time is the new Wikitech
logo since its original one was derived from the old MediaWiki logo that
has now changed. You can see this ticket
<https://phabricator.wikimedia.org/T279087> for previous discussion and
proposals of the new wikitech logo.
This time, it's much simpler. Only one round (as they are just variants of
the same logo), For two weeks only and effective immediately afterwards.
You can vote in https://wikitech.wikimedia.org/wiki/Wikitech_logo and
voting is open until 30 April 2021. You can only support up to two logos
(out of five proposed).I recommend reading the ticket before voting.
Thanks
--
Amir (he/him)
Hey all,
This is a quick note to highlight that the REL1_36 branch has now been
created for MediaWiki core and each of the extensions and skins in
Wikimedia git[0]. This is the first step in the release process for
MediaWiki 1.36, which should be out in late May 2021, approximately nine
months after MediaWiki 1.35.
The branches reflect (or are at least very close to) the code as of the
last 'alpha' branch for the release, 1.36.0-wmf.38, which was deployed to
Wikimedia wikis last week for MediaWiki itself and those extensions and
skins available there.
>From now on patches that land in the main development branch of MediaWiki
and its bundled extensions and skins will be slated for the MediaWiki 1.37
release unless specifically backported[1].
If you are working on a critical bug fix that will affect the code in the
release, once the patch has been merged into the development branch, you
should propose it for backporting by cherry-picking to the REL1_36 branch.
If you are working on a new feature, that should now not be backported. If
you have an urgent case where the work should block release for everyone
else, please file a task against the `mw 1.36-release` project on
Phabricator.[2]
If you have tickets that are tagged for `mw-1.36-release`, please finish
them, untag them, or reach out to get them resolved in the next few days.
We hope to issue the first release candidate, 1.36.0-rc.0, in two weeks'
time, and if all goes well, to release MediaWiki 1.36.0 a few weeks after
that.
Thanks!
– Tyler
[0]: <https://www.mediawiki.org/wiki/Bundled_extensions_and_skins>
[1]: <https://www.mediawiki.org/wiki/Backporting_fixes>
[2]: <https://phabricator.wikimedia.org/tag/mw-1.36-release/>
// sorry for cross-posting
Hi all,
another feature will soon make usage of templates easier:
Suggested values for parameters can be added to TemplateData and will be
shown as a drop-down list in VisualEditor. This allows VisualEditor users
to quickly select an appropriate value. Thus, it reduces potential errors
and the effort needed to fill the template with values. It will still be
possible to fill in values other than the suggested ones. More information
can be found on the help page [1] and on the project page. [2]
The WMDE Technical Wishes team plans to deploy this on all wikis on April
29. If you have any feedback, please let us know on the project’s talk
page. [3]
Timur
for the Technical Wishes team
[1] https://www.mediawiki.org/wiki/Help:TemplateData#suggestedvalues
[2]
https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Suggested_values_for_…
[3]
https://meta.wikimedia.org/wiki/Talk:WMDE_Technical_Wishes/Suggested_values…
--
Timur Vorkul
Technische WĂĽnsche
Wikimedia Deutschland e. V. | Tempelhofer Ufer 23–24 | 10963 Berlin
Tel. (030) 219 158 26-0
https://wikimedia.de
Bleiben Sie auf dem neuesten Stand! Aktuelle Nachrichten und spannende
Geschichten rund um Wikimedia, Wikipedia und Freies Wissen im Newsletter: Zur
Anmeldung <https://www.wikimedia.de/newsletter/>.
Unsere Vision ist eine Welt, in der alle Menschen am Wissen der Menschheit
teilhaben, es nutzen und mehren können. Helfen Sie uns dabei!
https://spenden.wikimedia.de
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.
https://www.mediawiki.org/wiki/Scrum_of_scrums/2021-04-21
= 2021-04-21 =
== Callouts ==
*** Cross-cutting: There are five filed blockers to the 1.36 RC.0 release
(due tomorrow), but two are unclaimed and apparently not being worked on:
https://phabricator.wikimedia.org/tag/mw-1.36-release/
* …
== Gerrit patches or GitHub Pull Requests for reviews or feedback ==
*
=== No updates ===
CommTech, Product Infrastructure, Parsing, Language, Analytics, Cloud
Services, Platform, Performance, Quality and Test Engineering, Release
Engineering, Search Platform, Security
== SoS Meeting Bookkeeping ==
* Updates:
== Product ==
=== Anti-Harassment Tools ===
* Blocked by:
* Blocking:
* Thank yous:
** Thanks to Sam Reed and James Forrester for code review and advice
** Thanks to DannyS for huge help on partial blocks review/QA
* Updates:
** We're working on partial blocks against actions while we await next
instructions on SecurePoll
=== Editing ===
* Blocked by:
* Blocking:
* Thank yous:
* Updates:
** Will be working with Performance and others to reduce ParserCache expiry
by ~7 days (30 -> 23) to free up some space, possibly caused by
DiscsussionTools reply links.
=== Growth ===
* Blocked by:
* Blocking:
* Thank yous:
* Updates:
** Continuing work on Add Link https://wikitech.wikimedia.org/wiki/Add_Link
** Preparing to enable on-wiki configuration next week
https://phabricator.wikimedia.org/T274520
** Migrating mentor data from user preferences to a dedicated table
https://phabricator.wikimedia.org/T279853
** Deploying Growth features as opt-in to eswiki
=== iOS native app ===
* Blocked by: N/A
* Blocking: N/A
* Thank yous:
* Updates: Version 6.8 - finally improving language varient support - is
currently rolling out.
=== Android native app ===
* Blocked by: N/A
* Blocking: N/A
* Thank yous:
* Updates: Version w/ image recommendations suggested edits should be
released 2 weeks from today.
=== Web ===
* Blocked by:
* Blocking:
* Thank yous:
* Updates:
** Finishing up Vue.js search autocomplete widget project report:
https://phabricator.wikimedia.org/T249430
** Preparing a release for WVUI to address a handful of bugs:
*** https://phabricator.wikimedia.org/T277256
*** https://phabricator.wikimedia.org/T277315
*** https://phabricator.wikimedia.org/T279088
** Beginning work on the new personal tools treatment for Desktop
Improvements:
https://www.mediawiki.org/wiki/Reading/Web/Desktop_Improvements/Features#Us…
=== Structured Data ===
* Blocked by:
* Blocking:
* Thank yous:
* Updates:
** Building a tool to manually test current implementation of the image
recommendations API
** Whittled down dependencies for the new MediaSearch extension; it now
only requires CirrusSearch
=== Abstract Wikipedia ===
* Blocked by:
** None.
* Blocking:
** None known.
* Thank yous:
* Updates:
** Working on Phase δ (delta):
https://meta.wikimedia.org/wiki/Abstract_Wikipedia/Phases
** Started circulating early draft of our TDMP pitch for asynchronous
parser fragments.
=== Inuka ===
* Blocked by:
* Blocking:
* Thank yous:
* Updates:
** Wikipedia Preview
*** Working on the version information
https://phabricator.wikimedia.org/T278377
*** Working on the debug information
https://phabricator.wikimedia.org/T278381
*** Working on the Wix integration https://phabricator.wikimedia.org/T278456
** Wikipedia KaiOS
*** Optimize the confirmed characters of the search method
https://phabricator.wikimedia.org/T246786
=== Library ===
* Blocked by:
* Blocking:
* Thank yous:
** Language team (Niklas and Abijeet) for helping us get partner
descriptions into TranslateWiki
* Updates:
** You can now translate Wikipedia Library partner descriptions!
https://translatewiki.net/wiki/Special:Translate?group=wikipedia-library-pa…
** Started setting up Matomo to track page views
** Started setting up tags to be translatable via TranslateWiki
** Finishing up The Wikipedia Library extension work
=== Vue.js ===
* Blocked by:
* Blocking:
* Thank yous:
* Updates:
** Starting work to unify button implementations in WVUI and better match
what's in the design style guide (https://phabricator.wikimedia.org/T278509)
** Adding contributing guidelines to WVUI:
https://gerrit.wikimedia.org/r/c/wvui/+/681178/3/contributing.md (under
review)
** Planning long-term migration of projects to Vue
== Technology ==
=== Fundraising Tech ===
* Blocked by:
* Blocking:
* Thank yous:
* Updates:
** More work on email prefs page https://phabricator.wikimedia.org/T268510,
https://phabricator.wikimedia.org/T268511
** Planning for integration with new API of backup card processor
** Work to migrate custom CRM code off drupal 7
** CiviCRM contact deduplication enhancements
** Audit / reconciliation file processing improvements:
https://phabricator.wikimedia.org/T277244,
https://phabricator.wikimedia.org/T265545
=== Site Reliability Engineering ===
* Blocked by:
** None
* Blocking:
** None
* Thank yous:
* Updates:
** 100% of MW appservers now on buster, no more stretch special test hosts,
mwdebug1003 removed
** Gitlab: Performance testing on WMCS done, defining backup and
monitoring, documentation
** The MediaWiki chart can run a php application on kubernetes
https://people.wikimedia.org/~oblivian/mw-on-k8s-shared-socket.png
** Scap logs will be transitioned to ECS 2021-05-04
=== WMDE Technical Wishes ===
* Blocked by:
* Blocking:
* Thank yous:
* Updates:
** Reusable edit count bucketing was accepted and is live for several
extensions.
== 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:
** Huge thanks to the Web team, especially Jon Robson, for their work on
fixing multiple blockers to the 1.36 release.
* Updates:
** REL1_36 release process:
*** [In calls-out] There are five filed blockers to the 1.36 RC.0 release
(due tomorrow), but two are unclaimed and apparently not being worked on:
https://phabricator.wikimedia.org/tag/mw-1.36-release/
** CI tools:
*** Nothing major.
*** Next release of mediawiki-codesniffer likely soon.
*** CI tools' upgrade status:
https://libraryupgrader2.wmcloud.org/status?branch=master
** PHP 8.0:
*** Nothing major.
*** 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! Our team, Wikimedia Germany’s Technical Wishes project [1], is
developing a series of improvements to make working with templates easier.
Maybe you’ve already heard of some of the projects that have recently been
deployed: [2] [3] [4]. We plan to release more improvements to make working
with templates easier over the course of this year:
It will become easier to find templates and to insert them into a page. [5]
Removing a template from a page (with Visual Editor) will become easier. [6]
Several problems with the existing interface for editing templates in the
VisualEditor will be tackled. [7]
Template creators and maintainers will be offered more guidance when they
are managing TemplateData with the template documentation editor. [8]
Now we’re looking for a few wikis who want to be the first to benefit from
these changes. If your wiki community is interested in this, all the
improvements listed above would be deployed to your wiki in a series of
releases, likely between May and July 2021. Of course, each deployment
would be announced beforehand.
We’re hoping for wikis of different sizes, both Wikipedias and sister
projects, and wikis with different scripts and writing directions. The
wikis should use TemplateData and ideally have the VisualEditor as a
default feature.
Is your wiki community interested to have early access to these
improvements? Email me or let me know on my talk page.[9]
Best,
Johanna
[1] Technical Wishes project:
https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes
[2] Bracket matching:
https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Bracket_Matching
[3] Improved color scheme for syntax highlighting:
https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Improved_Color_Scheme…
[4] Line numbering:
https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Line_Numbering
[5] Finding and inserting templates:
https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Finding_and_inserting…
[6] Removing a template from a page using the VisualEditor:
https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Removing_a_template_f…
[7] VisualEditor template dialog improvements:
https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/VisualEditor_template…
[8] TemplateData editor improvements:
https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Template_data_editor_…
[9] talk page:
https://meta.wikimedia.org/wiki/User_talk:Johanna_Strodt_(WMDE)
--
Johanna Strodt
Projektmanagerin Kommunikation Communitys Technische Wunschliste
Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 26-0
https://wikimedia.de
Unsere Vision ist eine Welt, in der alle Menschen am Wissens der Menschheit
teilhaben, es nutzen und mehren können. Helfen Sie uns dabei!
https://spenden.wikimedia.de
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.
Hi,
LibUp can now notify you about new upstream releases in Phabricator. An
example: <https://phabricator.wikimedia.org/T280117>.
It'll check daily to see if an upstream project has a new release, and
if so, file a Phabricator task. If it already filed a task that's still
open, it'll leave a new comment instead.
This is separate from LibUp's library upgrading in Gerrit, so it should
be able to support just about any project and leave it up to the humans
to decide what to do about the new version.
If you'd like to get notifications for your project, file a bug in the
#LibUp Phabricator project, or send a patch to the
labs/libraryupgrader/config Gerrit repository (see README for instructions).
Behind the scenes LibUp is using <https://release-monitoring.org/> which
supports checking a bunch of different package websites so we don't have
to reimplement it all.
-- Legoktm
