Hi! As many of you know, a central global repository for Lua modules and
templates has been a frequent request since the early days of the movement.
This year, I programmed a JavaScript tool called Synchronizer
https://www.mediawiki.org/wiki/Synchronizer
(inspired on a previous tool called DiBabel by User:Yurik)
The tool allows to synchronize (that is, automatically copy) Lua modules
across Wikimedia wikis, and provides other features to help developers
update and maintain global modules.
I also re-wrote the documentation at
https://www.mediawiki.org/wiki/Multilingual_Templates_and_Modules to
account for the new tool. It basically describes how to develop a Lua
module that can be copied unchanged to any wiki, by abstracting things like
user-readable strings and config.
Admittedly, this is a "poor man's version" of a proper solution to the
problem, but one I find invaluable while developing and maintaining
modules. Hopefully some of you may find it useful too!
Help needed in finding a replacement to the mobile-friendly page content Rest API for my web app
Hello All,
For my website webnomads.in I have been using mobile-friendly page content Rest API for years . Now that it has been stopped I am struggling to find a new suitable API as I was displaying the content in sections .
On various pages I read about making use of parsoids .
While I have explored the different API offerings , I could not find any API which is delivering the text based on sections . I will be very thankful if someone can guide me or point me to any article showing the use of Parsoid or any other way to deliver page content in text form and in sections .
Thanks in advance .
Regards
Harsh
Hi all,
We will perform a short maintenance on contint2002 host tomorrow 29 Aug
2023 08:00-8:15 UTC.
The machine hosts integration.wikimedia.org, an instance of jenkins and
zuul. Services have to be stopped and restarted, so expect some
unavailability for around 15 minutes. Alias/cname contint.wikimedia.org
also maps to this machine.
Greetings
Jelto
The Wikimedia Data Engineering team is pleased to announce that a new event
stream, mediawiki.page_change.v1, is now publicly available at
stream.wikimedia.org (here
<https://stream.wikimedia.org/v2/ui/#/?streams=mediawiki.page_change.v1>).
The new event stream models page changes using a consolidated changelog
data model, whereas existing streams, like page-create and revision-create,
model each type of page change as a separate stream. With the current
model, you would have to consume multiple streams to understand how a
MediaWiki page changed. With the new stream, when a page is created,
edited, or deleted, an event captures the new state, as well as the state
prior to the change.
For more information on what fields you can expect to see in the events,
see the schema definition here
<https://schema.wikimedia.org/repositories//primary/jsonschema/mediawiki/pag…>
.
Starting now, new streams will be suffixed with a major version and will
not use hyphens in stream names. For more information, see here
<https://wikitech.wikimedia.org/wiki/Event_Platform/Stream_Configuration#Str…>
.
Benefits:
-
Only one stream to consume (instead of having to consume page-create,
page-delete, and revision-create streams to have a full picture of page
changes)
-
Events are ordered for a given page_id (delete will not come before
create)
-
Latest event has current and prior state
The existing event streams, such as page-create, revision-create,
page-delete, etc will continue to remain available, for now. We encourage
people to migrate to the new consolidated stream when they can as we plan
to mark the existing streams as deprecated within the next year. We will
send another communication about this when the plan is decided.
If you have any questions or issues please drop a Phabricator ticket here
<https://phabricator.wikimedia.org/project/board/6628/>
--
Luke Bowmaker
Data Engineering - Product Manager
Hi friends,
Phabricator will be unavailable tomorrow morning, Friday 25th August
at 09:00 UTC. This should take no more than 15 minutes.
If you have any questions or concerns, please let us know!
--Eoghan
Hello All,
Following up from conversations at the Wikimedia Hackathon in May
<https://phabricator.wikimedia.org/T336990>, I’d like to give an update on
how we’re approaching the work around MediaWiki and what to expect in the
upcoming months!
Since the beginning of July, the Foundation has dedicated MediaWiki product
leadership and a new MediaWiki engineering group
<https://www.mediawiki.org/wiki/MediaWiki_Engineering_Group>. We’re in the
process of onboarding (i.e. team processes, scope and operational
questions, getting familiar with the domain), have been spreading out to
help with specific projects as consultants and/or code contributors and are
now kicking off broader research to inform a strategy for MediaWiki. This
email is the first edition of a monthly email report to wikitech-l and
mediawiki-l. Reports can also be found on
<https://www.mediawiki.org/wiki/MediaWiki_Product_Insights/Reports>this page
<https://www.mediawiki.org/wiki/MediaWiki_Product_Insights/Reports>.
The first 12 months are about building out the foundations for the
following years:
- Building up the new MW Engineering group and MW Product function
{{doing}}
- Developing a strategy for MediaWiki - by June 30th, 2024 [Wikimedia
Foundation Annual Plan, WE3
<https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/2023-2024/…>]
{{kicking off}}
- Reaching a 20% increase of authors to selected MediaWiki repositories
deployed in Wikimedia production - by June 30th, 2024 [WE3.2] {{preparing}}
- Investing in developer experiences and reduce fragmentation of
developer workflows - continuous work with specific deliverables in 2023/24
[WE 3.1] {{doing}}
- Exploring and resolving a set of questions around stewardship and Open
Source strategy (goes beyond MediaWiki) [WE3.3] {{preparing}}
The approach that we’re trying to take is to work problem-focused (start
from the problem, usage and needs), data driven (conduct research to inform
decisions), step by step (prioritize and scope things, since we can’t
address all questions at once), and take people along (share regularly
about the work, initiate exchange and invite people in).
The research to inform this work
<https://www.mediawiki.org/wiki/MediaWiki_Product_Insights> consists of
multiple pillars and phases:
- MediaWiki within Wikimedia’s ecosystem: Key challenges and
opportunities. Includes interviews and review of existing write-ups
(pre-kick off at the Hackathon in May, continue in July)
- MediaWiki usage and development beyond Wikimedia: Synergy effects,
opportunities and challenges (start in November)
- Components-workflow mapping exercise. How are core workflows such as
edit or patrol powered and enabled by MW core components, extensions,
modules, gadgets, tools as of today? Initial focus is on prototyping this
for 1-2 Wikipedias and potentially Wikidata (start in September)
- Exploration of MW platform designs - what changes could we make to
increase the sustainability of the platform, better serve our core
workflows and needs and provide easier, faster and cohesive paths to
feature development? (October-June)
- Ways to establish effective and responsible stewardship for the
platform (October-June)
MediaWiki within Wikimedia’s ecosystem: Interviews
A key part of research is talking to folks. We’ve kicked this off with
first interviews with MediaWiki developers
<https://phabricator.wikimedia.org/T336990> at the Hackathon in May, have
surveyed ourselves (= MediaWiki Engineering group) and plan to conduct more
interviews with a cross-section of people over the next 6 weeks. The main
focus of this round is on MediaWiki within Wikimedia’s ecosystem and we’ll
be reaching out to a few more MediaWiki volunteer developers starting this
week. We’re planning to organize broader MediaWiki ecosystem conversations
in the upcoming quarters.
Project snapshot: Onboarding via Code Mob
As we’re building up the new MediaWiki Engineering Group, we’re also
investing in onboarding team members to MediaWiki development and MediaWiki
APIs who are just getting started. Bill Pirkle has come up with an
onboarding concept and is hosting weekly “Code Mob” sessions for folks on
the teams across MW Engineering - if you’re interested in “learning along”,
you can find a list of recordings and topics on this page
<https://meta.wikimedia.org/wiki/User:BPirkle_(WMF)/Code_Mobs_2023>.
Reporting and documentation
We will share about our work through the monthly emails and in 3-4
MediaWiki Product Insights reports published throughout the Foundations’
fiscal year (July-June). Over the next weeks, we will also create or update
team pages and clean up + create Phabricator workboards to make it easier
to follow along (and for us to keep track/focus :-).
Your ideas, support, patience as we’re settling in, experiences and
insights in challenges and opportunities really matter for this to work
out. A big thanks to all the folks who already have offered support, shared
their experiences, or otherwise helped out so far! <3
If you have specific questions or thoughts on this edition, this talk page
<https://www.mediawiki.org/wiki/Talk:MediaWiki_Product_Insights> is a good
place to connect :-)
Thanks all for reading!
Birgit
--
Birgit Müller (she/her)
Director of Product, MediaWiki and Developer Experiences
Wikimedia Foundation <https://wikimediafoundation.org/>
Hi all,
we have to do maintenance on etherpad.wikimedia.org tomorrow 23rd Aug 08:00
UTC. The maintenance requires a short reboot. The estimated downtime should
be around 10 minutes.
Greetings
Jelto
Hi all,
we have to do maintenance on Gerrit tomorrow 23rd Aug 06:30 UTC. The
maintenance requires a short reboot. The estimated downtime should be
around 10 minutes.
Greetings
Jelto