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/>
After updates,
I set the language to "de" but i have the strange effect that not
everything is translated. e.g. i see "contributions" but the rest is in
German.
no idea, i checked the code the translation are complett.
CU
Hello (Semantic) MediaWiki users, maintainers, software developers, consultants, researchers!
The SMWCon in fall 2023 https://www.semantic-mediawiki.org/wiki/SMWCon_Fall_2023 will be held on location in Paderborn, Germany from December 11-13.
On three days there will be talks, tutorials and hackathons.
This conference addressed everybody interested in wikis and open knowledge, especially in Semantic MediaWiki, e.g. users, developers, consultants, business or government representatives, and researchers.
This conference aimed to:
* inspire/onboard new users,
* inform on where and how MediaWiki is used,
* convey and consolidate best practices,
* initiate/foster/integrate application and development and
* strengthen the community of stakeholders and its service portfolio.
Learn how to "do" MediaWiki in order to assume your responsibilities regarding your organization's knowledge management.
Please not that early-bird ticket sale ends today!
Call for Contributions
----------------------------
We are looking for use cases and best practices that provide insight in issues like
* How does AI change the way we use MediaWiki
* How do semantic wikis fit in and be combined with AI tools
* How can we use Semantic MediaWiki in research and organizations
* How do we develop and deploy MediaWiki and extensions
Your experience is valuable for all of us! So please share and propose a talk, tutorial or other contribution.
Go to the Conference Page (https://www.semantic-mediawiki.org/wiki/SMWCon_Fall_20223)
and hit the 'Propose a talk here' button.
Please propose a contribution if you plan to have one, even if you don't have the details yet. For us it is important to know what we can expect.
We look forward to your contribution!
Sponsoring
----------------
Thank you to the sponsors of SMWCon 2023!
* http://www.archixl.nl/ - Specialists in enterprise architecture, knowledge management, and semantics
* https://bluespice.com - The company behind BlueSpice, the open-source enterprise wiki software
* https://mywikis.eu - GDPR compliant (Semantic) MediaWiki hosting from the heart of Europe.
* https://wikibase-solutions.com/ - Specialist in business solutions with MediaWiki
Organization
------------------
The organizers of SMWCon 2023 and https://mwstake.org
* Bernhard Krabina, https://km-a.net (General Chair)
* Ad Strack van Schijndel, https://www.juggel.com (Program Chair)
* Tobias Oetterer, https://www.uni-paderborn.de/en/ (Local Chair)
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 1, 2023
Time: 15:00-16:00 UTC / 08:00 PT / 11:00 EDT / 16: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/>
Hi Community Metrics team,
This is your automatic monthly Phabricator statistics mail.
Accounts created in (2023-10): 392
Active Maniphest users (any activity) in (2023-10): 1115
Task authors in (2023-10): 555
Users who have closed tasks in (2023-10): 325
Projects which had at least one task moved from one column to another on
their workboard in (2023-10): 291
Tasks created in (2023-10): 2403
Tasks closed in (2023-10): 2327
Open and stalled tasks in total: 53760
* Only open tasks in total: 52740
* Only stalled tasks in total: 1020
Median age in days of open tasks by priority:
Unbreak now: 57
Needs Triage: 899
High: 1252
Normal: 1962
Low: 2558
Lowest: 2903
(How long tasks have been open, not how long they have had that priority)
Differential users who created or updated a patchset in (2023-10): 0
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 phab1004 at Wed 01 Nov 2023 12:00:42 AM UTC)