Yesterday there was a conversation about code review on irc and among other
things, how sometimes patches can get "stuck".
I had an idea for a way to improve things. I'm not sure if it is a good
idea, but there's only one way to find out.
So without further ado, announcing the Code Review Patch Board:
https://www.mediawiki.org/wiki/Code_review/patch_board
In short - each person is allowed to list one of their patches on the board
that they would really like to see reviewed. You can only list one patch at
a time, and it should be a patch that you have been unable to get review
for for at least a week through normal means. See the page for the full
list of guidelines.
I encourage people to give it a try. Add a patch you wrote that you cannot
get a review for. Or if you have +2 rights, try giving some love to these
underloved patches.
I would also love to hear feedback on the general idea as well as the
current guidelines.
To repeat, the url is:
https://www.mediawiki.org/wiki/Code_review/patch_board
Thanks,
bawolff
TL;DR: The legacy Mobile Content Service is going away in July 2023. Please
switch to Parsoid or another API before then to ensure service continuity.
Hello World,
I'm writing about a service decommission we hope to complete mid-July 2023.
The service to be decommissioned is the legacy Mobile Content Service
("MCS"), which is maintained by the Wikimedia Foundation's Content
Transform Team. We will be marking this service as deprecated soon.
We hope that with this notice, people will have ample time to update their
systems for use of other endpoints such as Parsoid [1] (n.b., MCS uses
Parsoid HTML).
The MCS endpoints are the ones with the relative URL path pattern
/page/mobile-sections* on the Wikipedias. For examples of the URLs see the
"Mobile" section on the online Swagger (OpenAPI) specification
documentation with matching URLs here:
https://en.wikipedia.org/api/rest_v1/#/Mobile
== History ==
The Mobile Content Service ("MCS") is the historical aggregate service that
originally provided support for the article reading experience on the
Wikipedia for Android native app, as well as some other experiences. We
have noticed that there are other users of the service. We are not able to
determine all of the users, as it's hard to tell with confidence from the
web logs.
The Wikimedia Foundation had already transitioned the Wikipedia for
Android and iOS apps to the newer Page Content Service ("PCS") several
years ago. PCS has some similarities with MCS in terms of its mobility
focus, but it also has different request-response signatures in practice.
PCS, as with MCS, is intended to primarily satisfy Wikimedia
Foundation-maintained user experiences only, and so this is classified with
the "unstable" moniker.
== Looking ahead ==
Generally, as noted in the lead, we recommend that folks who use MCS (or
PCS, for that matter) switch over to Parsoid for accessing Wikipedia
article content programmatically for the most predictable service.
The HTML produced by Parsoid has a versioned specification [2] and because
Parsoid is accessed regularly by a number of components across the globe
tends to have fairly well cached responses. However, please note that
Parsoid may be subject to stricter rate limits that can apply under certain
traffic patterns.
At this point, I do also want to note that in order to keep up with
contemporary HTML standards, particularly those favoring accessibility and
machine readability enhancements, Parsoid HTML will undergo change as we
further converge parsing stacks [3]. Generally, you should expect iteration
on the Parsoid HTML spec, and of course as you may have come to appreciate
that the shape of HTML in practice can vary nontrivially wiki-by-wiki as
practices across wikis vary.
You may also want to consider Wikimedia Enterprise API options, which range
from no cost to higher volume access paid options.
https://meta.wikimedia.org/wiki/Wikimedia_Enterprise#Access
== Forking okay, but not recommended ==
Because MCS acts as a service aggregate and makes multiple backend API
calls, caveats can apply for those subresources - possibility of API
changes, deprecation, and the like. We do not recommend a plain fork of MCS
code because of the subresource fetch behavior. This said, of course you
are welcome to fork in a way compatible with MCS's license.
== Help spread the word ==
Although we are aware of the top two remaining consumers of MCS, we also
are not sure who else is accessing MCS and anticipate that some downstream
tech may break when MCS is turned off. As we are cross-posting this
message, we hope most people who have come to rely upon MCS will see this
message. Please feel free to forward this message to contacts if you know
they are using MCS.
== Help ==
Although we intend to decommission MCS in July 2023, we would like to share
resources if you need some help. We plan to hold office hours in case you
would like to meet with us to discuss this or other Content Transform Team
matters. We will host these events on Google Meet. We will provide notice
of these office hours on the wikitech-l mailing list in the coming weeks
and months.
Additionally, if you would like to discuss your MCS transition plans,
please visit the Content Transform Team talk page:
https://www.mediawiki.org/wiki/Talk:Content_Transform_Team
Finally, some Content Transform Team members will also be at the Wikimedia
Hackathon [4] if you would like some in-person support.
Thank you.
Adam Baso (he/him/his/Adam), on behalf of the Content Transform Team
Director of Engineering
Wikimedia Foundation
[1] https://www.mediawiki.org/wiki/Parsoid
[2] https://www.mediawiki.org/wiki/Specs/HTML
[3] https://www.mediawiki.org/wiki/Parsoid/Parser_Unification/Updates
[4] https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2023
Hello!
Please take our annual* *Developer Satisfaction Survey*!
Link: https://wikimediafoundation.limesurvey.net/484133
The survey is open until Fri, 17 Feb 2023—two weeks from today.
____
This survey is for members of the *Wikimedia Developer Community* and
covers the following topics:
-
Code review tooling and process
-
Code quality
-
Phabricator
-
Continuous Integration
-
MediaWiki development environments
-
Beta cluster / Staging
Please take the survey if you’ve used the above tools as part of your role
developing software for the Wikimedia community.
We’re soliciting your feedback to:
-
Measure developer satisfaction, and
-
determine where to invest resources in the future
We will anonymize, explore, and report the data we gather on mediawiki.org.
View previous years' survey results:
https://www.mediawiki.org/wiki/Developer_Satisfaction_Survey
Privacy statement: This survey will be conducted via a third-party service,
which may subject it to additional terms. For more information on privacy
and data-handling, see the survey privacy statement
<https://foundation.wikimedia.org/wiki/Legal:2023_Developer_Satisfaction_Sur…>
.
Thank you!
Tyler Cipriani (he/him)
Engineering Manager, Release Engineering
Wikimedia Foundation
____
*: “annual,” except we missed 2022 🙁
Hello,
In accordance with CoC's amendment policy
<https://www.mediawiki.org/wiki/Code_of_Conduct/Amendments>. The committee
proposes an amendment on behalf of one of the community members to be added
in unacceptable behavior section
<https://www.mediawiki.org/wiki/Code_of_Conduct#Unacceptable_behavior>:
Soliciting help, support or technical assistance for websites whose
predominant activity or content is behaviour that explicitly and
significantly violates provisions of the code of conduct is forbidden in
Wikimedia technical spaces. For example, websites advocating violence or
hate speech are not welcome to ask for support on Wikimedia support forums.
This is similar to w:en:Wikipedia:No Nazis
<https://en.wikipedia.org/wiki/en:Wikipedia:No%20Nazis>
This will be open for three months for community feedback in
https://www.mediawiki.org/wiki/Topic:Xgg6dvg2athdb1h7 and if the community
reaches consensus and the committee won't oppose it, It will be added to
the policy.
Best
Amir (he/him),
On behalf of the CoC committee
Hello
*GitLab will be down this coming Tuesday, 02 May, from 09:00 - 12:00 UTC* for
the datacenter switchover[0].
Much of this switchover window will be downtime, during which you will be
unable to access GitLab through ssh or the web interface.
The process will involve DNS changes and a full backup of the GitLab server
in the codfw datacenter, which will then be restored on the GitLab server
in the eqiad datacenter.
You can follow along on IRC in the libera.chat #wikimedia-gitlab channel[1].
[0]: <https://phabricator.wikimedia.org/T335504>
[1]: <ircs://irc.libera.chat:6697/wikimedia-gitlab>
Hello all!
The Search Platform Team usually holds an open meeting on the first
Wednesday of each month. Come talk to us about anything related to
Wikimedia search, Wikidata Query Service (WDQS), Wikimedia Commons Query
Service (WCQS), etc.!
Feel free to add your items to the Etherpad Agenda for the next meeting.
Details for our next meeting:
Date: Wednesday, May 3, 2023
Time: 16:00-17:00 UTC / 08:00 PDT / 11:00 EDT / 17:00 CET
Etherpad: https://etherpad.wikimedia.org/p/Search_Platform_Office_Hours
Google Meet link: https://meet.google.com/vgj-bbeb-uyi
Join by phone: https://tel.meet/vgj-bbeb-uyi?pin=8118110806927
Have fun and see you soon!
Guillaume
--
*Guillaume Lederrey* (he/him)
Engineering Manager
Wikimedia Foundation <https://wikimediafoundation.org/>
But there's no "All tasks", see
https://upload.wikimedia.org/wikipedia/commons/archive/2/28/20230428045221%…
Am Fr., 28. Apr. 2023 um 06:44 Uhr schrieb Martin Domdey <dr.taxon(a)gmail.com
>:
> But there's no "All tasks", see appended screenshot.
>
> Martin
>
>
>
> Jean-Rene Branaa <jbranaa(a)wikimedia.org> schrieb am Fr., 28. Apr. 2023,
> 06:34:
>
>> When in the workboard select "All Tasks" from the filter menu on the top
>> right hand side of the window under the Search bar.
>>
>> cheers,
>>
>> JR
>>
>>
>>
>> On Thu, Apr 27, 2023 at 9:10 PM Martin Domdey <dr.taxon(a)gmail.com> wrote:
>>
>>> https://phabricator.wikimedia.org/T335420
>>>
>>> Hi, I want to list this resolved task on the workboard TaxonBot, but
>>> can't see it in Backlog or anywhere (I guess because it's resolved).
>>>
>>> Can you help me please?
>>>
>>> Thank you,
>>> Martin ...
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Wikitech-l mailing list -- wikitech-l(a)lists.wikimedia.org
>>> To unsubscribe send an email to wikitech-l-leave(a)lists.wikimedia.org
>>>
>>> https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
>>
>> _______________________________________________
>> Wikitech-l mailing list -- wikitech-l(a)lists.wikimedia.org
>> To unsubscribe send an email to wikitech-l-leave(a)lists.wikimedia.org
>>
>> https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
>
>
https://phabricator.wikimedia.org/T335420
Hi, I want to list this resolved task on the workboard TaxonBot, but can't
see it in Backlog or anywhere (I guess because it's resolved).
Can you help me please?
Thank you,
Martin ...
We would like to announce the release of MediaWiki Language Extension
Bundle 2023.04. This bundle is compatible with '''MediaWiki >=
1.38.0''' and requires '''PHP >= 7.4.0'''.
The next MLEB is expected to be released in 3 months. If there are
very important bug fixes, we will do an intermediate release. Please
give us your feedback at
[[Talk:MLEB|https://www.mediawiki.org/wiki/Talk:MLEB]].
* Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2023.04.tar…
* sha256sum: c39c9d969255808a628e9fe2a9a2eceefd14ee5d3d0ef8d1fd1a4765804ad896
* Signature: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2023.04.tar…
Quick links:
* Installation instructions are at: https://www.mediawiki.org/wiki/MLEB
* Announcements of new releases will be posted to a mailing list:
https://lists.wikimedia.org/postorius/lists/mediawiki-i18n.lists.wikimedia.…
* Report bugs to: https://phabricator.wikimedia.org/project/view/1464
Release notes for each extension are below.
== Highlights ==
* This is the last release of MLEB supporting '''MediaWiki >= 1.38'''
== Babel ==
* Fix "User categories creation should be able to use templates"
({{phab|T211665}}, {{gerrit|881947}})
* Add ability to override Babel categories ({{gerrit|881944}})
* Fix "Some language tags show wrong language ("English") in Babel
boxes" ({{phab|T64714}}, {{gerrit|884400}})
== CleanChanges and cldr ==
* Localisation and maintenance updates.
== Translate ==
* Optionally allow setting a source language for aggregate groups
({{phab|T281073}})
* Allow fetching translation statistics for messages with similar
prefix ({{phab|T298966}})
* Fix bug with importing fuzzy translations from .po files ({{phab|T323430}})
* Add back-links in various special pages in the Translate extension
* Use a text-based group selector in Special:ExportTranslations in
order to improve usability when a large number of message groups are
present ({{phab|T331843}})
* Show error message if group being exported has no translations for
selected language ({{phab|T331824}})
* Display "Translate" tab if a user has permission to translate
irrespective of whether public editing is enabled ({{phab|T334330}})
* Add support to configure readable and writable translation memory
services separately ({{phab|T322284}})
** Support for the <code>mirrors</code> configuration parameter will
be dropped in the next MLEB release.
== UniversalLanguageSelector ==
* Localisation and maintenance updates.
* Fix issues with up/down keys navigation for the ULS menu ({{phab|T328956}})
* Remove ULSMobileWebfontsEnabled configuration option ({{phab|T332837}})
--
Kartik Mistry | કાર્તિક મિસ્ત્રી
kartikm.wordpress.com
