I'm pleased to announce the immediate availability of MediaWiki
1.35.0-rc.1, the second release candidate for 1.35.x, the next LTS version
to replace 1.31 which is due to go end of life in June 2021. Download links
at the end of the e-mail. The tag has been signed and pushed to Git.
Please note that the PHP version requirement has been raised from 7.2.9 in
MediaWiki 1.34 (and 7.0 in MediaWiki 1.31), to 7.2.22 (this may change
further, see below).
This is not a final release and should not be used for production websites.
Known issues are tracked in Phabricator on the release workboard [1]. As
always please do try out the release candidate in a test environment and
report any issues that you discover. Please use the #MW-1.35-Release [2]
tag in Phabricator when reporting issues specific to this release.
It is expected that MediaWiki 1.35 will become final in late August 2020,
and will be supported for 3 years after that.
Known/outstanding issues/things to test:
* It has been proposed to require PHP 7.3 for MediaWiki 1.35, please
discuss at <https://phabricator.wikimedia.org/T257879>.
* Both the Vector skin and the underlying skin infrastructure are
undergoing numerous changes, so there might be things broken that are
already fixed in master and as such need backporting.
* VisualEditor and Parsoid are now bundled in the tarball and no longer
need a separate nodejs service. The documentation for this still needs to
be updated, and in some cases, users are reporting HTTP 500 errors from
RestBase <https://phabricator.wikimedia.org/T259693>.
* Watchlist expiry (behind the $wgWatchlistExpiry flag) is currently
experimental. It should be finished for the 1.35.0 final release.
* If you're on Windows and use 7zip, you may experience issues extracting
the tarball. This was noted in the last set of security releases. Try using
a different decompression tool <https://phabricator.wikimedia.org/T257102>.
Changes since 1.35.0-rc.0:
* (T252136) Fix RecentChanges watchlist filters when WatchlistExpiry is off.
* (T258662) Update time period for watchlist expiry pop-up.
* (T258443) Fix expiry dropdown not getting disabled on edit page.
* (T259398) Add license information for promise-polyfill.
* Remove executable bit from scripts without shebang.
* (T256526) Fix bold of watched items on Special:RecentChangesLinked.
* (T259060) Edit page expiry dropdown should keep state after
disabling/enabling.
* (T259009) Translate expiry period in pop-up message for watchlist expiry.
* (T258310) Add watchlist clock icon to RecentChanges.
* (T259362) Permit temporary table writes on replica DB connections.
* (T250214) Add UI support in Special:EditWatchlist for watchlist expiry.
* (T72470) Disable wgLegacyJavaScriptGlobals by default.
* (T130906) Add Edge to MediaWiki:Clearyourcache.
* (T257279) Add mediawiki.ui Less variable deprecation note.
* (T249521) Fixed reassignEdits.php to work with anonymous users.
* (T259448) Fix Circular dependency when creating service in
DBLoadBalancerFactory.
* (T257259) Default to using watchlist expiry of old page when moving pages.
Preliminary release notes:
https://phabricator.wikimedia.org/source/mediawiki/browse/REL1_35/RELEASE-N…https://www.mediawiki.org/wiki/Release_notes/1.35
Open Bugs:
[1] https://phabricator.wikimedia.org/project/board/4035/
Bug report form:
[2]
https://phabricator.wikimedia.org/maniphest/task/edit/form/1/?tags=MW-1.35-…
**********************************************************************
Download:
https://releases.wikimedia.org/mediawiki/1.35/mediawiki-1.35.0-rc.1.tar.gz
Download without bundled extensions:
https://releases.wikimedia.org/mediawiki/1.35/mediawiki-core-1.35.0-rc.1.ta…
Patch to previous version (1.35.0-rc.0):
https://releases.wikimedia.org/mediawiki/1.35/mediawiki-1.35.0-rc.1.patch.gz
GPG signatures:
https://releases.wikimedia.org/mediawiki/1.35/mediawiki-core-1.35.0-rc.1.ta…https://releases.wikimedia.org/mediawiki/1.35/mediawiki-1.35.0-rc.1.tar.gz.…
Public keys:
https://www.mediawiki.org/keys/keys.html
Hello,
can you check last two patches from this URL:
https://gerrit.wikimedia.org/r/q/status:open+owner:zorandori4444%2540gmail.…
?
As tests pass now, I believe that they are good to get +2 now.
Best regards,
Zoran Dori
volunteer, Wikimedia Serbia
s: kizule.xyz e: zorandori4444(a)gmail.com
*Imagine a world in which every single human being can freely share inthe
sum of all knowledge.*
The 1.36.0-wmf.3 version of MediaWiki is currently blocked at group0.[0]
The new version can proceed no further until these issues are resolved
or appropriately triaged:
* Uncaught ArgumentCountError: Too few arguments to function
OOUI\Tag::appendContent(), 0 passed
- https://phabricator.wikimedia.org/T259745
* Argument 3 passed to
CachingFallbackLabelDescriptionLookup::buildCacheKey() must be of the
type string, null given
- https://phabricator.wikimedia.org/T259744
Thanks for any help resolving these issues. If they're handled by
roughly 14:30 PDT / 21:30 UTC today, the train can roll forward.
Otherwise it can resume during US working hours on Thursday.
-- Your typical train temporizer
[0]. <https://phabricator.wikimedia.org/T257971>
[1]. <https://tools.wmflabs.org/versions/>
Hi all,
We’re happy to announce that the first two of many changes focused on
improving the desktop experience of the Vector skin [1] have been released
as a user preference to all projects and as default on a set of early
adopter wikis: Basque, Farsi, French, and Hebrew Wikipedias, French
Wiktionary, and Portuguese Wikiversity.
Since its introduction in 2009, the Vector skin has changed little, while
the needs of our readers and editors have shifted significantly, as have
their expectations for a quality reading experience that focuses on the
content itself. Over the next year, the readers web team [2] will be
researching and building out improvements to the desktop experience based
on research and existing tools built by our communities.
Our goal is to create a more welcoming reading and editing experience -
something that feels familiar yet makes it easier and quicker to read,
edit, and perform common functionality.
Our first change, a collapsible sidebar, allows users to collapse the
lengthy menu on the left side of the page. We believe this change improves
usability by allowing people to focus on the content itself - on reading,
editing, or moderating.
Our second change introduces a maximum line width to our content on pages
such as article pages and discussion pages. Studies have shown that
limiting the width can lead to better retention of content, as well as a
decrease in eye strain
You can opt into these features by unchecking “legacy vector” from the
appearance tab of your user preferences.
We’d also like to note that these are the first of a series of changes and,
as such, their visual characteristics are not permanent. Also - there might
be bugs. If you notice an issue or would like to learn more about the
project itself - please head to our project page [3].
Thank you!
Olga
[1] https://www.mediawiki.org/wiki/Skin:Vector
[2] https://www.mediawiki.org/wiki/Readers/Web/Team
[3] https://www.mediawiki.org/wiki/Reading/Web/Desktop_Improvements
--
*Olga Vasileva* // Senior Product Manager // Web
https://wikimediafoundation.org/
*Imagine a world in which every single human being can freely share in
the sum of all knowledge. That's our commitment. Donate
<http://donate.wikimedia.org/>. *
Hi All,
A hallway track is a series of (spontaneous and unrelated) gatherings of
small groups of people, where you start with one topic and might end at a
very different one, develop ideas together, get to know new folks and meet
people you haven’t seen for a while. [citation needed]
All of that sounds great - especially as we don’t have it currently. This
is why we came up with
The Hallway Track <https://www.mediawiki.org/wiki/The_Hallway_Track> - a
new initiative from/for the Wikimedia technical community to remotely
connect with each other. A space to discuss what we’re working on, new
ideas, fun stuff and maybe demo things.
It’s open to folks who want to get to know others in Wikimedia-Tech or want
to meet with people they haven’t seen in a while (or any other good reason
:-).
First edition takes place on Wednesday, August 12th, 2020, 18:00 UTC.
Sessions are for 6 people max, to allow for small group discussion.
If you’d like to participate or organise future editions, please go to
https://www.mediawiki.org/wiki/The_Hallway_Track.
Hope to see you at the Hallway Track!
Please bring your own coffee/carrot juice.
Addshore & Birgit
(Friends of The Hallway Track)
--
Birgit Müller (she/her)
Director of Technical Engagement
Wikimedia Foundation <https://wikimediafoundation.org/>
*Technical Wishes: FileExporter and FileImporter become default features on
all Wikis*
The FileExporter and FileImporter [1] will become default features on
August 5th, 2020 on all Wikis. They help you to move files from your local
Wiki to Wikimedia Commons, while keeping all original file information
(description, source, date, Author, and revision history) intact. The wish
to make moving files from local Wikis to Wikimedia Commons easier
originates from WMDE’s 2013 Technical Wishes survey. There it was voted
into the top wishes for technological improvements by the German-speaking
Wikipedia Community.
How does it work?
1.
Step: If you are an auto-confirmed user, you will see a link “Export to
Wikimedia Commons” in the menu on the local file page.
2.
Step: When you click on this link, the FileImporter checks if the file
can be moved to Commons. These checks are performed based on the wiki’s
configuration page which is created and maintained by each local wiki
community.
3.
Step: If the file is compatible with Commons, you will be taken to a
preview page on Wikimedia Commons, where you can update or add information
about the file, such as the description. You can also add the ‘Now Commons’
template to the file on the source wiki by clicking the corresponding check
box on the preview page on Wikimedia Commons. Admins can delete the file
from the local Wiki by clicking the checkbox ‘delete file on source wiki in
my name’. By clicking on the ‘Import’ button at the end of the page, the
file is imported to Wikimedia Commons.
If you want to know more about the FileImporter extension or the Technical
Wishes Project [3], follow the links. We are looking forward to answering
your questions and getting your feedback on our central feedback page [4].
--For the Technical Wishes Team: Max Klemm (WMDE) [5]
[1]
https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Move_files_to_Commons
[2]
https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Move_files_to_Commons
[3] https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes
[4] https://www.mediawiki.org/wiki/Help_talk:Extension:FileImporter
[5] https://meta.wikimedia.org/wiki/User:Max_Klemm_(WMDE)
--
Max Klemm
Working Student Community Communication for Technical Wishes
Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Phone: +49 (0)30 219 158 26-0https://wikimedia.de
Imagine a world in which every single human being can freely share in
the sum of all knowledge. Help us to achieve our
vision!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.
Hello,
We are replacing our current repository for Helm charts
(https://releases.wikimedia.org/charts/) with an instance of
ChartMuseum. The new repository index can be found at:
https://helm-charts.wikimedia.org/stable/index.yaml
Users may add/update the Helm repository config with using "helm repo
add wmf-stable https://helm-charts.wikimedia.org/stable/".
Developers may now stop the process of packaging helm charts manually,
rebuilding the index and pushing all that to git. As of now, increasing
the charts version number in Chart.yaml is sufficient to have the chart
being packaged and uploaded to ChartMuseum automatically.
We will remove the chart tgz archives from git as well as the old
repository from releases.wikimedia.org in the next week. If you
experience any issues, please feel free to reach out in
#wikimedia-serviceops.
For further details, please see:
https://wikitech.wikimedia.org/wiki/ChartMuseum
Cheers,
Janis Meybohm
Hi Community Metrics team,
This is your automatic monthly Phabricator statistics mail.
Accounts created in (2020-07): 316
Active Maniphest users (any activity) in (2020-07): 1068
Task authors in (2020-07): 569
Users who have closed tasks in (2020-07): 317
Projects which had at least one task moved from one column to another on
their workboard in (2020-07): 326
Tasks created in (2020-07): 2574
Tasks closed in (2020-07): 2174
Open and stalled tasks in total: 45187
* Only open tasks in total: 44186
* Only stalled tasks in total: 1001
Median age in days of open tasks by priority:
Unbreak now: 18
Needs Triage: 567
High: 933
Normal: 1267
Low: 1821
Lowest: 1839
(How long tasks have been open, not how long they have had that priority)
Active Differential users (any activity) in (2020-07): 8
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 phab1001 at Sat 01 Aug 2020 12:00:22 AM UTC)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi,
tl;dr: Help would be appreciated testing a new MediaWiki codesearch
UI: <https://codesearch-beta.wmcloud.org/>. Sticking "-beta" in
existing URLs should just work.
The current codesearch interface is a pretty bad hack based on
upstream's UI. Originally I implemented it that way with the
assumption that upstream would continue to make improvements that we
could benefit from but that didn't really happen.
The new beta UI implements some features I wanted/others have asked for:
* Switching search profiles doesn't lose your search query
* An overview listing which repositories have results
* An option to get a Phabricator checklist based on the results
Some features are missing (e.g. manual repository selector) that I
don't use, but if people want I can implement them. Please provide
requests or general feedback via email or the codesearch Phabricator
project.
If people are happy/satisfied with the new UI, I'd like to replace the
old one in a few weeks.
I'd also appreciate some help with some of the minor layout/styling
issues. The code[1] is written in Rust and compiled to WebAssembly,
but the styling is all Bootstrap so hopefully it's easy to work with.
I'm not sure it'll remain implemented in client-side Rust, the
performance really isn't that great.
[1]
https://gerrit.wikimedia.org/g/labs/codesearch/+/refs/heads/master/front
end/
Thanks,
- -- Legoktm
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEE2MtZ8F27ngU4xIGd8QX4EBsFJpsFAl8jzRMACgkQ8QX4EBsF
JpvHYBAA0Dnq1hMYqDQPMTh/S+6CXKf7YN91mMhWYoPNA/eWP9p8V3Sd6TIy+T3w
wCfNK3SBdsCt7G/ut5ikZ1U3orSr952imrJIGkK6FIV9FDCZ1Obgr/J3bTYNZGpP
gQ+BLvLIfHnNlVA3Wa5IsEf7ja1A7SBddfmjE5nl1NFR/7muzX43kmT+PYlMeJDt
J4EiZOgEdp+Dk12/zdTw0RAGbZDfcTRO6ytxe4ZNNKyef9jLq7OH3QrU6lYF/Nja
zoo+Kq6Bmv7428DrgtfInbdrYgWCRPAyVkuAje/9cH/W3k2RcY26y/2ohSXfS4mg
EBiywlOum+DBsm5gbFRG7fvqjvHBY77sIN7Io67OxZRcECzOfWd1qYiRI81aoRzd
4L+cuuqnK9cQdFzyXIx6C8cVu1HaaOaCum2mLgUxEMX/tome7tQ7ZY2wqEDY51Xv
YCFA91W4sCVmeZBJeYCMURiC7r/Aq0HwQAgzFynWCP5SEngDokwQ5MpOJwlsRhgG
dWdhHsWFvJmS5XofDYLRPGG+RM0l1JXpoxLxWr0k8/udiRmASS6Pev08DBWiayZv
xy62h1WB3lIIEb7W3JpGcQ8j6NZB6if1mkHl5HqjzDjqSbJ7QrbJPYUmQlou28L9
8OezeAhaqZbRKlIy3OR1KCCcCUTcOMo1jAiOlwSImRaD8dVzKkE=
=aRW2
-----END PGP SIGNATURE-----