As of 950cf6016c, the mediawiki/core repo was updated to use DB_REPLICA
instead of DB_SLAVE, with the old constant left as an alias. This is part
of a string of commits that cleaned up the mixed use of "replica" and
"slave" by sticking to the former. Extensions have not been mass
converted. Please use the new constant in any new code.
The word "replica" is a bit more indicative of a broader range of DB
setups*, is used by a range of large companies**, and is more neutral in
connotations.
Drupal and Django made similar updates (even replacing the word "master"):
* https://www.drupal.org/node/2275877
* https://github.com/django/django/pull/2692/files &
https://github.com/django/django/commit/beec05686ccc3bee8461f9a5a02c607a023…
I don't plan on doing anything to DB_MASTER, since it seems fine by itself,
like "master copy", "master tape" or "master key". This is analogous to a
master RDBMs database. Even multi-master RDBMs systems tend to have a
stronger consistency than classic RDBMs slave servers, and present
themselves as one logical "master" or "authoritative" copy. Even in it's
personified form, a "master" database can readily be thought of as
analogous to "controller", "governer", "ruler", lead "officer", or such.**
* clusters using two-phase commit, galera using certification-based
replication, multi-master circular replication, ect...
**
https://en.wikipedia.org/wiki/Master/slave_(technology)#Appropriateness_of_…
***
http://www.merriam-webster.com/dictionary/master?utm_campaign=sd&utm_medium…
--
-Aaron
// sorry for cross-posting
Hello,
A lot of heated discussion occur on talk pages – thus, edit conflicts
happen on talk pages a lot. To be able to solve these more effectively, the
Technical Wishes team at Wikimedia Germany is designing an additional user
interface for this situation. This interface is shown to you when you write
on a discussion page and another person writes a discussion post in the
same line and saves it before you do. With this additional editing conflict
interface you can adjust the order of the comments and edit your comment.
If you'd like to know more about this feature, please visit the project
page [1].
This interface is created as a result of the Technical Wishes survey [2] in
2015, in which the German Wikipedia community wished for a simpler way to
resolve edit conflicts. For regular edit conflicts on article pages, the two
column conflict user interface was created, which has been available as a
beta feature since November 2018. The plan is to make this additional
interface for talk pages available in a few months.
We are inviting everyone to have a look at the planned feature and let us
know what you think on our central feedback page [3]! -- For the Technical
Wishes Team: Max Klemm
[1]
https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Edit_Conflicts#Edit_c…
[2]
https://de.wikipedia.org/wiki/Wikipedia:Umfragen/Technische_W%C3%BCnsche_20…
[3] https://www.mediawiki.org/wiki/Help_talk:Two_Column_Edit_Conflict_View
--
Max Klemm
Working Student Community Communication for Technical Wishes
Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Phone: +49 (0)30 219 158 26-0https://wikimedia.de
Imagine a world in which every single human being can freely share in
the sum of all knowledge. Help us to achieve our
vision!https://spenden.wikimedia.de
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.
FYI:
https://blog.mozilla.org/blog/2020/03/31/moss-launches-covid-19-solutions-f…
>From the announcement: *"Mozilla is announcing today the creation of a
COVID-19 Solutions Fund as part of the Mozilla Open Source Support Program
(MOSS). Through this fund, we will provide awards of up to $50,000 each to
open source technology projects which are responding to the COVID-19
pandemic in some way. *
*The MOSS Program, created in 2015, broadens access, increases security,
and empowers users by providing catalytic funding to open source
technologists. We have already seen inspiring examples of open source
technology being used to increase the capacity of the world’s healthcare
systems to cope with this crisis. For example, just a few days ago, the
University of Florida Center for Safety, Simulation, and Advanced Learning
Technologies released an open source ventilator
<https://simulation.health.ufl.edu/technology-development/open-source-ventil…>.
We believe there are many more life-saving open source technologies in the
world.*
*As part of the COVID-19 Solutions Fund, we will accept applications that
are hardware (e.g., an open source ventilator), software (e.g., a platform
that connects hospitals with people who have 3D printers who can print
parts for that open source ventilator), as well as software that solves for
secondary effects of COVID-19 (e.g., a browser plugin that combats COVID
related misinformation)."*
--
Jonathan T. Morgan
Senior Design Researcher
Wikimedia Foundation
User:Jmorgan (WMF) <https://meta.wikimedia.org/wiki/User:Jmorgan_(WMF)>
(Uses He/Him)
*Please note that I do not expect a response from you on evenings or
weekends*
The Search Platform Team
<https://www.mediawiki.org/wiki/Wikimedia_Search_Platform> usually holds
office hours the first Wednesday of each month. Come talk to us about
anything related to Wikimedia search!
Feel free to add your items to the Etherpad Agenda for the next meeting.
Details for our next meeting:
Date: Wednesday, April 1st, 2020
Time: 15:00-16:00 GMT / 08:00-09:00 PDT / 11:00-12:00 EDT / 17:00-18:00 CEST
Etherpad: https://etherpad.wikimedia.org/p/Search_Platform_Office_Hours
Google Meet link: https://meet.google.com/vyc-jvgq-dww
Join by phone in the US: +1 786-701-6904 PIN: 262 122 849#
Hope to talk to you tomorrow!
Trey Jones
Sr. Software Engineer, Search Platform
Wikimedia Foundation
UTC-4 / EDT
Hi all,
We just launched [[WM:Techblog]] <https://techblog.wikimedia.org/>, a new
place to share stories from the Wikimedia technical community with the
world. Yay!
We created this venue to provide a central place for people to share
stories about the technical work that they do— like:
-
How to run a top ten website that is all Open Source?
-
How do we make our codebase more modular and future-proof?
-
How do we come together to work on technical projects?
-
How to develop a product for many different languages?
-
How do new tools and bots help run Wikimedia projects?
-
What can we learn from data science and research?
-
And, much more…
Check out these posts for examples:
Computational knowledge: Wikidata, Wikidata query Service, and women who
are mayors!
<https://techblog.wikimedia.org/2020/03/24/computational-knowledge-wikidata-…>
By Trey Jones
Parsoid in PHP, or There and Back Again
<https://techblog.wikimedia.org/2020/03/24/parsoid-in-php-or-there-and-back-…>,
By S.Subramanya Sastry and C.Scott Ananian
Wikimedia projects have many intersections with the larger Open Source
community. It’s our hope that the technical blog will create more
visibility and conversations and provide information to a wider audience of
people who are interested in our work.
If you are interested in writing a blog post, read the editorial guidelines
<https://www.mediawiki.org/wiki/Wikimedia_technical_blog_editorial_guidelines>
to learn about what would make a good story and how to get published! We
manage the process of reviewing and publishing posts here:
https://phabricator.wikimedia.org/tag/Technical-blog-posts
Thanks to everyone who contributed to making the blog possible. There were
many!
For the WM Techblog team,
Sarah R. Rodlund
Technical Writer, Developer Advocacy
<https://meta.wikimedia.org/wiki/Developer_Advocacy>
srodlund(a)wikimedia.org
Hello Everyone,
It's time for Wikimedia Tech Talks 2020 Episode 2! This talk will take
place on *25 March 2020 at 6 PM UTC*.
*Title: *Understanding Wikimedia Maps and its challenges
*Speaker:* Mateus Santos, Software Engineer
*Summary: *The WMF Product Infrastructure Team has been maintaining the
Wikimedia Maps service for the last year and a half with help from SRE.
This talk will share the challenges and work of creating a better
development environment to enhance productivity, solve technical debt and
keep up with platform modernization.
The link to the Youtube Livestream can be found here:
https://www.youtube.com/watch?v=2LH-pYdi9Ks
During the live talk, you are invited to join the discussion on IRC at
#wikimedia-office
You can watch past Tech Talks here:
https://www.mediawiki.org/wiki/Tech_talks
If you are interested in giving your own tech talk, you can learn more
here:
https://www.mediawiki.org/wiki/Project:Calendar/How_to_schedule_an_event#Te…
Note: This is a public talk. Feel free to distribute through appropriate
email and social channels!
Kindly,
Sarah R. Rodlund
Technical Writer, Developer Advocacy
<https://meta.wikimedia.org/wiki/Developer_Advocacy>
srodlund(a)wikimedia.org
