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! :)
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. :)
(If you don’t work with links tables such as templatelinks, pagelinks and
so on, feel free to ignore this message)
TLDR: The schema of links tables (starting with templatelinks) will change
to have numeric id pointing to linktarget table instead of repeating
namespace and title.
The current schema and storage of most links tables are: page id (the
source), namespace id of the target link and title of the target. For
example, if a page with id of 1 uses Template:Foo, the row in the database
would be 1, 6, and Foo (Template namespace has id of 6)
Repeating the target’s title is not sustainable, for example more than half
of Wikimedia Commons database is just three links tables. The sheer size of
these tables makes a considerable portion of all queries slower, backups
and dumps taking longer and taking much more space than needed due to
unnecessary duplication. In Wikimedia Commons, on average a title is
duplicated around 100 times for templatelinks and around 20 times for
pagelinks. The numbers for other wikis depend on the usage patterns.
Moving forward, these tables will be normalized, meaning a typical row will
hold mapping of page id to linktarget id instead. Linktarget is a new table
deployed in production and contains immutable records of namespace id and
string. The major differences between page and linktarget tables are: 1-
linktarget values won’t change (unlike page records that change with page
move) 2- linktarget values can point to non-existent pages (=red links).
The first table being done is templatelinks, then pagelinks, imagelinks and
categorylinks will follow. During the migration phase both values will be
accessible but we will turn off writing to the old columns once the values
are backfilled and switched to be read from the new schema. We will
announce any major changes beforehand but this is to let you know these
changes are coming.
While the normalization of all links tables will take several years to
finish, templatelinks will finish in the next few months and is the most
So if you:
… rely on the schema of these tables in cloud replicas, you will need to
change your tools.
… rely on dumps of these tables, you will need to change your scripts.
Currently, templatelinks writes to both data schemes for new rows in most
wikis. This week we will start backfilling the data with the new schema but
it will take months to finish in large wikis.
You can keep track of the general long-term work in
https://phabricator.wikimedia.org/T300222 and the specific work for
templatelinks in https://phabricator.wikimedia.org/T299417. You can also
read more on the reasoning in https://phabricator.wikimedia.org/T222224.
*Amir Sarabadani (he/him)*
Staff Database Architect
Wikimedia Foundation <https://wikimediafoundation.org/>
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. 
Line numbers are shown in the “Template” namespace when syntax
highlighting (CodeMirror extension) is turned on.  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). 
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. 
In VisualEditor, the template dialog will become bigger and descriptions
will be more visible. 
When using syntax highlighting (CodeMirror extension)*, matching
brackets will be highlighted  and the color scheme will be updated
for better readability .
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
For syntax highlighting (CodeMirror extension), a colorblind-friendly
color scheme will be added. You’ll be able to activate it via a user
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
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
The Trainsperiment is complete!
Thank you to all the folks who commented and helped solve blockers—
*together* *we deployed four trains in one week!*
We have another favor to ask: we want to hear what you thought of the
If you have the mental space to take a survey, we'd appreciate it.
- Link: https://forms.gle/8P8BDuUrT1JKtCu36
- Deadline: We'll leave the survey open until *Friday, April 8th*
We'll share what we learn (anonymously) shortly after that!
Tyler Cipriani (he/him)
Engineering Manager, Release Engineering
The MediaWiki Stakeholders will be hosting our monthly meeting tomorrow
and all are invited.
Time: 15:30:00UTC 11:30AM Eastern 8:30AM Pacific 17:30 CEST
Google Meet: https://meet.google.com/mdd-ufhn-ksb
Markus Glaser, of Hallo Welt!, will talk about "Verified content in
MediaWiki with blockchain":
In a project with inblock.io, Hallo Welt! explored the possibilities
of creating a verification chain for content and changes in
MediaWiki. Markus will talk about what they did.
Robert Vogel, also of Hallo Welt!, will introduce the MWStake
Learn about what the MWStake Components are, their origin and
purpose. Robert will share Hallo Welt!'s experience with this
approach and show how MWStake Components can be used in your own
Please join us!
Mark A. Hershberger