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
This release promotes Node.js 14 to be the default for the fresh-node command.
Get started by installing, updating, or learning more, at:
https://gerrit.wikimedia.org/g/fresh#fresh-environment
Changelog:
https://gerrit.wikimedia.org/g/fresh/+/22.05.1/CHANGELOG.md
Node.js 14 is now the default environment for the fresh-node command, this follows WMF CI (Thanks James Forrester!). [1] Node.js 12 remains available via fresh-node12. Node.js 10 has been removed after being deprecated since September of last year.
This release also adds support for detecting and installing to your home directory instead of system-wide, which is often preferred on Linux. The installer automatically selects one of $HOME/bin or $HOME/.local/bin if it exists and is in your "PATH". (Thanks Antoine Musso!)
If you encounter problems with Node.js 14 or experience other issues, let us know on Phabricator at https://phabricator.wikimedia.org/tag/fresh/. This is also where you can previous tasks.
Fresh is a fast way to create isolated environments from your terminal. These can be used to work more responsibly with 'npm' developer tools such as ESLint, QUnit, Grunt, Selenium, and more. Example guide: https://www.mediawiki.org/wiki/Manual:JavaScript_unit_testing
--
Timo Tijhof
[1] https://phabricator.wikimedia.org/T267890