Dear Wikimedia
I am writing to extend an invitation to your organization to participate in
our Open Source Program DELTA WINTER OF CODE, NIT TRICHY.
DWOC - Where Winter meets Coding!
aims to foster collaboration and innovation among students and
professionals in the open source community. During the program, your
organization will have the opportunity to share your expertise and projects
with our students, and our students will have the chance to learn from your
experiences and work on real-world open source projects.
Winter is the season of coding excellence, and DWOC invites organizations
worldwide to join our transformative coding journey. Embrace the magic of
collaboration and innovation as we foster the next generation of developers
in a global community.
Calling All Organizations!
Passionate about mentoring? Apply now! DWOC is open for organization
applications. Be part of the winter coding magic.
Apply here https://dwoc.io/ <https://dwoc.io/>
Please let us know if your organization is interested in participating
[image: Mailtrack]
<https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=sig…>
Sender
notified by
Mailtrack
<https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=sig…>
11/16/23,
03:11:41 PM
Hi WIKIMEDIA,
I'm writing to express my interest in contributing to your organization.
I'm impressed by the work that you do and would like to know how I can get
started. Can you please provide me with more information about how to
become a
contributor joining your team? What are the requirements that I need to
meet? Are there any steps I need to take to get started? Thank you in
advance for considering my request. I look forward to hearing from you
soon.
Best regards,
Vaishnavi Maheshwari
[image: Mailtrack]
<https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=sig…>
Sender
notified by
Mailtrack
<https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=sig…>
11/15/23,
04:03:33 PM
tl;dr
Ignore this email if you do not use MediaWiki event streams.
On Monday December 11 2023, all MediaWiki related event streams will
have artificial
canary events
<https://wikitech.wikimedia.org/wiki/Event_Platform/EventStreams#Canary_Even…>
injected into them. If you use any of these streams, you should discard
these canary events.
*Add code to your consumers that discards events where* meta.domain ==
"canary".
Canary Events
At WMF, we use artificial 'canary' AKA 'heartbeat' events
<https://wikitech.wikimedia.org/wiki/Event_Platform/Stream_Configuration#can…>
to differentiate between a broken event stream and an empty event stream.
Canary events should be produced at least once an hour. If there are no
events in a stream for an hour, then something is likely broken with that
stream.
These artificial canary events can be identified by the fact that their
meta.domain field is set to "canary". If you use any of the streams listed
below, you will need to add code that discards any events where meta.domain
== "canary".
Back in 2020, we began producing canary events into all new streams, but we
never got around to enabling these for streams that already existed. We
needed to ensure that all consumers of these streams filtered out the
canary events. We're just finally getting around to enabling canary events
for all streams.
We will enable canary event production
<https://phabricator.wikimedia.org/T266798> for the following streams on
Monday, December 11th, 2023:
- mediawiki.recentchange
- mediawiki.page-create
- mediawiki.page-delete
- mediawiki.page-links-change
- mediawiki.page-move
- mediawiki.page-properties-change
- mediawiki.page-restrictions-change
- mediawiki.page-suppress
- mediawiki.page-undelete
- mediawiki.revision-create
- mediawiki.revision-visibility-change
- mediawiki.user-blocks-change
- mediawiki.centralnotice.campaign-change
- mediawiki.centralnotice.campaign-create
- mediawiki.centralnotice.campaign-delete
If you consume any of these streams, either external to WMF networks using
EventStreams, or internally using Kafka, please ensure that your consumer
logic discards events where meta.domain == "canary" before this date. (Note
that not all of these streams are exposed publicly at stream.wikimedia.org
<https://stream.wikimedia.org/?doc#/streams>.)
Thank you,
-Andrew Otto & the WMF Data Engineering team
<https://wikitech.wikimedia.org/wiki/Data_Engineering>
References
- T266798 - Enable canary events for all MediaWiki streams
<https://phabricator.wikimedia.org/T266798>
- T251609 - Automate ingestion and refinement into Hive of event data from
Kafka using stream configs and canary/heartbeat events
<https://phabricator.wikimedia.org/T251609>
Hi there,
The 1.42.0-wmf.4 version of MediaWiki is blocked at group0.
The new version can proceed no further until the following is resolved:
- https://phabricator.wikimedia.org/T350726: [PageImages]
SelectQueryBuilder::fetchFieldValues expects the query to have only one
field
Thank you for your help resolving this issue!
-- Your humble train toiler
--
Jaime Nuche
Software Engineer III
Wikimedia Foundation <https://wikimediafoundation.org/>
Hello. Is there something broken in API? Starting from today every time I
get the same message from mediawiki.org (and also testwiki), see the
screenshot.
Igal (User:IKhitron)
https://imgur.com/a/GCptf0T
Hi all,
Hope you have been well! We have just released v4.2 of the Commons
Android app to production. The update is now available on Play store [1]
and F-droid [2]. You could also build the app directly from our GitHub
repository [3].
An important thing we wanted to communicate. We've changed the Mapbox
API key used by the app in this release (v4.2.1) due to some unforeseen
circumstances. We also had to revoke the old API key that is being used
by the older version of the app (< v4.2.1).
You might face issues with accessing maps in those versions of the app
such as the Nearby screen appearing blank etc. We request your to kindly
upgrade to v4.2.1 in order to continue using the features for which
rendering a map is necessary. Other features should work fine. We regret
the inconvenience that this may cause. Feel free to open an issue in our
issue tracker [4] for any assistance. We'll be glad to help.
This release also includes the done by Ritika Pahwa during GSoC 2023.
This includes changes done to improve the reliability of the failed,
stuck uploads and changes to prevent location metadata loss for uploads
done via in the app.
In case you've been facing issues with the uploads, do give the latest
version a try. It should be better than before. Feel free to reach out
to us with any feedback you may have. It would be very helpful.
Other significant changes:
- Dark mode colour improvements
- Uploading via the in-app camera has been fixed and should work
normally.
- Provide the ability to edit an image to losslessly rotate it while
uploading.
- Category search now shows exact matches without any discrepancies
- We've switched to using MapLibre instead of Mapbox and thereby
disabled telemetry sent to Mapbox. We're also actively exploring
alternatives to Mapbox so that we could completely move away from it.
Check out the related issue [5] for information regarding the same.
- Fix some redundant crash issues
Checkout our changelog [6] for a more detailed set of changes since the
last announcement.
[[ References ]]
[1]: https://play.google.com/store/apps/details?id=fr.free.nrw.commons
[2]: https://f-droid.org/en/packages/fr.free.nrw.commons
[3]: https://github.com/commons-app/apps-android-commons/releases/tag/v4.2.1
[4]: https://github.com/commons-app/apps-android-commons/issues
[5]: https://github.com/commons-app/apps-android-commons/issues/5352
[6]:
https://github.com/commons-app/apps-android-commons/blob/main/CHANGELOG.md
Best regards,
Sivaraam (User:Kaartic)
Hello everyone,
I'm Martin Urbanec from the Wikimedia Foundation's Growth team
<https://www.mediawiki.org/wiki/Growth>. During the 2023-24 fiscal year,
we're working on Community configuration 2.0
<https://www.mediawiki.org/wiki/Community_configuration_2.0>, an extension
that empowers administrators to modify a subset of MediaWiki configuration
on-wiki, so that they can customize features to their needs. The Growth
team implemented this for its own features and since it was a great help in
scaling, we decided to generalize what we created and offer it to all
Wikimedia developers.
The Growth team spent a couple of months on planning Community
configuration 2.0 as well as discussing the project with its potential
users. You can read more information in the project page at MediaWiki.org
<https://www.mediawiki.org/wiki/Community_configuration_2.0> and the Product
Requirements Document
<https://docs.google.com/document/d/1Ai7ib6h1q9ly5xClowK2cn0CKIJp3Z1KpkvwzVM…>
.
The first aspect the Growth team is looking to define is configuration
validation, so that a malformed configuration file doesn’t cause the
MediaWiki instance to fail. We wrote our proposal regarding validation as a
Phabricator task at https://phabricator.wikimedia.org/T349757.
With this email, we would like to ask for your feedback, which you can
submit via Phabricator: https://phabricator.wikimedia.org/T349757. If you
feel so, we also invite you to read the Product Requirements Document and
submit any feedback as comments within that document. We would appreciate
it if you can submit any feedback before the end of *November 08, 2023*. In
case you have other questions about Community configuration, feel free to
ask them at the MediaWiki.org project talk page
<https://www.mediawiki.org/wiki/Talk:Community_configuration_2.0>.
Looking forward to reading your feedback!
For the Growth team,
*Martin Urbanec* (he/him)
Senior Software Engineer (Growth)
Wikimedia Foundation <https://wikimediafoundation.org/>