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
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
Hey all,
TL;DR: In April 2017, the jQuery library in MediaWiki core was upgraded
from 1.x
to 3.x (the current stable version), with the jQuery Migrate plugin enabled
to
ease migration. We temporarily still load jQuery 1.x on Wikimedia wikis.
Read about the API changes at https://jquery.com/upgrade-guide/3.0/
== Upgrade guide ==
An overview of the important changes is available at:
https://jquery.com/upgrade-guide/3.0/
This page also contains advice on how to migrate your code. In most cases
it involves fairly
simple changes, such as using a different method name, or adding quotes in
selectors.
The vast majority of the added requirements and removed methods are
restored through
the jQuery Migrate plugin with a deprecation warning in the console. As
such, it's unlikely
your code will require any immediate changes.
If you do find a deprecation warning in the console, you can use the
warning documentation
to find out more:
https://github.com/jquery/jquery-migrate/blob/e967c3b98b/warnings.md
Once jQuery 3 is in Wikimedia production (with jQuery Migrate) it will be
easy to
find uses of deprecated methods with the deprecation warnings. However, you
don't
need to wait for August to start migrating. The methods removed in jQuery 3
have
been deprecated for a while already, and their replacements are already
available
in jQuery 1.x in production, today.
== Timeline ==
* April 2017: jQuery 3 lands in MediaWiki core master with jQuery Migrate
plugin.
* April to July 2017: Testing and fixing of issues arising from the switch.
* July 2017: jQuery 3 enabled in Wikimedia's Beta Cluster. [1]
* August 2017: jQuery 3 enabled on Wikimedia wikis in production.
jQuery 3 will also be released as part of MediaWiki 1.30.0 (expected in
November 2017). [2]
As part of MediaWiki 1.30, inclusion of jQuery Migrate will made
configurable so that sites
that have already migrated may disable the plugin for better run-time
performance.
Track progress at <https://phabricator.wikimedia.org/T124742>.
-- Krinkle
[1] https://www.mediawiki.org/wiki/Beta_Cluster
[2] https://www.mediawiki.org/wiki/MediaWiki_1.30
Apologies for cross-posting
Call for Posters & Demos
SEMANTiCS 2017 - The Linked Data Conference
13th International Conference on Semantic Systems
Amsterdam, Netherlands
September 11 -14, 2017
http://2017.semantics.cc
For details please go to: https://2017.semantics.cc/calls
Important Dates (Posters & Demos Track):
*Submission Deadline: July 10, 2017 (11:59 pm, Hawaii time)
*Notification of Acceptance: August 10, 2017 (11:59 pm, Hawaii time)
*Camera-Ready Paper: August 18, 2017 (11:59 pm, Hawaii time)
As in the previous years, SEMANTiCS’17 proceedings will be published by
ACM ICPS (pending) and CEUR WS proceedings.
This year, SEMANTiCS features a special Data Science track, which is an
opportunity to bring together researchers and practitioners interested
in data science and its intersection with Linked Data to present their
ideas and discuss the most important scientific, technical and
socio-economical challenges of this emerging field.
SEMANTiCS 2017 will especially welcome submissions for the following hot
topics:
*Metadata, Versioning and Data Quality Management
*Semantics for Safety, Security & Privacy
*Web Semantics, Linked (Open) Data & schema.org
*Corporate Knowledge Graphs
*Knowledge Integration and Language Technologies
*Economics of Data, Data Services and Data Ecosystems
Special Track (please check appropriate topic in submission system)
*Data Science
Following the success of previous years, we welcome any submissions
related but not limited to the following ‘horizontal’ (research) and
‘vertical’ (industries) topics:
Horizontals:
*Enterprise Linked Data & Data Integration
*Knowledge Discovery & Intelligent Search
*Business Models, Governance & Data Strategies
*Semantics in Big Data
*Text Analytics
*Data Portals & Knowledge Visualization
*Semantic Information Management
*Document Management & Content Management
*Terminology, Thesaurus & Ontology Management
*Smart Connectivity, Networking & Interlinking
*Smart Data & Semantics in IoT
*Semantics for IT Safety & Security
*Semantic Rules, Policies & Licensing
*Community, Social & Societal Aspects
Data Science Special Track Horizontals:
*Large-Scale Data Processing (stream processing, handling large-scale
graphs)
*Data Analytics (Machine Learning, Predictive Analytics, Network Analytics)
*Communicating Data (Data Visualization, UX & Interaction Design,
Crowdsourcing)
*Cross-cutting Issues (Ethics, Privacy, Security, Provenance)
Verticals:
*Industry & Engineering
*Life Sciences & Health Care
*Public Administration
*e-Science
*Digital Humanities
*Galleries, Libraries, Archives & Museums (GLAM)
*Education & eLearning
*Media & Data Journalism
*Publishing, Marketing & Advertising
*Tourism & Recreation
*Financial & Insurance Industry
*Telecommunication & Mobile Services
*Sustainable Development: Climate, Water, Air, Ecology
*Energy, Smart Homes & Smart Grids
*Food, Agriculture & Farming
*Safety, Security & Privacy
*Transport, Environment & Geospatial
Posters & Demos Track
The Posters & Demonstrations Track invites innovative work in progress,
late-breaking research and innovation results, and smaller contributions
in all fields related to the broadly understood Semantic Web. These
include submissions on innovative applications with impact on end users
such as demos of solutions that users may test or that are yet in the
conceptual phase, but are worth discussing, and also applications, use
cases or pieces of code that may attract developers and potential
research or business partners. This also concerns new data sets made
publicly available.
The informal setting of the Posters & Demonstrations Track encourages
participants to present innovations to the research community, business
users and find new partners or clients and engage in discussions about
the presented work. Such discussions can be invaluable inputs for the
future work of the presenters, while offering conference participants an
effective way to broaden their knowledge of the emerging research trends
and to network with other researchers.
Poster and demo submissions should consist of a paper that describe the
work, its contribution to the field or novelty aspects. Submissions must
be original and must not have been submitted for publication elsewhere.
Accepted papers will be published in HTML (RASH) in CEUR and, as such,
the camera-ready version of the papers will be required in HTML,
following the poster and demo guidelines (https://goo.gl/3BEpV7). Papers
should be submitted through EasyChair
(https://easychair.org/conferences/?conf=semantics2017 and should be
less than 2200 words in length (equivalent to 4 pages), including the
whole content of the paper.
For the initial reviewing phase, authors may submit a PDF version of the
paper following any layout. After acceptance, authors are required to
submit the camera-ready in HTML (RASH).
Submissions will be reviewed by experienced and knowledgeable
researchers and practitioners; each submission will receive detailed
feedback. For demos, we encourage authors to include links enabling the
reviewers to test the application or review the component.
For details please go to: https://2017.semantics.cc/calls
*https://www.mediawiki.org/wiki/Scrum_of_scrums/2017-06-28
<https://www.mediawiki.org/wiki/Scrum_of_scrums/2017-06-28>*
*= 2017-06-28 =*
*contact: https://www.mediawiki.org/wiki/Wikimedia_Engineering
<https://www.mediawiki.org/wiki/Wikimedia_Engineering>*
== Callouts ==
* Ops: +2 needed on https://gerrit.wikimedia.org/r/359417 to remove
disabled image handling from VCL
* RelEng: Potential widespread thumbnail problems on beta cluster
https://phabricator.wikimedia.org/T169114
* Thursday 29th, codfw row A switch upgrade:
https://phabricator.wikimedia.org/T168462 : expect ~10min downtime per rack
== Audiences ==
=== Readers ===
==== iOS native app ====
* Blocked by: None
* Blocking: None
* Updates: 5.5.0 released, 5.5.1 pending
==== Android native app ====
* Blocked by: n/a
* Blocking: n/a
* Updates: (all ongoing)
** working on reading list syncing UI, eagerly awaiting the backend service
** Stephen working on cross-platform CSS/JS consolidation
** working on hiring an engineer, about to kick off hiring a PM
==== Reading Web ====
* Blocked by:
i18n/parsing: Your guidance is requested on Translate tag doesn't get
parsed on action=parse[https://phabricator.wikimedia.org/T168743 ]
Release engineering team: More an FYI, ee'd like to switch all our browser
tests to Node.js. Not clear of timeline for
https://phabricator.wikimedia.org/T164721 Run WebdriverIO tests in CI for
extensions for planning purposes.
Ops: +2 needed on https://gerrit.wikimedia.org/r/359417 to remove disabled
image handling from VCL
* Blocking: n/a (please let us know)
* Updates:
** Working with services team to spec out a new HTML summary endpoint
service. (https://phabricator.wikimedia.org/T113094) - if you are using
TextExtracts you may want to keep an eye on changes. Bug fixes are coming.
** Starting to prepare for some updates to desktop print styles and
sunsetting OCG
==== Reading Infrastructure ====
* Blocked by:
* Blocking:
* Updates:
** working on OCG replacement (current approach: Electron with PDF
post-processing - T168871)
** starting work on Reading List Service
** measuring payload size changes from Parsoid to read-html - T164033
** stripping reference list contents - T168875
==== Multimedia ====
* Blocked by: Potential widespread thumbnail problems on beta cluster -
RelEng? https://phabricator.wikimedia.org/T169114
* Blocking: N/A
* Updates: 3D mass-upload test went well - but see above re: thumbnails.
Not currently sure what a large number of 3d2png runs will do to
performance.
==== Discovery ====
* Blocked by: n/a
* Blocking: n/a
* Updates: Working on 'explore similar' feature for SRP :
https://www.mediawiki.org/wiki/Cross-wiki_Search_Result_Improvements/explor…
- instrumenting this feature for an upcoming AB test.
=== Community Tech ===
* Blocked by: No blockers
* Blocking: N/A
* Updates:
- * XTools rewrite ongoing (http://xtools.wmflabs.org/)
- * LoginNotify roll-out ongoing
- * CodeMirror beta feature rolling out to Test Wikipedia next week (
https://www.mediawiki.org/wiki/Extension:CodeMirror)
- * Ongoing work on RangeContributions
=== Contributors ===
==== Editing ====
* Blocked by:
* Blocking:
* Updates:
==== Parsing ====
* Updates:
** Redlinks, disambig links, and redirect links are now handled in Parsoid
as well -- went live on Monday. Also bumped HTML version to 1.5.0.
** Linter went live on all wikis last week and now we are working on an
announcement to use this to get wikis to start fixing pages that would
break when Tidy is replaced. High priority issues (
https://www.mediawiki.org/wiki/Help:Extension:Linter#High-priority_lint_iss…
)
should be addressed.
** Parsoid language variants patch is getting final reviews and tweaks
before it is merged for RT testing. A followup patch will address rendering
a page in the requested variant.
==== Collaboration ====
* Blocked by: None
* Blocking: Ops on Flow dumps (is this
https://phabricator.wikimedia.org/T164262 ?)
* Updates:
** We will soon merge changes to make HTMLUsersMultiselectWidget work
properly, see https://gerrit.wikimedia.org/r/#/c/357963/
** This will be used for the Echo blacklist feature:
https://phabricator.wikimedia.org/T150419
** Work on RCFilters beta feature improvements continues
==== Language ====
* Blocked by: None
* Blocking: None
* Updates:
** Work on CX migration to OOjs + fixes continue.
** Minor updates to Apertium spa-cat language pair deployed.
** Kartik working with Services for new CX API end points.
==== Contributors Design ====
* Blocked by:
* Blocking:
* Updates:
== Technology ==
=== Analytics ===
* Blocked by:
* Blocking:
* Updates:
** Add cummulative fields to MediaWiki history data set (user revision
count, seconds elapsed since last revision) and improve format of timestamp
** Fixing a couple inconsistencies in webrequest tagging code
** Continuing work on Wikistats2 front-end, we got a repository in
Differential, we will push an initial version to it in short.
** Renaming of unique devices project wide metric to unique devices per
project family
** Getting ready for execution of EL purging script, (finalizing
white-list, making columns on EL DB nullable, bug fixes for the script)
=== Cloud Services ===
* Blocked by:
* Blocking:
* Updates:
=== Fundraising Tech ===
* Blocked by: -
* Blocking: -
* Updates:
* Minor CentralNotice features to improve Fundraising workflow
* Minor CiviCRM issues
* Usual onslaught of payment processor integration maintenance
* Slow week because a few team are members away
=== MediaWiki Platform ===
* Blocked by:
* Blocking:
* Updates:
=== Performance ===
* Blocked by:
* Blocking:
* Updates:
=== Release Engineering ===
* Blocked by:
* Blocking:
* Updates:
=== Research ===
* Blocked by:
* Blocking:
* Updates:
=== Scoring Platform ===
* Blocked by:
* Blocking:
* Updates:
** ORES intermittently unavailable for around 7 hours on 2017-06-23
*** https://wikitech.wikimedia.org/wiki/Incident_documentation/20170623-ORES
=== Search Platform ===
* Blocked by: none
* Blocking: none
* Updates:
** Continuing work on ML-assistend ranking. xgboost selected as modeling
library (https://phabricator.wikimedia.org/T162061)
** Working on fixing breakage in non-Cirrus phrase search (
https://phabricator.wikimedia.org/T167798)
** Working on Q1 goals
=== Security ===
* Blocked by:
* Blocking:
* Updates:
=== Services ===
* Blocked by: none
* Blocking: none as far as we know
* Updates:
** Automatic rerendering of HTML to bump the version to 1.5.0 -
elevated VE latencies for a while
** Red links support in Change Propagation
=== Technical Operations ===
* Blocked by: Flow dumps blocked on Collab Team, they are already aware
* Blocking: none
* Updates:
** ORES had intermittent issues on the 23rd. Long debugging session with
multiple teams. Many thanks to Subbu for figuring out the root cause!!
** Goals are being wrapped up
** Thursday 29th, codfw row A switch upgrade:
https://phabricator.wikimedia.org/T168462 : expect ~10min downtime per rack
== Wikidata ==
* No blockers.
* Wikidata is finally in the "enhanced" versions of recent changes and
watchlist! https://phabricator.wikimedia.org/T46874
* Creating Special:PageData as a canonical entry point for machine readable
page data: https://phabricator.wikimedia.org/T163923
* More work on the Lexeme UI: https://phabricator.wikimedia.org/T165567
* Working on replacing deprecated ApiErrorReporting code.
== German Technical Wishlist ==
* No blockers (as I'm aware of).
* Sneak-peak at currently running survey: http://tools.wmflabs.org/twl17/