Hello everyone!
Mark your calendars for the Wikimania Hackathon! The Wikimania 2022
Hackathon is a free, online event open to the general public to work
together on technical projects, learn new skills, and meet other technical
contributors. You can find more information about this on the Wikimania page
<https://wikimania.wikimedia.org/wiki/2022:Hackathon>, which will continue
to grow over the next few weeks. For more details, read below.
*Schedule: *
The Hackathon will take place virtually in three time blocks:
16- 22 UTC August 12
12-17 UTC August 13
A final showcase on August 14.
*Format:*
At the beginning of the event, anyone can present a technical project they
plan to work on at the Pre-Event Showcase. This session will provide a
space for people to find teams, brainstorm new ideas, and make plans for
what to hack during the Hackathon.
Throughout the following hours, there will be social sessions and training
sessions run by the community, but the majority of the time will be spent
hacking together. Attendees can also attend other Wikimania activities.
At the end of the event, there will be a final showcase to present advances
or new technical projects built during the Hackathon to all of Wikimania.
*Accessibility:*If you have any accessibility or translation requests,
please contact hlepp(a)wikimedia.org.
Looking forward to spending time hacking together!
Cheers,
Haley and the WMF Developer Advocacy Team
MediaWiki devs,
I've been running the test suite using PHP 8.1 and providing patches in
Gerrit. I've gotten some feedback but I am hoping that I can get the
requisite +2's to get these fixes incorporated into MediaWiki.
I have several patches outstanding with no comments. If they could be
+2'd that would be awesome.
If they need more work before they're accepted, please let me know how
they are lacking so that I can update them.
Most of these can be found here:
https://gerrit.wikimedia.org/r/q/topic:change-809720
Thanks!
Mark.
--
http://hexmode.com/
I cannot remember the books I've read any more than the meals I have eaten;
even so, they have made me.
-- Ralph Waldo Emerson
Hey folks,
I know it's a bit early in the fiscal year and that's probably why I can't
find anything on wiki, but I understood that the new yearly plan puts a lot
of emphasis on the multimedia features. Does that include making 3D models
usable in our wikis? If there are planned projects related to that in this
fiscal year, would it be possible to get a link to the project page?
I'm asking because there are a lot of cool, freely licensed models out
there just waiting to be imported...
Thank you,
Strainu
The Search Platform Team
<https://www.mediawiki.org/wiki/Wikimedia_Search_Platform> 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, July 6th, 2022
Time: 15:00-16:00 UTC / 08:00-09:00 PDT / 11:00-12:00 EDT / 16:00-17:00 WAT
/ 17:00-18: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
Hope to talk to you tomorrow!
—Trey
Trey Jones
Staff Computational Linguist, Search Platform
Wikimedia Foundation
UTC–4 / EDT
Hi all,
Just a small reminder for any developers that they only have 4 more
days to become eligible to vote in the 2022 WMF Board of Trustees
election.
Developers can confirm their eligibility by reviewing the below list:
* are Wikimedia server administrators with shell access
* or have made at least one merged commit to any Wikimedia repos on
Gerrit, between 5 January 2022 and 5 July 2022.
* or have made at least one merged commit to any repo in
nonwmf-extensions or nonwmf-skins, between 5 January 2022 and 5 July
2022.
* or have made at least one merged commit to any Wikimedia tool repo
(for example magnustools) between 5 January 2022 and 5 July 2022.
* or have made at least 300 edits before 5 July 2022, and 20 edits
between 5 January 2022 and 5 July 2022, on Translatewiki.
* or maintainers/contributors of any tools, bots, user scripts,
gadgets, and Lua modules on Wikimedia wikis.
* or have substantially engaged in the design and/or review processes
of technical development related to Wikimedia.
This list was copied from
<https://meta.wikimedia.org/wiki/Wikimedia_Foundation_elections/2022/Voter_e…>.
If you need help getting a patch(/s) merged in the next few days,
don't hesitate to reach out to the community in the next few days on
the mailing lists, other locations such as the various IRC channels or
phabricator.
Regards,
p858snake/Peachey88
Der neue Baustein {{AhG}} soll anzeigen, an welchen Stellen in der Wikipedia gerade
eine Ad-hoc-Gruppe aktiv ist. Eine Ad-hoc-Gruppe kann als eine Art "task force police"
verstanden werden, also eine schnelle Eingreiftruppe, die problematische Texte bearbeitet.
Jeder Autor sollte diese "Vorlage:AhG" an beliebigen Stellen in der Wikipedia einsetzen
können, sobald er ein Problem erkannt hat, das er nicht alleine lösen kann. Das Bildschirmfoto
im Anhang zeigt die Anwendung des neuen Bausteines "AhG" auf einer typischen Seite, die dringend
überarbeitet werden muß. Jeder Admin kann den Baustein einsetzen, um schnell ein Einsatzkommando
zusammenzustellen.
Grüße
Siegfried
--
Siegfried Schmitt
Mathystr. 14-16
76133 Karlsruhe
GERMANY
Telefon: +49 721 358577
Mobilfunk: +49 1515 7525144
Siegfried.Schmitt(a)web.de
[If you don't write gadgets, user scripts or work on MediaWiki code feel
free to ignore this message]
Hey all!
Given the hackathon this weekend, now seemed like a good idea to talk about
us having a policy for code we write for gadget and user scripts developers
and as gadget and user script developers. TDLR: I am proposing a policy to
guide developers and authors of these kinds of scripts. I would like people
to read through my first draft
<https://www.mediawiki.org/wiki/User:Jdlrobson/Extension:Gadget/Policy#Polic…>
[1] and give me feedback on the talk page. Please feel free to share on
wiki.
*What is being proposed*
A policy page that would be editable on wiki and linked to from the editing
interfaces on gadgets, to guide both parties on how to write code that's
sustainable and less prone to breakage.
*Why is this needed?*
Despite gadgets and user scripts (which will be referred from now on as
wiki-based code) being a key component of MediaWiki projects, up until now
frontend APIs (e.g. how wiki-based code should interact with source control
provided code) have been ill-defined leading to misunderstandings between
engineers and wiki-based code developers when wiki-based code break. This
also leads to code rot, where developers do not feel empowered to make
changes as it's unclear how their changes will impact wiki-based code
developers. On top of this, when wiki-based code breaks it's not clear who
can and will fix them.
To solve this a policy I have been pushing for some time to make the
contract between MediaWiki developers and wiki-based code developers
explicit and less confusing.
I hope on the long run a policy would restore trust and good faith between
the two parties.
*How can you help?*
To contribute to the policy please use the discussion page to raise
concerns, suggestions, removals or additions.
*What's the deadline?*
I'd like to have all feedback gathered by 30th May 2022
[1]
https://www.mediawiki.org/wiki/User:Jdlrobson/Extension:Gadget/Policy#Polic…