Hi,
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
> changed:
>
> https://bluejeans.com/396234560
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?
-Jeremy
Hello,
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.
Best regards,
Zoran.
P. S.: Happy weekend! :)
Hi everyone,
I want to notify you that I have, on behalf of the WikiTeq company, made a
task https://phabricator.wikimedia.org/T298277 for requesting repository
ownership for the Lingo extension.
In case that you have any kind of questions, please let me know. :)
Best regards,
Zoran
Hi everyone,
In 2019, the German-speaking wikis selected “Make working with templates
easier” as the focus area of Wikimedia Deutschland’s Technical Wishes
project. Since then, our team has made improvements in different areas, to
help template creators as well as users of the wikitext editor and
VisualEditor. Our work on this focus area is coming to an end, so I’d like
to summarize what happened and lay out the next steps:
Two changes from our Templates project have been available on all* wikis
for a while already:
-
A new attribute “suggested values” was introduced to help you clarify
what values a parameter may expect. [1]
-
Line numbers are shown in the “Template” namespace when syntax
highlighting (CodeMirror extension) is turned on. [2] A few wikis have
these line numbers in _all_ namespaces. If you want this for your wiki as
well, please reach out to us.
Several other changes were deployed to a small group in the past months. A
big thanks to Catalan, Turkish, Greek, Malay, Twi, French, Hungarian,
Hebrew, Finnish, Dagbani and German Wikipedia, to English Wikivoyage and
Nauruan Wiktionary as well as Wikitech wiki for testing these changes and
giving feedback to help us improve these projects. These changes are now
coming to more wikis:
-
Finding and inserting templates will become easier with an improved
search (in the TemplateWizard & in the template dialog of VisualEditor and
New Wikitext mode). [3]
-
In VisualEditor, you’ll be able to remove a template from a page via the
context menu, just like removing a table or an image. [4]
-
In VisualEditor, the template dialog will become bigger and descriptions
will be more visible. [5]
-
When using syntax highlighting (CodeMirror extension)*, matching
brackets will be highlighted [6] and the color scheme will be updated
for better readability [7].
The planned deployment date for all of these changes is March 9 (and March
16 on English Wikipedia).
A few weeks later, we’ll be deploying the last improvements from our
Templates project:
-
For syntax highlighting (CodeMirror extension), a colorblind-friendly
color scheme will be added. You’ll be able to activate it via a user
setting.
-
A range of fundamental changes to the VisualEditor template dialog will
be deployed. They will make it easier to understand what is expected from a
template, to navigate the template dialog, and to add parameters to a
template.
Feedback on all the projects is much appreciated on their respective talk
pages. Thanks a lot on behalf of the Technical Wishes team,
Johanna, Community Communications Technical Wishes
---
* All improvements in the CodeMirror extension, which provides syntax
highlighting, only apply to wikis that have the extension installed. This
is generally true for left-to-right language wikis, because unfortunately
the extension doesn’t work sufficiently for right-to-left languages yet
[1]
https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Suggested_values_for_…
[2] https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Line_Numbering
[3]
https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Finding_and_inserting…
[4]
https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Removing_a_template_f…
[5]
https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/VisualEditor_template…
[6] https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Bracket_Matching
[7]
https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Improved_Color_Scheme…
TLDR: Tech leads please review Best practices for extensions <https://www.mediawiki.org/wiki/Best_practices_for_extensions> on mediawiki.org.
Hi all,
You may be familiar with the Best practices for extensions <https://www.mediawiki.org/wiki/Best_practices_for_extensions> page on mediawiki.org. It has been marked as a draft since 2017.
I'd like to polish this page and get it to a state where it would be uncontroversial to label it as "Development guideline <https://www.mediawiki.org/wiki/Development_guidelines>". This would not make it a hard policy. Neither does it imply that it covers all practices in all situations.
Rather, it would mean that the items that are there now are indeed a part of our current best practices. We would keep it alive through bold <https://en.wikipedia.org/wiki/Wikipedia:Be_bold> edits and talk page conversations, similar to our Coding conventions <https://www.mediawiki.org/wiki/Manual:Coding_conventions/PHP> and other such guidelines that we maintain peer to peer and through consensus.
The reason I've not simply labelled it as such already is because before today I found the document to be out of sync with our actual practices. I have made a number of changes with descriptive edit summaries to bring it in sync with what I percieve to be our best practices; based on how myself and other maintainers perform code review at large, and how we review new extensions prior to deployment.
All are welcome to fix mistakes, raise questions/concerns on the talk page, on this thread. You're also welcome to message me directly anytime if you prefer.
If you consider yourself familiar with our practices and/or lead and mentor other engineers, please take a minute to review the page and consider whether the items reflect your current understanding and judgement.
--
Timo Tijhof,
Principal Engineer,
Wikimedia Performance Team.
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, March 2nd, 2022
Time: 16:00-17:00 GMT / 08:00-09:00 PST / 11:00-12:00 EST / 17:00-18:00 CET
& WAT
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 next week!
—Trey
Trey Jones
Staff Computational Linguist, Search Platform
Wikimedia Foundation
UTC–5 / EST
Hello folks,
The most recent GitLab update reset all Runner registration tokens due to a
critical security issue. Already registered Runners are not affected and
keep working as expected. Registering new Runners needs an updated token.
So, please update the registration token for your self-managed project
Runners if you need to re-register or register new runners.
If you don't use a self-managed GitLab Runner no action is needed.
For more information see the most recent release notes:
https://about.gitlab.com/releases/2022/02/25/critical-security-release-gitl…
Greetings
Jelto
Hello everyone,
TLDR; Wikimedia will soon be applying as a mentoring organization to Google
Summer of Code 2022 <https://summerofcode.withgoogle.com> [1] and Outreachy
Round 24 <https://www.outreachy.org/> [2]. We are currently working on a
list of interesting project ideas to include in the application. If you
have some ideas for coding or non-coding (design, documentation,
translation, outreach, research) projects, share them here: <
https://phabricator.wikimedia.org/T299453> [3].
*Timeline*
As a mentor, you will engage potential candidates in the application period
for both programs between March and April. You will help candidates make
small contributions to your project and answer any project-related queries
during this time. You will work more closely with the accepted candidates
during the coding period between May and August.
*New changes are coming to GSoC*
GSoC has exciting changes this year, including:
* Eligibility criteria redefined–the program is now open to all open-source
newcomers 18 years and older. It will no longer be solely focused on
university students or recent graduates.
* Multiple sizes of projects supported–ranging from ~175 to ~350 hr long.
* Increased flexibility in project timing–project deadline can be extended
to up to 22 weeks.
*Tips for proposing projects*
* Follow this task description template when you propose a project in
Phabricator: <
https://phabricator.wikimedia.org/tag/outreach-programs-projects> [4]. Add
#Google- Summer-of-Code (2022) or #Outreachy (Round 24) tag.
* Project should require an experienced developer ~15 days and a newcomer
~3 months to complete.
* Each project should have at least two mentors, and one of them should
hold a technical background.
* Ideally, the project has no tight deadlines, a moderate learning curve,
and fewer dependencies on Wikimedia's core infrastructure. Projects
addressing the needs of a language community are most welcome!
* If you don't have an idea in mind and would like to pick one from an
existing list, check out these projects: <
https://phabricator.wikimedia.org/tag/outreach-programs-projects/> [4]
* To learn more about the roles and responsibilities of mentors, visit our
resources on MediaWiki.org: <
https://www.mediawiki.org/wiki/Outreachy/Mentors> [5], <
https://www.mediawiki.org/wiki/Google_Summer_of_Code/Mentors> [6].
Cheers,
Srishti
[1] https://summerofcode.withgoogle.com
[2] https://www.outreachy.org/
[3] https://phabricator.wikimedia.org/T299453
[4] https://phabricator.wikimedia.org/tag/outreach-programs-projects/
[5] https://www.mediawiki.org/wiki/Outreachy/Mentors
[6] https://www.mediawiki.org/wiki/Google_Summer_of_Code/Mentors
*Srishti Sethi*
Senior Developer Advocate
Wikimedia Foundation <https://wikimediafoundation.org/>