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
TLDR: Tech leads please review Best practices for extensions <https://www.mediawiki.org/wiki/Best_practices_for_extensions> on mediawiki.org.
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.
Wikimedia Performance Team.
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:
This is Yashraj Singh , I am currently pursuing my bachelor's in computer
I am a beginner with open source but really passionate about it. I,ve got
my hands in technologies like C/C++ and frontend development () , can you
give me an idea that how can I start making contributions to your
Thank you for your time and consideration
MediaWiki TiddlyWiki Dokuwiki MoinMoin BookStack Gollum and other open
source wiki progams - you don't p2p-swing it as you're supposed to,
program peer-to-peer programs including unseen competitive games
now it's time for me to take apart your aching heart
selling out Isengard Tower and garden by welcoming
Rey refuses to sell BB-8 for 60 portions in the desert - you do it
from comfy chairs in era of Internet
siding with Chief Tui by accepting the island without peer-to-peer
games github twitch email
when Ocean himself helps Mona in p2p manner
turning programs into projects like producers who push Nick Lang to
play Joe Gunn when he wants Ray Casanov part
caging programs under user namespaces, making L3 furious - why?!
because you are my organic overlords?!
nesting around one program and not programming games like proud Vulcan Academy
yet having shiny webpages, docs, chats and lengthy maintainer attributions
no wonder Spock left for Starfleet
thank you, ministers, for your consideration - live long and prosper
soak it in cause it's the last you'll ever see
honest as What the Health?
if Eliud Kipchoge instead of breaking 2 hour barrier set up a
donation booth with a little throne in the middle of the track
if Linus - inner Biff stole name Freax - agreed to join Steve Jobs
and Apple on that meeting when he first came to California
instead of keeping his word - free and open
if torrent clients accepted Strickland-server-networks-only Hill
Valley instead of generating most traffic
if Jesus instead of feeding 4000 started a bread-breaking
fund-raising how-else-economy-is-economy business together with elders
even i would invite them to Realm of Monsters as dear co-owners
now i eat you so prepare your final plea
even dust of open-source wiki programs we shake off of Buckbeak's hoofs
but be sure - peer-to-peer programs including new competitive games
- are climbing like Honnold on El Sendero Luminosa
no projects no experiments no docs and issue-discussions-scarthcing
on top of our heads
no money-donate-ads-coins-jobs-sponsor deadly poison
programs who are guests not workers
alive and singing with their won voice like John Mayer Vultures at LA Live
better than what Borg of money can collective-gram
are flying towards target like Hawkeye's arrows along with Pat Brown
and Impossible Foods mission
both will be served in vegan jars of
treasure-from-a-sunken-pirate-wreck parens ( )
you wish you were nice and shinyyy!
Jon Stewart: you cant just read the prompter?
Colbert: i'm reading the prompter in here (points to heart) - you can
read that pablum