I'm happy to share that the first Web Perf Hero award of 2022 goes to Amir Sarabadani!
This award is in recognition of Amir's work (@Ladsgroup) over the past six months, in which he demonstrated deep expertise of the MediaWiki platform and significantly sped up the process of saving edits in MediaWiki. This improved both the potential of MediaWiki core, and as experienced concretely on WMF wikis, especially on Wikidata.org.
Refer to the below medawiki.org page to read about what it took to *cut latencies by half*:
https://www.mediawiki.org/wiki/Wikimedia_Performance_Team/Web_Perf_Hero_awa…
This award is given on a quarterly basis, and manifests as a Phabricator badge:
https://phabricator.wikimedia.org/badges/view/17/
-- Timo Tijhof, on behalf of WMF Performance Team.
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, this is a friendly reminder that we would love to hear from you
about your experience at last weekend's Hackathon.
Please fill in the survey until Sunday, May 29th and help us improve.
See the links below.
Thanks a lot in advance!
andre
-------- Quoted Message --------
From: Haley Lepp
Date: Sun, 22 May 2022 11:13:39 -0700
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
--
Andre Klapper (he/him) | Bugwrangler / Developer Advocate
https://blogs.gnome.org/aklapper/
_______________________________________________
Wikitech-ambassadors mailing list -- wikitech-ambassadors(a)lists.wikimedia.org
To unsubscribe send an email to wikitech-ambassadors-leave(a)lists.wikimedia.org
At the Wikimedia Hackathon 2022 that ended yesterday I have showed a program in the Showcase that can convert blocks from visual-programming-language Snap! to source code. This is the link to the folder where the program is located in. https://public.paws.wmcloud.org/User:Hog%C3%BC-456/BlocktoCode/ The program reads an XML-File with the definition of a program and gives the source code as an output. The platform for creating the blocks I used is called Snap!. This is an further development of Scratch. Scratch is an visual programming language based on blocks, that can be combined to create a program. A block is a small sentence with gaps for the variables. In Snap! it is possible to create own blocks and it includes an feature to directly convert blocks to code. I dont know how far this is developed and after I havent understand how to export the result with the code I have written a own program to do that.
What do you think are potential use cases for low code platforms like Snap! within the Wikimedia Projects. From my point of view such platforms offer a chance to make programming accessible to more people. It is from my point of view easier with such a platform to write small programs as without such an support. I am interested in use cases where the built-in codification feature or my program can be used to generate code that will be then useful within the Wikimedia projects.
Have a nice day and I am interested in your thoughts.
Hogü-456
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/>