A few years ago, I wrote a "yet another" client library for the MediaWiki
action API, and went to the official list on
https://www.mediawiki.org/wiki/API:Client_code , expecting to add my
library. Instead, I found instructions on that page asking that new
libraries be added to https://www.mediawiki.org/wiki/API:Client_code/All
and describing a review process for periodically checking that libraries
meet some basic standards, before copying them over to the main list.
As happens with wiki workflows, this excellent concept fell into disrepair
and with nobody pushing it forward, there seems to be no new review
activity. Without active curation, I think it's unhelpful to have two
separate pages for "reviewed" and unreviewed libraries. My suggestion is
to merge the two pages and add a column for review status, so the
information is all in one place. I imagine this will reduce the work
needed to maintain this list.
Regards,
[[mw:User:Adamw]]
Hi all,
excited to share that we've released OOUI v0.44.0. It already happened
last Tuesday. ;)
Due to activities around Global Accessibility Awareness Day[0] and
Wikimedia Hackathon[1] (hope the ones participating had all fun!) the
release email is coming now.
It is rolling out on the normal train today, Tuesday, 24 May 2022.
Highlights in this release since v0.43.0:
- Dropped support for IE<10, FF<38, Android<4.4 in sync with updated
MediaWiki and Wikimedia's browser matrix. This removes a significant
amount of CSS rules and hacks specifically for those browsers[2]
-- This also enables us to use modern CSS techniques like Flexbox,
here resulting in a fix for a 6 year old bug on Firefox by Ed Sanders.
You can find details on additional new features, code-level, styling
and interaction design amendments, and all improvements since v0.43.0
in the full changelog[3].
Thanks to all code contributors, and to James D. Forrester and Bartosz
Dziewoński for their consistently excellent help – on this release
again.
If you have any further queries or need help dealing with breaking
changes, please let me know.
As always, interactive demos and library documentation is available on
mediawiki.org[4], there is comprehensive generated code-level
documentation and interactive demos and tutorials hosted on
doc.wikimedia.org[5].
OOUI version: 0.44.0
MediaWiki version: 1.39.0-wmf.13[6]
Date of deployment to production: Regular train, starting Tuesday 24 May 2022
[0] - https://meta.wikimedia.org/wiki/Accessibility/Global_Accessibility_Awarenes…
[1] - https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2022/
[2] - https://phabricator.wikimedia.org/T306486
[3] - https://gerrit.wikimedia.org/g/oojs/ui/+/v0.44.0/History.md
[4] - https://www.mediawiki.org/wiki/OOUI
[5] - https://doc.wikimedia.org/oojs-ui/master/demos/?page=icons&theme=wikimediau…
[6] - https://wikitech.wikimedia.org/wiki/Deployments#Tuesday,_May_24
Best,
Volker
Hi Everyone,
On behalf of the 2022 Wikimedia Hackathon Committee, we would like to thank
you for coming to the Wikimedia Hackathon!
Please consider giving us feedback on the Hackathon and your suggestions
for improvement.
There are two ways to give feedback:
1. Fill out the Wikimedia Hackathon Survey <
https://wikimedia.qualtrics.com/jfe/form/SV_cGbCKj4xyP0H3wi >. For more
information on privacy and data-handling, see the survey privacy statement
<https://foundation.wikimedia.org/wiki/Wikimedia_Hackathon_Post-Event_Survey…>.
The
survey will remain open until May 29, 2022.
2. If you would like to share feedback but do not wish to take the
Qualtrics survey, you can leave feedback on the Etherpad
<https://etherpad.wikimedia.org/p/Wikimedia_Hackathon_2022_Feedback>.
Finally, check out the badges
<https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2022/How_to#Joining_a_se…>
the committee made. You can put them on your userpages to show your
participation.
Thank you again for joining us! It was so much fun to meet everyone and
hack together.
See you at the Wikimania Hackathon in August!
Haley, on behalf of the
2022 Wikimedia Hackathon Team
Hi everyone,
We hope you’re ready for this three-day event, because the event starts in
10 hours!
The main hackathon will take place over the weekend (Friday through
Sunday), with two sets of core hours for sessions, social events, and
hacking. These core hours are:
-
3:00 <https://iw.toolforge.org/zonestamp/1653102000> - 6:00
<https://iw.toolforge.org/zonestamp/1653112800>UTC (Note: this is
tonight for some time zones!)
-
15:00 <https://iw.toolforge.org/zonestamp/1653145200>- 19:0
<https://iw.toolforge.org/zonestamp/1653159600>0 UTC
We’re expecting the virtual space to be the busiest at these times. Outside
of those core hours, you’re welcome to stay online to hack on projects,
collaborate with others, or hang out in the virtual space.
The goal with this schedule is to allow time for breaks and to accommodate
as many time zones as possible. You are not expected to attend both sets of
core hours - choose whichever hours work for you! For more info, see the
Schedule <https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2022/Schedule>.
When will the event start?
The opening ceremony will happen twice - once at 3:00 UTC, and once at
15:00 UTC on May 20. Find the links on the schedule
<https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2022/Schedule>!
How can I join the virtual space?
We’ll be using an online game-style space for the Hackathon. The links will
be published shortly before the event on the hackathon page on MediaWiki.org
<https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2022>. There will be
rooms for hacking and for sessions. Feel free to explore the virtual space
and join any room - they’re open for everyone!
What happens if I need help?
Once the platform goes live, you will be able to find a Help Desk where you
can ask questions, report any incidents, or just consult useful information
about the event. There are also discussion channels
<https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2022/Discussions> that
you can participate in.
How can I work on a project?
If you have an idea, you will be able to add your own projects
<https://phabricator.wikimedia.org/project/board/5802/> on Phabricator. If
you don’t know yet what to work on, see what projects
<https://phabricator.wikimedia.org/project/view/5802/> others will be
working on. You might find a project to join or get inspiration for your
own idea!
If you have any other questions, please check our FAQ
<https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2022/FAQ> section or
leave a comment on the talk page.
See you soon!
Melinda, for the Hackathon Committee
--
Melinda Seckington
Developer Advocacy Manager
Wikimedia Foundation <https://wikimediafoundation.org/>
Hello,
The committee has finished selecting new members of the Code of Conduct
Committee <https://www.mediawiki.org/wiki/Code_of_Conduct/Committee>. The
new committee candidates are (in alphabetical order):
- Amir Sarabadani
- Eugene233
- Martin Urbanec
- MusikAnimal
- Nuria Ruiz
Auxiliary members will be (also in alphabetical order):
- Effie Mouzeli
- Huji
- Jayprakash12345
- Luke081515
- Tony Thomas
More details about the member candidates can be found in this MediaWiki.org
page
<https://www.mediawiki.org/wiki/Code_of_Conduct/Committee/Members/Candidates>
.
Changes compared to last term:
- Legoktm leaves the main committee
- Eugene233 joins the main CoC committee
- Nuria moves from auxiliary to the main committee
- Luke081515 joins the auxiliary committee
- Ariel leaves the auxiliary committee
- Tony Thomas moves from main to the auxiliary committee
This is not the final structure. According to the Code of Conduct
<https://www.mediawiki.org/wiki/Code_of_Conduct/Committee#Selection_of_new_m…>,
the current committee publishes the new members and calls for public
feedback. Please let the committee know via techconduct(a)wikimedia.org if
you have any concern regarding the candidate slate by end of day *May 31,
2022*.
After that, the committee will either finalize the candidate slate or
update it in response to concerns raised. If the candidate slate changes,
there will be another two week feedback period covering the newly proposed
members. After the selections are finalized, there will be a training
period, after which the new Committee will be appointed and serve for a
year.
Best,
Martin Urbanec, on behalf of the Code of Conduct committee