Hello all, *(with apologies for cross-posting)*
We’re happy to announce that the next annual Wikimedia Hackathon will be
taking place May 2nd - 4th, 2025 in Istanbul, Turkey
<https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2025>! This event is
being organized by the Wikimedia Foundation in collaboration with local
Wikimedia affiliate, Wikimedia Community User Group Turkey (WMTR)
<https://meta.wikimedia.org/wiki/Wikimedia_Community_User_Group_Turkey>.
The Wikimedia Hackathon is an annual event to bring the global technical
community together to connect, hack, and explore new ideas. Technical
contributors from all around the world come together to improve the
technological infrastructure and software that powers and benefits the
Wikimedia projects.
During the Hackathon, we will focus on bringing together people who have
already contributed to the many technical aspects of Mediawiki and our
Wikimedia projects, those who know how to find their way around on our
technical ecosystem, and who are able to work or collaborate on projects
rather autonomously.
The 2025 Hackathon will happen in-person, onsite at the Renaissance Polat
Istanbul Hotel
<https://www.marriott.com/en-us/hotels/istrn-renaissance-polat-istanbul-hote…>
, and we’ll have discounted room codes for those that want to stay at the
hotel venue, to be announced in the coming weeks.
For those unable to attend in person, we'll be live-streaming the Hackathon
opening ceremony and closing showcase. Local and global communities are
also welcome and encouraged to organize pre-hackathon events or related
meetups.
Next steps:
-
Event registration will open on November 12, 2024 and will close mid
April 2025, or earlier based on event capacity.
-
There are a limited number of scholarships that can be requested during
early registration and all scholarships provided will adhere to the WMF
travel policy
<https://foundation.wikimedia.org/wiki/Policy:Scholarship_travel_policy>
guidelines.
-
Scholarship requests will only be accepted for consideration
until December
10, 2024.
-
Mark your calendars and register early!
All participants will adhere to the Code of Conduct
<https://www.mediawiki.org/wiki/Code_of_Conduct> for Wikimedia technical
spaces and the Friendly Space Policy
<https://foundation.wikimedia.org/wiki/Policy:Friendly_space_policy>.
If you have any questions or would like to reach out to the organizing
team, feel free to email hackathon(a)wikimedia.org or comment on the talk page
<https://www.mediawiki.org/w/index.php?title=Talk:Wikimedia_Hackathon_2025&a…>.
Cheers,
Deb
--
deb tankersley (she/her)
developer outreach program management
Wikimedia Foundation
Hi everyone,
tl;dr The tools we use to document Wikimedia JavaScript code are changing.
In the short term, you can read the complete MediaWiki core JavaScript docs
using the 1.41 version[0] while we migrate to the new system[1]. If you use
JavaScript documentation on doc.wikimedia.org, please share your feedback
on wiki[2].
Wikimedia JavaScript codebases are switching from using JSDuck[3] to
JSDoc[4] for documentation. Started in 2016, this migration is necessary
because JSDuck is currently unmaintained and does not support the ES6
standard[5]. Several Wikimedia JavaScript codebases, including Vector and
GlobalWatchlist, already use JSDoc, while several others, such as
VisualEditor and MediaWiki core, still use JSDuck.
The migration project consists of two parts: changing the codebases to
support JSDoc and improving the usability of the JSDoc WMF theme. For more
information, see phab:T138401[6].
== Migrating MediaWiki core to JSDoc ==
We are migrating MediaWiki core to JSDoc incrementally. While the migration
is in progress, the master branch docs will be incomplete, containing only
those modules that have been migrated. To read the old JSDuck docs, see the
MediaWiki 1.41 docs[0].
To help with migration, choose a module from the list in phab:T352308[7],
and follow the guide on phab:T138401[6] to translate the tags from JSDuck
to JSDoc.
== Migrating other codebases ==
You can find a list of codebases that use JSDuck on phab:T138401[6].
(Please add any that are missing.) To help migrate a codebase that uses
JSDuck, follow the instructions to set up JSDoc[8], and use the guide in
phab:T138401[6] to translate the tags from JSDuck to JSDoc.
== Improving the JSDoc WMF theme ==
One of the biggest differences between JSDuck and JSDoc is the HTML
interface for reading the docs. The WMF theme for JSDoc is not as
full-featured as the JSDuck theme, but to support this migration, the
Wikimedia Foundation Web, Design Systems, and Technical Documentation teams
are working to prioritize and complete a set of improvements to the JSDoc
theme, with the goal of releasing version 1 of jsdoc-wmf-theme in 2024.
If you use JavaScript documentation on doc.wikimedia.org, please leave a
comment on the JSDoc WMF theme talk page[2] and let us know how you use the
docs and which features of the theme are the most important to you.
Thank you for reading!
Alex, Kamil, Jon, Roan, and Anne
[0]: https://doc.wikimedia.org/mediawiki-core/REL1_41/js/
[1]: https://doc.wikimedia.org/mediawiki-core/master/js/
[2]: https://www.mediawiki.org/wiki/Talk:JSDoc_WMF_theme
[3]: https://github.com/senchalabs/jsduck
[4]: https://en.wikipedia.org/wiki/JSDoc
[5] https://en.wikipedia.org/wiki/ECMAScript
[6]: https://phabricator.wikimedia.org/T138401
[7]: https://phabricator.wikimedia.org/T352308
[8]: https://www.mediawiki.org/wiki/JSDoc
--
Alex Paskulin
Technical Writer
Wikimedia Foundation
Hello all,
Hope you have been well! We have just released v5.1.0 of the Commons
Android app to production. The update is now available on Play store
(beta track) [1] and F-droid [2]. You could also build the app directly
from our GitHub repository [3].
This release includes the improved upload queue that was specified in
the previous release post. This was contributed by Kanahia during
Google Summer of Code 2024[4]! He was mentored by Nicolas and Ritika.
The new upload queue system ensures smoother, sequential processing and
better progress tracking. It also provides more flexibility with
managing your whole upload queue by allowing to pause / resume / cancel
all ongoing uploads.
With this enhancement, we have retired the "Limited Connection Mode".
However, the new upload queue's pause provides flexibility similar to
the old mode. We would love to hear any thoughts / concerns about this
change.
Other significant changes:
- Fixed an UI issue where the 'Subcategories' and 'Parent Categories'
tabs appeared blank in the Category Details screen. Resolved by
optimizing view binding handling in the parent fragments.
- Added an option in "Nearby" feature enabling users to provide feedback
on Wikidata items. Users can report if an item doesn’t exist, is at a
different location, or has other issues, with submissions tagged for
easy tracking and updates.
- Improved the "Nearby" feature by splitting the query into two parts
for faster loading and better performance, especially in areas with
dense amount of places. This update also resolves issues with pins
overlapping place names.
- Upgraded AGP and target/compile SDK to 34 and make necessary
adjustments to the app such as adding "Partial Access" support.
- Fixed an issue where editing depictions removed all other structured
data from images. Now, only depictions are updated, preserving other
associated data.
- Fixed map centering in the image upload flow to use GPS EXIF tag
location from pictures and ensured "Show in map app" accurately
reflects this location.
- Fixed navigation after uploading via Nearby by directing users to the
Uploads activity instead of returning to Nearby, preventing confusion
about needing to upload again.
These are only a small chunk of all the changes that were part of this
release. Checkout our release notes [3] for a more detailed set of
changes since the last announcement.
As always, feel free to reach our to us with your valuable feedback.
You could share feedback in our talk page [5] / by writing an e-mail
to commons-app-android(a)googlegroups.com / via our issue tracker [6].
[ 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/v5.1.0
[4]: https://phabricator.wikimedia.org/T360265
[5]: https://commons.wikimedia.org/wiki/Commons_talk:Mobile_app
[6]: https://github.com/commons-app/apps-android-commons/issues
Best regards,
Sivaraam (User:Kaartic)
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, November 6, 2024
Time: 16:00-17:00 UTC / 08:00 PDT / 11:00 EDT / 17:00 CEST
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/>
With over 30 years of dedicated service in Rhode Island, Pools Plus is your trusted partner for exceptional pool and spa design, construction, and maintenance. We pride ourselves on creating stunning and enduring aquatic environments tailored to enhance your outdoor space. Our team of experts brings decades of experience to ensure a seamless, stress-free process from concept to completion, backed by reliable support to keep your pool or spa pristine all year. Discover the Pools Plus difference for a beautiful and relaxing outdoor oasis.
visit here for full info: https://www.poolsplusri.com
Dear Mediawiki maintainers:
In light of recent discussions within the Linux kernel community regarding
compliance with U.S. sanctions laws, particularly the removal of Russian
contributors from the MAINTAINERS file,[1][2] how are you ensuring
compliance with the U.S. Department of the Treasury's Office of Foreign
Assets Control (OFAC) regulations in your GPL-licensed projects?[3]
Specifically:
A. What measures are in place to screen contributors against OFAC's
Specially Designated Nationals (SDN) list?
B. How do you handle contributions from individuals or entities located in
countries subject to US embargos?
C. Have you assessed potential risks associated with sanctioned parties?
D. What steps are taken to educate and train maintainers and contributors
about OFAC sanctions and compliance requirements?
The underlying issue is that the GPL, unlike most other open source
licences, has been considered a contract in U.S. courts (e.g., Artifex
Software, Inc. v. Hancom, Inc. in 2017; Software Freedom Conservancy, Inc.
v. Vizio, Inc. in 2021) which means individuals who work for certain
designated companies in U.S.-sanctioned or embargoed countries are
forbidden from providing their copyrighted contributions to software
licensed under the GPL.[4] Other organizations go further to avoid
compliance issues -- for example Google Summer of Code forbids any
participation by people "ordinarily resident" in any US embargoed
country.[5] Understanding your approach to these issues would be invaluable
for the broader open-source community in maintaining compliance and
upholding the integrity of all GPL-licensed projects.
[1] https://www.phoronix.com/news/Linux-Compliance-Requirements
[2]
https://lore.kernel.org/lkml/e7d548a7fc835f9f3c9cb2e5ed97dfdfa164813f.camel…
[3] https://ofac.treasury.gov/faqs/all-faqs
[4]
https://arstechnica.com/information-technology/2024/10/russian-coders-remov…
[5] https://developers.google.com/open-source/gsoc/faq
Thank you for your attention to these questions.
For personal and safety reasons, I request anonymity on this topic and
prefer that replies be shared with the list rather than sent to me directly.
Back in June I announced https://schedule-deployment.toolforge.org/ as
a new tool to help simplify editing the
https://wikitech.wikimedia.org/wiki/Deployments page.[0] Today I am
back to let y'all know that thanks to a feature request by Gergő [1]
you can now use the tool by first browsing [[wikitech:Deployments]] to
find the backport window you would like to use.
When you have found the window that will work best for you, you can
click the green circled plus icon in the upper right corner of the
window's "changes" section. That link will take you to a view on the
scheduler tool showing the same deployment window's current patches
and a form to add your Gerrit change set. Submitting this form puts
you in the same workflow that you would get from the link on a
backport eligible Gerrit change, but with the addition of having the
window pre-selected in the scheduling form.
A related workflow change is that once you have scheduled a change set
for deployment using the tool you will now be redirected to that
window's view rather than the tool's landing page.
There were a few hiccups with the schedule-deployment tool earlier
today. These ended up being less than awesome handling of unexpected
data in the Deployments page. Hopefully my fixes will keep things
running smoothly for the foreseeable future. My thanks go out to Kosta
for reporting these issues and continuing to use the tool even though
he is so good at finding the sharp edges.
[0]: https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/…
[1]: https://phabricator.wikimedia.org/T372059
Bryan
--
Bryan Davis Wikimedia Foundation
Principal Software Engineer Boise, ID USA
[[m:User:BDavis_(WMF)]] irc: bd808