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
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
Hi, what would you like to see in gerrit or improved? I've been working been working on developing a plugin that pull's in zuul's status into PolyGerrit. See the running demo at https://imgur.com/a/uBk2oxQ . Im also planning on adding "recheck" and "check experimental" as buttons to PolyGerrit's ui to improve CI. This will help new users who can recheck (and existing users that either forgot they can type this or haven't learned yet).
Note that i cannot promise that anything suggested in this thread will be worked on, but i can try my best.
See tasks https://phabricator.wikimedia.org/T214068 and https://phabricator.wikimedia.org/T214631 .
Hi!
Wikimetrics <https://metrics.wmflabs.org/> development has been frozen
since 2017, and we Analytics consider it's time to sunset this tool. Its
last day of operation will be March 24th, 2019.
If you're a Wikimetrics user, please consider working with Event Metrics
<https://eventmetrics.wmflabs.org/>, a newer tool that, like Wikimetrics,
allows to gather statistics on cohorts of wiki users. It has been running
for one year now, has great documentation
<https://meta.wikimedia.org/wiki/Event_Metrics>, and is supported by
the Community
Tech <https://meta.wikimedia.org/wiki/Community_Tech> team.
For more information, you can read this Phabricator task
<https://phabricator.wikimedia.org/T211835>.
Please, post any questions or comments in there.
Thanks!
--
*Marcel Ruiz Forns** (he/him)*
Analytics Developer @ Wikimedia Foundation
Hello all,
I am Manimaran. I am Free Software Activist and also android developer. I
try to make app for contributing Wiktionary. Which help to record audio
then upload to commons.
I share my efforts to my blog. I face some problem on development. Any one
can help me.
*Blog* :
https://manimaran96.wordpress.com/2019/01/06/spell4wiki-mobile-app-to-recor…
*Source code* : https://github.com/manimaran96/Spell4Wiki
*APK file* :
https://github.com/manimaran96/Spell4Wiki/blob/master/apk_file/spell4wiki_1…
*Issue*
- When Uploading audio I got an error message* ->
*{“error”:{“code”:”permissiondenied”,”info”:”The
action you have requested is limited to users in one of the groups:
[[Wikipedia:Autoconfirmed users|Autoconfirmed users]],
[[Wikipedia:Administrators|Administrators]], [[Wikipedia:User access
levels#Confirmed|Confirmed users]].”,”*”:”See
https://en.wikipedia.org/w/api.phpfor API usage. Subscribe to the
mediawiki-api-announce mailing list at <
https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce>
for notice of API deprecations and breaking changes.”},”servedby”:”mw1226″}
- But My User name is confirmed via mail. Also Have permission to
upload. Then I don’t know why comes this type of issue.
- Also trying with other wikipedians username same error comes all of
them.
This is just another small reminder that, because the servers which host
tiles.wmflabs.org and wma.wmflabs.org (wikiminiatlas) and overpass-wiki
run on a version of the OS (Ubuntu Trusty) that is no longer supported (and
hasn't been available for new instances since november 2017).
These services need maintainers and support by community members in order
to keep them alive after dec 18th (after which wmflabs will phase out those
versions) and before the EOL of early 2019 of the OS. Unfortunately it
seems no one is stepping up so far to convert these machines.
This issue is tracked at https://phabricator.wikimedia.org/T204506
As I was curious, I looked around on the tile server a bit and used what I
could find to update
https://wikitech.wikimedia.org/wiki/OSM_Tileserver#Technology_stack
This is all the information that I could gather, but i'm FAR from sure if
that is complete information and if I would break anything with a rebuild
basing myself on that info, so any information on missing elements etc.
would be appreciated. I've not gotten around to looking at wikiminiatlas.
If the services are not rebuild then likely they will just disappear at
some point for all layer variants. This includes the mapnik, black and
white, hill shading, hike bike layers. As I have no idea how many users of
these services there are, it is hard to say what the effect of that would
be.
DJ
The Search Platform Team
<https://www.mediawiki.org/wiki/Wikimedia_Search_Platform> usually holds
office hours the first Wednesday of each month. Come ask us anything about
Wikimedia search!
We’re particularly interested in:
* Opportunities for collaboration—internally or externally to the Wikimedia
Foundation
* Challenges you have with on-wiki search, in any of the languages we
support
But we're happy to talk about anything search-related. Feel free to add
your items to the Etherpad Agenda for the next meeting.
Details for our next meeting:
Date: Wednesday, March 6th, 2018
Time: 16:00-17:00 GMT / 08:00-9:00 PST / 11:00-12:00 EST / 17:00-18:00 CET
Etherpad: https://etherpad.wikimedia.org/p/Search_Platform_Office_Hours
Google Meet link: https://meet.google.com/vyc-jvgq-dww
*N.B.:* Google Meet System Requirements
<https://support.google.com/meet/answer/7317473>
Trey Jones
Sr. Software Engineer, Search Platform
Wikimedia Foundation
Currently, there's a patch under review [0] to enable a PHP sniff which
would detect so called "Pointless conditionals". These are conditionals
(if...else or ternary) where both branches only assign or return a boolean
value, and which could potentially one-lined using the if condition. T
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi,
It's Thursday :)
I wanted to say thank you this week to Zoranzoki21 and Matěj Suchánek
for jumping on the phan migration and helping with upgrading
extensions to take advantage of newer static analysis tools.
- -- Legoktm
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE2MtZ8F27ngU4xIGd8QX4EBsFJpsFAlx4MmcACgkQ8QX4EBsF
JptmvhAAkDQYXwVrQq+DOsX1pJGh0c5lNLrUWfZnnMZo2s3Nsao5uPIbxp0jO/RR
2upf5XreCttpq/NscKyidHWrrlT9ASdOuphrGrssZDTISOez8+4fiBKGRKKmPRqn
ejyJ5evj4Imv4uZOGCj0rxOCOYSfqPSiKBs27n8XpjM/i1uDGwZfHlQaT0zxCEN0
NuJ4CZ7FZp3fYA+QE4wdqhv/hb4qfdmg9JEuudMn3e6B51U4detmCED3yHuQQEEf
zDKDhk4SvGfzP5QMaGDR/Qskeb3WCbWDQJJaprAdrAvPk71FWQYxhYjFYYp3GgCp
14KMAhADkTE7GcSMuHuJyDgvAzshiQZHfOVwVsK+EJop5yvIhZ8ypHRhN3bn5xKF
MnOyKlZtf0B6cIRGJnW93T1kN2q8D0iUMT/fNM14v9Bl95/CICpRkB31DCewDlb0
zlna5YehBIge/V8HcIS5G1Et7NpdFBHjHcs23226KDwmqPM0Da6jfQiKgAQ+uNTk
EeMAPe3v2+gSy9biFCRDxNhmMgM4+zsECvXdLzV8fA4J8wTW19SCwJ+YrKSGQpxk
848kSzX+KQuUP8N7aRfuLQCOM49hQQMGDWpZ1CUhwUJEXhNEP7GGESDZQXG4s6h3
hmUA4XrwqdrYSVBq3bg03GlM0O28GXYQrJXQMkpas/7izLugLVE=
=M1a1
-----END PGP SIGNATURE-----
The Release Engineering team has started a working group to discuss
and consider our future continuous integration tooling. Please help!
The RelEng team is working with SRE to build a continuous delivery and
deployment pipeline, as well as changing production to run things in
containers under Kubernetes. We aim to improve the process of making
changes to software behind our various sites by making it take less
effort, happen faster, be less risky, and as automated as possible.
The developers will have a better development experience, be more
empowered, and more productive.
Wikimedia has had a CI system for many years now, but is based on
versions of tools that are reaching the end of their useful life.
Those tools need to be upgraded, and this will probably require
further changes due to how the new versions function. This is a good
point to consider what tools and functionality we need and want.
The working group is tasked to consider the needs and wants, and
evaluate the available options, and make a recommendation of what to
use in the future. The deadline is March 25. The work is being
documented at https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/CI_Future…
and we're currently collecting requirements and candidates to
evaluate.
We would welcome any feedback on those! Via IRC (#wikimedia-pipeline),
on the talk page of the working group's wiki page above, or as a
comment to the blog post below. Or as a reply to this email.
(Also at
https://phabricator.wikimedia.org/phame/post/view/148/choosing_tools_for_co…)