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
I've been meaning to document this for a while.
If you're finding yourself visiting Special:Export/Import often for the
purpose of MediaWiki development there is a much better way to get content
into your local wiki for testing purposes.
This short video explains how MobileFrontend extension provides tooling to
help you debug live on-wiki content via $wgMFContentProviderClass [1]
https://youtu.be/uRQzjN0hBlY
Hope it saves someone lots of time!
[1]
https://github.com/wikimedia/mediawiki-extensions-MobileFrontend/blob/maste…
--
Jon Robson
Senior Software Engineer
Following the recent outage, we've had a new series of complaints
about the lack of improvements in CX, especially related to
server-side activities like saving/publishing pages.
Now, I know the team is involved in a long-term effort to merge the
editor with the VE, but is there an end in sight for that effort? Can
I tell people who ask "look, 6 more months then we'll have a much
better translation tool"?
Is there a publicly available roadmap for this project and more
generally, for CX?
Thanks,
Strainu
Hello and thank you.
What do you mean in country named "--"?
Igal (User:IKhitron)
On Feb 15, 2018 00:15, "Nuria Ruiz" <nuria(a)wikimedia.org> wrote:
Hello from Analytics team:
Just a brief note to announce that Wikistats 2.0 includes data about
pageviews per project per country for the current month.
Take a look, pageviews for Spanish Wikipedia this current month:
https://stats.wikimedia.org/v2/#/es.wikipedia.org/reading/
pageviews-by-country
Data is also available programatically vi APIs:
https://wikitech.wikimedia.org/wiki/Analytics/AQS/
Pageviews#Pageviews_split_by_country
We will be deploying small UI tweaks during this week but please explore
and let us know what you think.
Thanks,
Nuria
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
TL;DR see <https://phabricator.wikimedia.org/T179461> for a proposed
naming change.
I proposed in Phabricator a wile ago [0] that we adopt the term
"Wikimedia developer account" across our wikis and other documentation
for the LDAP-backed user accounts that are created using
wikitech.wikimedia.org.
These same sign-on credentials are used for:
* wikitech.wikimedia.org
* Gerrit
* Phabricator (optionally)
* toolsadmin.wikimedia.org
* horizon.wikimedia.org
* ssh-based "shell access" to Toolforge and Cloud VPS servers
* a variety of web services providing access to operational and
analytics data related to the Wikimedia services
There are plans [1][2] in various stages of progress to change things
about how developer accounts are created and managed. Breaking
assumptions in our documentation about the back-end storage system
(LDAP) and the front-end management interface (wikitech) will help
make these changes less disruptive. It also helps remove another
lingering "labs" reference that the Cloud Services rebranding efforts
have been trying to address.
This change probably has almost no impact on existing technical
community members. It is really just targeted at making things a bit
less confusing for newcomers.
If you have thoughts or concerns about this proposal, please describe
them on the Phabricator task [0]. I'm proposing that on or about March
23rd (4 weeks from the date of this message) the comments on the task
will be evaluated for consensus and an approve/deny decision.
[0]: https://phabricator.wikimedia.org/T179461
[1]: https://phabricator.wikimedia.org/T161859
[2]: https://phabricator.wikimedia.org/T179463
Thanks,
Bryan
--
Bryan Davis Wikimedia Foundation <bd808(a)wikimedia.org>
[[m:User:BDavis_(WMF)]] Manager, Cloud Services Boise, ID USA
irc: bd808 v:415.839.6885 x6855
I was checking sixdegreesofwikipedia.com [0] and I saw that it implements
an application-driven breath-first search [1], like many other gadgets for
Wikipedia.
Very recently I have been experimenting with recursive Common Table
Expressions [2], which are or will be available on the latest versions of
MySQL and MariaDB.
With a single query on can obtain all titles directly or indirectly in a
category:
WITH RECURSIVE cte (cl_from, cl_type) AS
(
SELECT cl_from, cl_type FROM categorylinks WHERE cl_to =
'Database_management_systems' -- starting category
UNION
SELECT categorylinks.cl_from, categorylinks.cl_type FROM cte JOIN page ON
cl_from = page_id JOIN categorylinks ON page_title = cl_to WHERE cte.cl_type
= 'subcat' -- subcat addition on each iteration
)
SELECT page_title FROM cte JOIN page ON cl_from = page_id WHERE
page_namespace = 0 ORDER BY page_title; -- printing only articles in the end
, ordered by title
(it is more complex than needed because table denormalization, other
examples would be much simpler)
Thanks to CTEs, we can traverse hierarchies, without the need of external
tools, in a single SQL query and much more efficiently-- it doesn't need an
external application.
None of these features are present on the minimum required versions of
Mediawiki, or the latest version available on WMF servers-- but I wonder if
people- Mediawiki hackers and Tools creators- would be interested on doing
those?
[0] <https://www.sixdegreesofwikipedia.com>
[1] <
https://github.com/jwngr/sdow/blob/master/sdow/breadth_first_search.py#L36>
[2] <
https://dbahire.com/mysql-8-0-new-features-in-real-life-applications-roles-…
>
---------- Forwarded message ----------
From: mathieu stumpf guntz <psychoslave(a)culture-libre.org>
Date: Tue, Feb 27, 2018 at 11:17 AM
Subject: Re: [Wikitech-l] [Wikimedia-l] What's making you happy this week?
(Week of 18 February 2018)
To: Wikimedia Mailing List <wikimedia-l(a)lists.wikimedia.org>, Pine W <
wiki.pine(a)gmail.com>, "wikitech-l(a)lists.wikimedia.org" <
wikitech-l(a)lists.wikimedia.org>
What's making me happy this week is joining the "Telegrafo" discussion for
ELISo <https://t.me/joinchat/CQ8tET7pcCXQSBO1ERPJug> and I also just found
Six Degrees of Wikipedia <https://www.sixdegreesofwikipedia.com/?source=Peace&target=Epistemology>.
Le 18/02/2018 à 23:12, Pine W a écrit :
> What's making me happy this week is Isarra's persistence in working on the
> Timeless skin. Timeless is based on Winter. [0] [1]
>
> For anyone who would like to try Timeless, it's available in Preferences
> under Appearance / Skin.
>
> What's making you happy this week?
>
> Pine
> ( https://meta.wikimedia.org/wiki/User:Pine )
>
> [0] https://www.mediawiki.org/wiki/Skin:Timeless
> [1] https://www.mediawiki.org/wiki/Winter
> _______________________________________________
> Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wik
> i/Mailing_lists/Guidelines and https://meta.wikimedia.org/wiki/Wikimedia-l
> New messages to: Wikimedia-l(a)lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> <mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe>
>
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
--
Jaime Crespo
<http://wikimedia.org>
https://www.mediawiki.org/wiki/Scrum_of_scrums/2018-02-28
= 2018-02-28 =
*please come prepared with status of quarterly goal dependencies*
== Callouts ==
* Fundraising campaign in Sweden2018-02-06 - 2018-03-06 and Italy
2018-02-01- 2018-02-27:
https://meta.wikimedia.org/wiki/CentralNotice/Calendar
* Review from Wikidata search: https://gerrit.wikimedia.org/r/c/380895/
* MediaWiki Platform: We received a request from Legal to collaborate on a
Voluntary Product Accessibility Template (VPAT) in response to a request
from the US Nuclear Regulatory Commission, since they want to use MediaWiki
and need a VPAT in order to do so. We have begun reaching out to people to
see what is necessary to make this happen. If anybody has familiarity with
creating a VPAT, please reach out to Cindy Cicalese.
== Audiences ==
=== Readers ===
==== iOS native app ====
* Blocked by:
* Blocking:
* Updates:
** Continuing work on 5.8.0 - Synced Reading Lists (
https://phabricator.wikimedia.org/tag/ios-app-v5.8.0-manatee-on-a-skateboar…
)
==== Android native app ====
* Blocked by: Reading Lists schema/api deployments
* Blocking:
* Updates:
** Finalizing work on reading lists sync (completed user testing, ready for
beta)
==== Readers Web ====
* Blocked by:
* Blocking:
* Updates:
**
*Quarterly goal dependency update:
** Increase learning by lowering the cost of exploration
*** Reading Web/Performance
** Continue improving the ways that users can download articles of interest
for later consumption
*** Reading Web: Tech Ops/RelEng
==== Readers Infrastructure ====
* Blocked by:
** SRE on Reading Lists schema change
https://phabricator.wikimedia.org/T188048
** Wikidata on code review for description overrides
https://phabricator.wikimedia.org/T184000
* Blocking:
** Android on Reading Lists beta
* Updates:
**
==== Multimedia ====
* Updates
** Extension:3D on all wikis (to support embedding files; not allow uploads)
** MediaInfo work progressing
** SDC search work progressing
* Quarterly goal dependency update
** Prepare backend infrastructure for structured data search
*** SDC: Search PF/Multimedia/Wikidata
** Wikimedia Technology/Goals/2017-18 Q3#Segment 2: Search integration and
exposure
*** SDC: Research/Multimedia
** Prepare backend infrastructure for structured data search
*** SDC: Search PF/Multimedia/Wikidata
=== Contributors ===
==== Community Tech ====
* Blocked by:
* Blocking:
* Updates:
** Pings from summary going to production in a week or two
** Thanks for log entries progressing well
==== Anti-Harassment Tools ====
* Blocked by: None
* Blocking: None
* Updates:
** Continuing work on Interaction Timeline (
https://tools.wmflabs.org/interaction-timeline/)
** Start Work on Blocking Tools
==== Editing ====
* Blocked by:
* Blocking:
** Updates: VIsual diffs, auto-save
==== Maps ====
* Blocked by: Services
* Blocking: None
** Updates
==== Parsing ====
* Blocked by:
* Blocking:
* Updates:
** Reminder: RFC discussion today about whitespace stripping and Tidy (
https://phabricator.wikimedia.org/T157418 )
** Linter: some requested features and replacing estimated counts with more
accurate counts is stalled for a bit. Kunal is overcommitted and cannot
work on it. We are investigating what we could do that doesn't require too
many db schema changes, but will pick it up soon.
*Quarterly goal dependency update:
** Support work towards unifying MediaWiki's parser implementations, in
liaison with Technology's MediaWiki team
*** Parsing:Mediawiki PF/Services
*** Platform -- in regular discussion with Tim / Kunal; Linter dependency
(update as above)
*** Services -- in regular discussion with them; They need to figure out
storage / cache issues for variants and whether they need any special API
end points on the Parsoid end.
==== Collaboration ====
* Blocked by:
* Blocking: SRE on Flow dumps
* Updates:
** Flow dumps work on the back burner right now because of urgent things
that came up
** ORES deployed to svwiki and simplewiki on Monday, going to eswiki and
eswiktionary on Wednesday
** Flow beta feature opt-outs are broken again, looks like it's caused by
MCR changes but we're not sure, still stumped. Going to investigate this
next week.
==== Language ====
* Blocked by:
* Blocking:
* Updates:
**
=== Audiences Design ===
* Blocked by:
* Blocking:
* Updates:
**
* Quarterly goal dependency update:
** Audiences Design Standardise our user interfaces to match user
expectation of quality from our products
*** Audiences Design: Ops
==== UI Standardization ====
* Blocked by:
* Blocking:
* Updates:
** No OOUI rel this week, but several changes on build process already in
master, thanks to OOUI contributors
*** Also merged is “align toolbar items' focus to widgets elsewhere”
https://phabricator.wikimedia.org/T188031 will be in next week's rel
** Style Guide:
*** more build updates, and improved contributors' documentation and
workflows
*** Additions to “Illustrations” section
*** Upcoming are content changes on “Color palette” and “Typography“
== Technology ==
=== Analytics ===
* Blocked by:
* Blocking:
* Updates:
**
* Quarterly goal dependency update:
**Improve, adjust, or create features geared at the needs identified in New
Editors research project.
*** New Editors Experience:Analytics
=== Cloud Services ===
* Blocked by:
* Blocking:
* Updates:
**
=== Fundraising Tech ===
* Blocked by:
* Blocking:
* Updates:
** Getting close to real-money tests on new API for main card processor
** Making our Civi geocoding available as a standard extension, fixing
other geo-search Civi stuff
** Kicking off CentralNotice consultations with performance team
** Processing batch refunds for donors affected by confusing recurring
toggle
=== MediaWiki Platform ===
* Blocked by:
* Blocking:
* Updates:
** Actor table: merged!
*** Working to update extensions that need updating due to changes in core
tables for the actor table patch
** Comment table
*** follow up schema change still in progress
*** WRITE_BOTH enabled on group 1, will probably be enabled everywhere this
week
** TemplateStyles: VE breakage was found and fixed
** We received a request from Legal to collaborate on a Voluntary Product
Accessibility Template (VPAT) in response to a request from the US Nuclear
Regulatory Commission, since they want to use MediaWiki and need a VPAT in
order to do so. We have begun reaching out to people to see what is
necessary to make this happen.
*Quarterly goal dependency update:
** Support work towards unifying MediaWiki's parser implementations, in
liaison with Technology's MediaWiki team
*** Parsing:Mediawiki PF/Services
* Reduce product and technical debt to modernise our tools and
technologies, and to make future changes more effective and efficient
*** Parsing/Mediawiki PF
**1.1 It is possible to store structured data within wiki pages, in
particular on media file pages on Commons. We will enable the MediaWiki
storage layer to correctly store and process structured data elements
within wiki pages.
*** SDC: Mediawiki PF/Wikidata
=== Performance ===
* Blocked by:
** N/A
* Blocking:
** Analytics, need to get ZMQ turned off for our final app so they can
disable the crossloader
* Updates:
** Met w/ FRTech about CentralNotice, about to kick of performance
evaluation.
** Moved WebPageTest collection to running on Linux, teams that use WPT
metrics (Reading, Portal) will need to switch their dashboards. Peter will
write up instructions and email a link to them out later in the week.
** Private wiki Thumbor deployed. Wiki writeup on that published.
Completes a quarterly goal.
** mcrouter deploy has been potentially scrapped due to SRE concerns about
the project state (no maintenance releases, etc). Evaluating pushing
forward with Dynomite instead. Puts a Quarterly Goal for Multi-DC at risk.
** ResourceLoader dropped Grade A support for IE10
** Pubished lit review of existing Performance Perception studies:
https://www.mediawiki.org/wiki/Wikimedia_Performance_Team/Perceived_Perform…
** Deploying NavTiming collection for Singapore and a few other countries
in order to support new cache site rollout
=== Release Engineering ===
* Blocked by:
* Blocking:
* Updates:
**
*Quarterly goal dependency update:
** Continue improving the ways that users can download articles of interest
for later consumption
*** Reading Web: Tech Ops/RelEng
** Update:
*
=== Research ===
* Blocked by:
* Blocking:
* Updates:
*Quarterly goal dependency update:
** Wikimedia Technology/Goals/2017-18 Q3#Segment 2: Search integration and
exposure
*** SDC: Research/Multimedia
** Update:
*
=== Scoring Platform ===
* Blocked by: Security - JADE extension security review
https://phabricator.wikimedia.org/T188308
* Blocking: None
* Updates:
** Working with word embeddings (word2vec) to make predictions more
accurate and utilize NLP more -- we know Search is also interested in word
embeddings
** Automating makefile generation for building AI models -- this will make
our model building environment more scale-able and add support for more
wikis and more models faster
** We're working with Collab on auditing ORES filters deployments:
https://phabricator.wikimedia.org/T187836
** MVP deployment of JADE to beta cluster coming (post security review --
Blocked on that)
=== Search Platform ===
* Blocked by:
* Blocking:
* Updates:
- Improved wiktionary sister search relevancy by switching to title
search https://phabricator.wikimedia.org/T185250
- Added regex search for intitle:
https://phabricator.wikimedia.org/T156474
- Kafka poller for WDQS merged, testing:
https://phabricator.wikimedia.org/T185951
- Had some issues with categories sync to WDQS, fixed & added monitoring
to it: https://phabricator.wikimedia.org/T188293
- Working on query parsing refactoring:
https://phabricator.wikimedia.org/T185108
- Working on Serbian analyzer for ES:
https://phabricator.wikimedia.org/T183015
- Working on making Wikidata items appear in completion searches faster:
https://phabricator.wikimedia.org/T183053
*Quarterly goal dependency update:
** Prepare backend infrastructure for structured data search
*** SDC: Search PF/Multimedia/Wikidata
** Update:
*
=== Security ===
* Blocked by:
* Blocking:
* Updates:
**
=== Services ===
* Blocked by: none
* Blocking: none
* Updates:
** New HTML summary is still being slowly rolled out in collaboration with
Reading, prepared to pull next switch whenever
** refreshLinks job switched to kafka for all but wikipedias and
wiktionaries. Monitoring potential issues
** cdnPurge job will be switched this week
** Kudos to Luca and Analytics for deploying burrow kafka lag monitoring
*Quarterly goal dependency update:
** Parsoid: designing the storage for language variants
=== Site Reliability Engineering ===
* Blocked by:
** Collaboration on Flow dumps per usual
https://phabricator.wikimedia.org/T164262
* Blocking:
** Reading-Web on chromium-render deploy
https://phabricator.wikimedia.org/T186748
* Updates:
** Working on getting eqsin (Singapore) live
** 2 issues with HHVM and mediawiki last week caused very minor outages (
https://phabricator.wikimedia.org/T188019andhttps://phabricator.wikimedia.org/T184048 )
** A lot of hardware refreshing ongoing
*Quarterly goal dependency update:
** Continue improving the ways that users can download articles of interest
for later consumption
*** Reading Web: Tech Ops/RelEng
** Update: chromium-render deploy new service request came in, internal
discussions started
*
** Audiences DesignStandardise our user interfaces to match user
expectation of quality from our products
*** Audiences Design: Ops
** Update:
*
== Wikidata ==
* Blocked by:
* Blocking:
** Aware of https://phabricator.wikimedia.org/T184000 (review of SHORTDESC
magic word and API)
** Aware of https://gerrit.wikimedia.org/r/380895 (Search requesting final
"Go!")
* Updates:
** Incident report on QualityConstraints caching:
https://wikitech.wikimedia.org/wiki/Incident_documentation/20180226-Wikibas…
** Readable links for Lexeme references used in Statements:
https://phabricator.wikimedia.org/T1854997
** Disable Senses for the first Lexeme release:
https://phabricator.wikimedia.org/T186995
*Quarterly goal dependency update:
**1.1 It is possible to store structured data within wiki pages, in
particular on media file pages on Commons. We will enable the MediaWiki
storage layer to correctly store and process structured data elements
within wiki pages.
*** SDC: Mediawiki PF/Wikidata
** Update:
* Recent patch by the Multimedia team unblocked and ready.
** Prepare backend infrastructure for structured data search
*** SDC: Search PF/Multimedia/Wikidata
** Update:
*
== German Technical Wishlist ==
* Blocked by:
* Blocking:
* Updates:
**