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
Every year or so the Cloud Services team tries to identify and clean up
unused projects and VMs. We do this via an opt-in process: anyone can
mark a project as 'in use,' and that project will be preserved for
another year.
I've created a wiki page the lists all existing projects, here:
https://wikitech.wikimedia.org/wiki/News/Cloud_VPS_2019_Purge
If you are a VPS user, please visit that page and mark any projects that
you use as {{Used}}. Note that it's not necessary for you to be a
project admin to mark something -- if you know that you're currently
using a resource and want to keep using it, go ahead and mark it
accordingly. If you /are/ a project admin, please take a moment to mark
which VMs are or aren't used in your projects.
When December arrives, I will shut down and begin the process of
reclaiming resources from unused projects.
If you think you use a VPS project but aren't sure which, I encourage
you to poke around on https://tools.wmflabs.org/openstack-browser/ to
see what looks familiar. Worst case, just email
cloud(a)lists.wikimedia.org with a description of your use case and we'll
sort it out there.
Exclusive toolforge users are free to ignore this task.
Thank you!
-Andrew and WMCS team
Hello,
We have requested a 30 minutes read-only window for s6 wikis (T235475) for
the 19th Nov from 05:00-05:30 AM UTC to switchover that section primary
database master (T235469)
db1061 is an old host and out of warranty that will be decommissioned
(T217396). The new master will be db1131.
We are going to do this on Tuesday 19th Nov from 05:00 to 05:30 AM UTC (we
do not expect to use the 30 minutes window, if everything goes as expected).
Impact: Writes will be blocked on the following wikis
frwiki
jawiki
ruwiki
Reads will remain unaffected.
Communication will happen at #wikimedia-operations
If you are around at that time and want to help with the monitoring, please
join us!
Thanks
Hello,
We have requested a 30 minutes read-only window for s1 (enwiki) (T234801)
for the 14th November from 05:00-05:30 AM UTC to switchover that section
primary database master (T234800)
db1067 is an old host and out of warranty that will be decommissioned
(T217396). The new master will be db1083
We are going to do this on Thursday 14th Nov from 05:00 to 05:30 AM UTC (we
do not expect to use the 30 minutes window, if everything goes as expected).
Impact: Writes will be blocked on the following wiki:
enwiki
Reads will remain unaffected.
Communication will happen at #wikimedia-operations
If you are around at that time and want to help with the monitoring, please
join us!
Thanks
*Note that the time is different for this session because of Daylight
Savings time and a scheduling conflict.*
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, Nov 6th, 2019
Time: 17:00-18:00 GMT / 09:00-10:00 PST / 12:00-13:00 EST / 18:00-19:00 CST
Etherpad: https://etherpad.wikimedia.org/p/Search_Platform_Office_Hours
Google Meet link: https://meet.google.com/vyc-jvgq-dww
Hope to talk to you in a week!
—Trey
Trey Jones
Sr. Software Engineer, Search Platform
Wikimedia Foundation
UTC-4 / EDT
Is there a “special” way in mediawiki to get parameters passed by URL or do you just use the conventional PHP way ($_GET)? I am trying to check if “Special:CreateAccount?reason=“ is set/has a value (and what that value is).
Thank you for your assistance, trying to be convention compliant.
-TheSandDoctor
Hi,
For HTML version see
https://www.mediawiki.org/wiki/Scrum_of_scrums/2019-10-30
Željko
--
= 2019-10-30 =
== Callouts ==
* SRE: Product Infrastructure needs advice on making requests to
third-party APIs from MediaWiki. Please see [[phab:T236797]]
* CPT: SRE Infrastructure foundations Blocked by CPT on service-runner PR,
requesting follow-up https://github.com/wikimedia/service-runner/pull/221
* Release Engineering
** Next week train last train (1.35.0-wmf.5 - [[phab:T233853]]) is the last
train before two week break
** v3 of architecture document for new continuous integration wants review
and feedback [[User:LarsWirzenius/NewCI]]
== Product ==
=== Editing ===
* Updates:
** Developing talk pages prototype v1.0: Replying to specific comments
=== Growth ===
* Updates:
** Mobile summary for suggested edits (task [[phab:T235810]])
** Newcomer tasks: task explanation widget (task [[phab:T235046]])
** Mobile homepage: Don't clone module DOM in overlays
** Homepage: Refactor StartEditing.js to not use global selectors
** Homepage: Refactor SuggestedEditsModule to not use global selectors
** Suggested Edits: Add placeholder image (task [[phab:T232423]])
** Suggested Edits: Implement difficulty filters (task [[phab:T235042]])
** Suggested Edits: Save task types to user preference (task
[[phab:T235042]])
=== iOS native app ===
* Blocked by:
** Core Platform I think? (Need last followup wikidiff2 patch, version++ &
release for section info returned in JSON [[gerrit:546231]])
* Updates:
** 6.4.1 in testing
***3D touch fix in article view
** 6.5 in active development - [[phab:project/view/4245]]
*** History & diffs feature (user testing this week)
*** Blocked by last followup wikidiff2 patch, version++ & release
[[gerrit:546231]]
=== Android native app ===
* Updates:
** Finishing up API provisions work with PI team, in preparation for a
major release with Suggested Edits V3 feature.
**App now supports the red bordered announcement for fundraising.
=== Product Infrastructure ===
* Blocked by:
* SRE: Product Infrastructure needs advice on making requests to
third-party APIs from MediaWiki. Please see [[phab:T236797]]
* Updates:
** Aiming to enable the MachineVision extension in production (Commons and
Test Commons only) ASAP (pending results of security and performance
reviews)
*** Note: For an initial, two-week testing period, the extension
functionality will only be exposed to specific testing users
=== Structured Data ===
* Blocking:
** Search Platform: Data dumps for SDC: [[phab:T221917]]
=== Inuka ===
* Updates:
** KaiOS app search feature: [[phab:T236262]]
** KaiOS app article pagination: [[phab:T234436]]
=== UI Standardization ===
* Updates:
** Design Style Guide
*** “Components” section: Finishing up basic components for official
publication [[phab:T229333]] & [[phab:T217154]]
*** Changing over to scap deployment of Style Guide to enable Git LFS for
large binary files
** OOUI release this week delayed, cause Volker being sick
== Technology ==
=== Fundraising Tech ===
* Blocking:
** Release Engineering: [Low priority] Fundraising Tech: Code review on
[[gerrit:544071]] appreciated to unblock [[phab:T192167]]
* Updates:
** Tweaks to monthly conversion form to ensure donors don't continue seeing
banners [[phab:T235209]]
** Investigating data discrepancies in initial tests of new CentralNotice
data pipeline.
** CentralNotice: Reviewing contractor-written code for sub-national
targeting. [[phab:T226438]]
** CiviCRM: More improvements for contact record de-duplication
=== Core Platform ===
* Blocking:
**iOS - Need last followup wikidiff2 patch, version++ & release for section
info returned in compare endpoint [[gerrit:546231]]
***Will need to pass in those section byte offsets for it to work
** SRE Infrastructure foundations Blocked by CPT on service-runner PR,
requesting follow-up https://github.com/wikimedia/service-runner/pull/221
* Updates:
** Finishing page history API
** Starting minimal client API
** Rolling out new echo notification storage on test wikis
** Supporting rollout of Parsoid/PHP
=== Engineering Productivity ===
==== Release Engineering ====
* Blocked:
** Site Reliability Engineering: logstash-beta.wmflabs.org does not receive
any mediawiki events [[phab:T233134]]
** [Low priority] Fundraising Tech: Code review on [[gerrit:544071]]
appreciated to unblock [[phab:T192167]]
* Updates:
** v3 of architecture document for new continuous integration wants review
and feedback [[User:LarsWirzenius/NewCI]]
** Train Health
*** Last week: 1.35.0-wmf.3 - [[phab:T233851]]
*** This week: 1.35.0-wmf.4 - [[phab:T233852]]
*** Next week: 1.35.0-wmf.5 - [[phab:T233853]] - last train before two week
break
=== Scoring Platform ===
* Updates:
*** Catalan edit quality now can use Spanish Badwords (cross lingual
vandalism is interesting) [[phab:T223794]]
*** Complete design assets for Jade Entity UI [[phab:T212370]]
*** Jade API review continues. Thanks CPT! [[phab:T199834]]
*** (Still to be deployed) Limiting ORES requests to 50 rev_ids (was
documented, but not enforced) [[phab:T232005]]
*** New docs for Jade API [[Extension:Jade/API]] [[phab:T229968]]
*** mwoauth 0.3.7 is out with clean handling of Unicode
*** Fixed model info label-ordering issue in revscoring. [[phab:T229445]]
*** Starting a spike for OOUIJS for Jade UI. [[phab:T208819]]
*** Continued refactoring of revscoring to handle session-based modeling
work [[phab:T231214]]
=== Search Platform ===
* Blocked by:
** Structured Data: Data dumps for SDC: [[phab:T221917]]
* Updates:
** Re-indexed Slovak-language wikis with improved analysis chain:
[[phab:T223787]]
** The highlighter will no longer break surrogate pairs - [[phab:T234613]]
** Analysis of new "Did You Mean" suggestion results - [[phab:T232760]]
** Sister search was temporarily broken, and fixed - [[phab:T235778]]
=== Security ===
* Updates:
** Review the FileImporter extension's load of config from wiki pages for
security concerns, in-progress high priority, [[phab:T202071]]
** Security readiness review for the MachineVision extension, in-progress
and nearing completion, [[phab:T227346]]
** Security concept review for newcomer tasks on Special:Homepage,
in-progress and nearing completion, [[phab:T235720]]
** Final date for submitting Data Map / GDPR updates will be Nov 30.
=== Site Reliability Engineering ===
* Blocked by:
** CPT: SRE Infrastructure foundations Blocked by CPT on service-runner PR,
requesting follow-up https://github.com/wikimedia/service-runner/pull/221
* Blocking:
** Release Engineering: logstash-beta.wmflabs.org does not receive any
mediawiki events [[phab:T233134]]
** Product Infrastructure needs advice on making requests to third-party
APIs from MediaWiki. Please see [[phab:T236797]]