On Tue, Mar 1, 2016 at 3:36 PM, David Strine <dstrine(a)wikimedia.org> wrote:
> We will be holding this brownbag in 25 minutes. The Bluejeans link has
I'm not familiar with bluejeans and maybe have missed a transition
because I wasn't paying enough attention. is this some kind of
experiment? have all meetings transitioned to this service?
anyway, my immediate question at the moment is how do you join without
sharing your microphone and camera?
am I correct thinking that this is an entirely proprietary stack
that's neither gratis nor libre and has no on-premise (not cloud)
hosting option? are we paying for this?
can someone to update list https://phabricator.wikimedia.org/P10500 which
contains repositories which haven't mediawiki/mediawiki-codesniffer.
I found in list that much repositories are empty, and repositories which
aren't available on Gerrit.
So, can someone please update this list of repositories (in
mediawiki/extensions) which haven't mediawiki/mediawiki-codesniffer, but at
least, contains one PHP file. or to provide me command with which I can
update list when I want, so I don't need to request it every time.
P. S.: Happy weekend! :)
Wikimedia is participating in the winter edition of this year's Outreachy <
https://www.outreachy.org/>  (December 2021–February 2022)! The deadline
to submit projects on the Outreachy website is *September 30th, 2021*.
If you would like to share an idea for a project that you would like to
mentor or you are not familiar with the program and want to learn anything
more about it, feel free to reply to this email or leave a note on <
*About the Outreachy program*:
Outreachy offers three-month internships to work remotely in Free and Open
Source Software (FOSS), coding and non-coding projects with experienced
mentors. These internships run twice a year–from May to August and December
to March. Interns are paid a stipend of USD 5,500 for the three months of
work. They also have a USD 500 stipend to travel to conferences and events.
Interns often find employment after their internship with Outreachy
sponsors or jobs that use the skills they learned during their internship.
This program is open to both students and non-students. Outreachy expressly
invites the following people to apply:
- Women (both cis and trans), trans men, and genderqueer people.
- Anyone who faces under-representation, systematic bias, or
discrimination in the technology industry in their country of residence.
- Residents and nationals of the United States of any gender who are
Black/African American, Hispanic/Latinx, Native American/American Indian,
Alaska Native, Native Hawaiian, or Pacific Islander.
See a blog post highlighting experiences and outcomes of interns who
participated in a previous round of Outreachy with Wikimedia <
Some tips for mentors for proposing projects:
- Follow this task description template when you propose a project in
Add #Outreachy (Round 23) tag to it.
- Remember, the project should require an experienced developer ~15 days
to complete and a newcomer ~3 months.
- Each project should have at least two mentors, and one of them should
hold a technical background.
- When it comes to picking a project, you could propose one that is:
- Relevant for your language community or brings impact to the
Wikimedia ecosystem in the future.
- Welcoming and newcomer-friendly and has a moderate learning curve.
- A new idea you are passionate about, there are no deadlines
attached to it; you always wanted to see it happen but couldn't
due to lack
of resources help!
- About developing a standalone tool (possibly hosted on Wikimedia
Toolforge), with fewer dependencies on Wikimedia's core
doesn't necessarily require a specific programming language.
See roles and responsibilities of an Outreachy mentor <
We look forward to your participation!
(On behalf of the organization team)
Senior Developer Advocate
Wikimedia Foundation <https://wikimediafoundation.org/>
// sorry for cross-posting
Here is another change from WMDE’s Technical Wishes team concerning syntax
Soon, line numbers will be shown in wikitext editors when you have the
syntax highlighting feature (CodeMirror
enabled. The change will make it easier to detect line breaks and to
refer to a particular line in discussions. More information can be found on
this project page. 
We plan to deploy this with this week’s Mediawiki train, so it should be on
wikis from April 13-15. As a first step, it will be available on the
template namespace only. Deployment on other namespaces is planned for the
If you have any feedback, please let us know on the project’s talk page.
 We hope line numbering will be useful to you!
for the Technical Wishes team
Projektmanagerin Kommunikation Communitys Technische Wunschliste
Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 26-0
Unsere Vision ist eine Welt, in der alle Menschen am Wissens der Menschheit
teilhaben, es nutzen und mehren können. Helfen Sie uns dabei!
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/029/42207.
This is a quick note to highlight that in three weeks' time, the REL1_37
branch will be created for MediaWiki core and each of the extensions and
skins in Wikimedia git, with some (the 'tarball') included as sub-modules
of MediaWiki itself. This is the first step in the release process for
MediaWiki 1.37, which should be out in late November 2021, approximately
six months after MediaWiki 1.36.
The branches will reflect the code as of the last 'alpha' branch for the
release, 1.37.0-wmf.23, which will be deployed to Wikimedia wikis in the
week beginning 13 September 2021 for MediaWiki itself and those extensions
and skins available there. (Note that there will not be a 1.37.0-wmf.22
deployment, so there are only two Wikimedia production train deployments
inclusive between now and the branch point.)
After that point, patches that land in the main development branch of
MediaWiki and its bundled extensions and skins will be slated for the
MediaWiki 1.38 release unless specifically backported.
If you are working on a new feature that you wish to land for the release,
you now have three weeks to finish your work and land it in the development
branch; feature changes should not be backported except in an urgent case.
If your work might not be complete in time, and yet should block release
for everyone else, please file a task against the `mw-1.37-release` project
If you have tickets that are already tagged for `mw-1.37-release`, please
finish them, untag them, or reach out to get them resolved in the next few
We hope to issue the first release candidate, 1.37.0-rc.0, two weeks after
the branch point, and if all goes well, to release MediaWiki 1.37.0 a few
weeks after that.
Tyler Cipriani (he/him)
Engineering Manager, Release Engineering
My name is Soham Parekh. I've been working with the foundation both in the
capacities of a volunteer as well as a mentor for Outreachy and Google
Summer of Code since past year and absolutely love being here. I've
recently been exploring a bit of Devops and infrastructure primarily
learning about monitoring, provisioning, Docker and the likes and wanted to
contribute on projects along these lines. I think this would be an amazing
learning experience for me given Wikipedia is capable of handling such huge
chunks of traffic and maintain across all the projects. I wanted some
guidance on which team/group is ideal to reach out to for projects of this
kind? Any help will be awesome!