Apologies for cross-posting
<mailbox:///home/julia/.thunderbird/0xgpsb48.default/Mail/Local%20Folders/Trash?number=18993455&part=1.2.2&filename=486eca59914e673f7b637acad4ef4466efdf01db><mailbox:///home/julia/.thunderbird/0xgpsb48.default/Mail/Local%20Folders/Trash?number=18993455&part=1.2.2&filename=486eca59914e673f7b637acad4ef4466efdf01db>
Call for Research & Innovation Papers
SEMANTiCS 2016 - The Linked Data Conference
Transfer // Engineering // Community
12th International Conference on Semantic Systems
Leipzig, Germany
September 12 -15, 2016
http://2016.semantics.cc
<https://www.google.com/url?q=http://2016.semantics.cc/&sa=D&ust=14531132570…>
Important Dates (Research & Innovation)
* Abstract Submission Deadline: April 14, 2016 (11:59 pm, Hawaii time)
* Paper Submission Deadline: April 21, 2016 (11:59 pm, Hawaii time)
* Notification of Acceptance:May 26, 2016 (11:59 pm, Hawaii time)
* Camera-Ready Paper: June 16, 2016(11:59 pm, Hawaii time)
Submissions via Easychair:
https://easychair.org/conferences/?conf=semantics2016research
<https://www.google.com/url?q=https://easychair.org/conferences/?conf%3Dsema…>
As in the previous years, SEMANTiCS’16 proceedings are expected to be
published by ACM ICP.
The annual SEMANTiCS conference is the meeting place for professionals
who make semantic computing work, who understand its benefits and
encounter its limitations. Every year, SEMANTiCS attracts information
managers, IT-architects, software engineers and researchers from
organisations ranging from NPOs, through public administrations to the
largest companies in the world. Attendees learn from industry experts
and top researchers about emerging trends and topics in the fields of
semantic software, enterprise data, linked data & open data strategies,
methodologies in knowledge modelling and text & data analytics. The
SEMANTiCS community is highly diverse; attendees have responsibilities
in interlinking areas like knowledge management, technical
documentation, e-commerce, big data analytics, enterprise search,
document management, business intelligence and enterprise vocabulary
management.
The success of last year’s conference in Vienna with more than 280
attendees from 22 countries proves that SEMANTiCS 2016 will continue a
long tradition of bringing together colleagues from around the world.
There will be presentations on industry implementations, use case
prototypes, best practices, panels, papers and posters to discuss
semantic systems in birds-of-a-feather sessions as well as informal
settings. SEMANTICS addresses problems common among information
managers, software engineers, IT-architects and various specialist
departments working to develop, implement and/or evaluate semantic
software systems.
The SEMANTiCS program is a rich mix of technical talks, panel
discussions of important topics and presentations by people who make
things work - just like you. In addition, attendees can network with
experts in a variety of fields. These relationships provide great value
to organisations as they encounter subtle technical issues in any stage
of implementation. The expertise gained by SEMANTiCS attendees has a
long-term impact on their careers and organisations. These factors make
SEMANTiCS for our community the major industry related event across Europe.
SEMANTiCS 2016 will especially welcome submissions for the following hot
topics:
* Data Quality Management
* Data Science (Data Mining, Machine Learning, Network Analytics)
* Semantics on the Web, Linked (Open) Data & schema.org
* Corporate Knowledge Graphs
* Knowledge Integration and Language Technologies
* Economics of Data, Data Services and Data Ecosystems
Following the success of previous years, the ‘horizontals’ (research)
and ‘verticals’ (industries) below are of interest for the conference:
Horizontals
* Enterprise Linked Data & Data Integration
* Knowledge Discovery & Intelligent Search
* Business Models, Governance & Data Strategies
* 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
Verticals
* Industry & Engineering
* Life Sciences & Health Care
* Public Administration
* 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
* Transport, Environment & Geospatial
Research / Innovation Papers
The Research & Innovation track at SEMANTiCS welcomes the submission of
papers on novel scientific research and/or innovations relevant to the
topics of the conference. Submissions must be original and must not have
been submitted for publication elsewhere. The Research & Innovation
track at SEMANTiCS is a single-blind review process (author names are
visible to reviewers, reviewers stay anonymous). The submitted abstract
and the topics are leveraged to find adequate reviewers for submitted
papers. Please write an email to
semantics2016researchtrack(a)easychair.org
<mailto:semantics2016researchtrack@easychair.org>, if you have any
questions.
Papers should follow the ACM ICPS guidelines for formatting and must not
exceed 8 pages in length for full papers and 4 pages for short papers,
including references and optional appendices. The layout templates can
be found here:
http://www.acm.org/sigs/publications/proceedings-templates
<https://www.google.com/url?q=http://www.acm.org/sigs/publications/proceedin…>All
accepted full papers and short papers will be published in the digital
library of the ACM ICP Series. Research & Innovation papers should be
submitted through EasyChair at:
https://easychair.org/conferences/?conf=semantics2016research
<https://www.google.com/url?q=https://easychair.org/conferences/?conf%3Dsema…>.
Papers must be submitted in PDF (Adobe's Portable Document Format)
format. Other formats will not be accepted. For the camera-ready
version, the source files (Latex, WordPerfect, Word) will also be needed.
Important Dates (Research & Innovation)
* Abstract Submission Deadline: April 14, 2016 (11:59 pm, Hawaii time)
* Paper Submission Deadline: April 21, 2016 (11:59 pm, Hawaii time)
* Notification of Acceptance:May 26, 2016 (11:59 pm, Hawaii time)
* Camera-Ready Paper: June 16, 2016 (11:59 pm, Hawaii time)
Research and Innovation Chairs:
* Anna Fensel
<https://www.google.com/url?q=http://www.anna.fensel.com/&sa=D&ust=145311325…>,
University of Innsbruck
* Amrapali Zaveri
<https://www.google.com/url?q=http://dumontierlab.stanford.edu/&sa=D&ust=145…>,
Stanford University
Contact email address:semantics2016researchtrack@easychair.org
<mailto:semantics2016researchtrack@easychair.org>
Research and Innovation Deputy Chairs:
* Bernhard Haslhofer
<https://www.google.com/url?q=http://bernhardhaslhofer.info/&sa=D&ust=145311…>,
Austrian Institute of Technology
* Artem Revenko
<https://www.google.com/url?q=https://www.linkedin.com/in/artem-revenko-1831…>,
Semantic Web Company
Conference Chairs:
* Sebastian Hellmann
<https://www.google.com/url?q=http://aksw.org/SebastianHellmann.html&sa=D&us…>,
AKSW/KILT, InfAI, Leipzig University
* Tassilo Pellegrini
<https://www.google.com/url?q=https://en.wikipedia.org/wiki/Tassilo_Pellegri…>,
UAS St. Pölten
Senior Program Committee:
* Paul Buitelaar, Insight - National University of Ireland, Galway
* Oscar Corcho, Universidad Politécnica de Madrid
* Claudia D'Amato, University of Bari
* Brian Davis, DERI NUIG
* Victor de Boer, VU Amsterdam
* Christian Dirschl, Wolters Kluwer Germany
* Michel Dumontier, Stanford University
* Agata Filipowska, Department of Information Systems, Poznan
University of Economics
* Bernhard Haslhofer, AIT-Austrian Institute of Technology
* Sebastian Hellmann, AKSW/KILT, InfAI, Leipzig University
* Andreas Hotho, University of Wuerzburg
* Jose Emilio Labra Gayo, Universidad de Oviedo
* Peter Mika, Yahoo! Research
* Axel-Cyrille Ngonga Ngomo, University of Leipzig
* Josiane Xavier Parreira, Siemens AG Österreich
* Heiko Paulheim, University of Mannheim
* Tassilo Pellegrini, University of Applied Sciences St. Pölten
* Marta Sabou, Vienna University of Technology
* Harald Sack, Hasso-Plattner-Institute for IT Systems Engineering,
University of Potsdam
* Ruben Verborgh, Ghent University - iMinds
* Maria Esther Vidal, Universidad Simon Bolivar, Dept. Computer Science
Program Committee:
* Alessandro Adamou, Knowledge Media Institute, The Open University
* Rajendra Akerkar, Western Norway Research Institute
* Vladimir Alexiev, Ontotext Corp
* Jose María Alvarez Rodríguez, Carlos III University of Madrid
* Stefan Bischof, Siemens AG Österreich
* Volha Bryl, Springer Nature
* Irene Celino, CEFRIEL
* Pierre-Antoine, Champin LIRIS
* Roland Cornelissen, Metamatter
* Gianluca Correndo, University of Southampton
* Roberta Cuel, University of Trento
* Aba-Sah Dadzie, Knowledge Media Institute, The Open University
* Elena Demidova, L3S Research Center
* Tommaso Di Noia, Politecnico di Bari
* Marin Dimitrov, Ontotext
* Mauro Dragoni, Fondazione Bruno Kessler - FBK-IRST
* Samhaa El-Beltagy, Cairo University
* Ingo Feinerer, University of Applied Sciences Wiener Neustadt
* Javier D. Fernández, Computer Science Department. University of
Valladolid
* Fabien Gandon, Inria
* Jorge Garcia, Ontology Engineering Group, Universidad Politécnica de
Madrid
* Roberto Garcia, Universitat de Lleida
* José María García, University of Seville
* Alain Giboin, INRIA Sophia Antipolis - Méditerranée
* Juan Miguel Gómez-Berbís, Universidad Carlos III de Madrid
* Jose Manuel Gomez-Perez, Expert System
* Michael Granitzer, University of Passau
* Benjamin Heitmann, Insight Centre for Data Analytics, National
University of Ireland, Galway
* Eelco Herder, L3S Research Center
* Laura Hollink, CWI
* Katja Hose, Aalborg University
* Valentina Janev, Mihailo Pupin Institute, University of Belgrade
* Anja Jentzsch, Hasso Plattner Institut
* Ali Khalili, VU University Amsterdam
* Sabrina Kirrane, Vienna University of Economics and Business - WU Wien
* Dimitris Kontokostas, University of Leipzig
* Christoph Lange, University of Bonn
* Nelia Lasierra Beamonte, UMIT – University for Health Sciences,
Medical Informatics and Technology
* Isaac Lera, University of the Balearic Islands
* Steffen Lohmann, Fraunhofer IAIS
* Vanessa Lopez, IBM Research
* Sandra Lovrenčić, University of Zagreb, Faculty of organization and
informatics Varazdin
* Markus Luczak-Roesch, University of Southampton
* Elisa Marengo, Faculty of Computer Science, Free University of
Bozen-Bolzano
* John P. Mccrae, National University of Ireland, Galway
* Andras Micsik, SZTAKI
* Andrea Moro Sapienza, Università di Roma
* Dmitry Mouromtsev, NRU ITMO, Russia
* Claudia Müller-Birn, Freie Universität Berlin
* Lyndon Nixon, MODUL University
* Inna Novalija, Jozef Stefan Institute
* Andrea Giovanni Nuzzolese, STLab, ISTC-CNR
* Leo Obrst, MITRE
* Maryam Panahiazar, Stanford University
* Alexander Panchenko, Université catholique de Louvain
* Viviana Patti, University of Turin
* Silvio Peroni, University of Bologna
* Xiuquan Qiao, Beijing University of Posts and Telecommunications
* Achim Rettinger, Karlsruhe Institute of Technology
* Mariano Rico, Universidad Politécnica de Madrid
* Giuseppe Rizzo, ISMB
* Marco Rospocher, Fondazione Bruno Kessler
* Matthew Rowe, Lancaster University
* Anisa Rula, University of Milano-Bicocca
* Felix Sasaki, W3C
* Vadim Savenkov, Vienna University of Economics and Business (WU)
* Francois Scharffe, 3Top
* Luciano Serafini, Fondazione Bruno Kessler
* Pavel Shvaiko, Informatica Trentina
* Nadine Steinmetz, TU Ilmenau
* Holger Stenzhorn, Saarland University Hospital
* Simon Steyskal, Siemens AG Austria
* Vojtěch Svátek, University of Economics, Prague
* Konstantin Todorov, LIRMM
* Ioan Toma, STI Innsbruck
* Jürgen Umbrich, Vienna University of Economy and Business (WU)
* Joerg Waitelonis, Hasso-Plattner-Institute Potsdam
* Krzysztof Wecel, Poznan University of Economics
* Eva Zangerle, Databases and Information Systems, Department of
Computer Science, University of Innsbruck
Forwarding video links (:
---------- Forwarded message ----------
From: Pine W <wiki.pine(a)gmail.com>
Date: Sat, Jan 16, 2016 at 6:43 PM
Subject: Thank yous and video recordings for the Wikipedia 15 joint
celebrations (SF, NYC, and Seattle)
To:
<snip>
Video links to Youtube (Commons uploads will happen in the near future, I
believe):
* Welcome and lightning talks: https://www.youtube.com/watch?v=dGhxEpowM6A
* "Wikipedia's content gender gap":
https://www.youtube.com/watch?v=uW1WSVmpvwk
* "Stories from the weird old days":
https://www.youtube.com/watch?v=ZLmGc-hpp3U
* Panel discussion "The impact of 15 years of Wikipedia":
https://www.youtube.com/watch?v=CiEjkxCGmgU
Here's to the next 15 years!
Pine
While promotions are fairly insular, I think the wikitech community
would be happy to see this.
----- Forwarded message from Greg Grossmeier <greg(a)wikimedia.org> -----
> Date: Fri, 15 Jan 2016 14:32:54 -0800
> From: Greg Grossmeier <greg(a)wikimedia.org>
> To: "WMF Staff (All)" <wmfall(a)lists.wikimedia.org>
> Subject: Chad Horohoe promoted to Senior Software Engineer
>
> I'm more than pleased to announce that Chad Horohoe has been promoted to
> Senior Software Engineer.
>
> For those of you who don't know Chad, let me give a quick run down:
>
> 2005 - Started as a volunteer editor[0]
> 2008 - Became a MediaWiki developer[1]
> 2010 - Started contracting for WMF[2]
> 2012 - Became staff[3]
>
> Those are just the legal/contract related highlights; Chad has done a
> lot to help make the Wikimedia technology stack better. Everything from
> migrating us from SVN to Git, shepherding multiple RFCs, working with
> our upstream projects (HHVM, Phabricator, Gerrit), helped bring us our
> new search infrastructure (ElasticSearch), and is generally a great
> person to ask when no one else knows the history.
>
> Please join me in congratulating Chad!
>
> Greg
>
> [0] First edit:
> https://en.wikipedia.org/w/index.php?diff=prev&oldid=10508529
> [1] https://www.mediawiki.org/wiki/Special:Code/MediaWiki/35764
> [2] Shortly after being stuck in Berlin due to Eyjafjallajökull
> erupting. https://phabricator.wikimedia.org/T25223
> [3] Super secret ADP url, I couldn't find a good public reference.
>
>
> --
> | Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
> | identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |
----- End forwarded message -----
--
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |
I've been working with a number of colleagues getting ready to turn HTTPS
on by default for various loc.gov domains. This has been fairly successful
and we're working through the old legacy apps now.
When that work completes, we'll have somewhere around half a million links
which differ only in the URL scheme. What would be the best way to rewrite
all of those URLs? I'd like to reduce the window during which users transit
from HTTPS -> HTTP -> HTTPS.
If anyone's curious, I've been collecting the links for a few dozen wikis
in a somewhat oversized Git repo:
https://github.com/acdha/lc-wikipedia-links
The first site which has completely migrated is the much smaller World
Digital Library which has just under four thousand links:
https://gist.github.com/acdha/f785b22b356a9842439e
Thanks,
Chris
Please join for the following tech talk:
*Tech Talk**:* Creating Useful Dashboards with Grafana
*Presenter:* Timo Tijhof
*Date:* January 13, 2016
*Time: *21:30 UTC
<http://www.timeanddate.com/worldclock/fixedtime.html?msg=Timo+Tech+Talk&iso…>
Link to live YouTube stream <http://www.youtube.com/watch?v=UlL6UoRUQAM>
*IRC channel for questions/discussion:* #wikimedia-office
*Summary: *Over the past two years Timo has worked a lot with our metric
infrastructure and the various visualisation tools in use at Wikimedia. The
aim of this talk is to help you create better dashboards with Grafana. Timo
will discuss the various metric types we have, how they are gathered in our
software environments, and how you can use Graphite to query this data. He
will also share lessons learned in the Performance Team using real world
examples.
*TL;DR:* Stuff is changing. If you notice problems with session handling in
1.27.0-wmf.11, file a bug in Phabricator and CC me (Anomie) and Gergő (Tgr).
MediaWiki's authentication layer is getting a major overhaul! This will
allow us to do cool stuff like 2-factor authentication without the 2-factor
extension having to be redone for LdapAuth/CentralAuth/every-other-auth,
third-party login (e.g. Google, Facebook) without hacking around everything
with crazy hooks, and supporting more than just one authentication method
at a time.
Broadly speaking, this change involves the addition of two new things:
SessionManager (already merged, being deployed with 1.27.0-wmf.11) and
AuthManager (hopefully coming by the end of February).
- SessionManager replaces the use of PHP's $_SESSION and session_*()
functions and the UserLoadFromSession and UserSetCookies hooks with a more
extensible mechanism.
- AuthManager allows for independent pluggable authentication modules,
multiple authentication methods, and removes the assumption that all logins
can be handled with a one-page form having "username" and "password"
fields. No more needing to adjust every authentication extension to know
about every other authentication extension it might have to cooperate with.
However, the changes we're making do mean that various things are going to
need updating.
== For users ==
You shouldn't notice any changes due to SessionManager. If you do see
problems related to session handling in 1.27.0-wmf.11, file a bug in
Phabricator and CC me (Anomie) and Gergő (Tgr).
Once AuthManager comes around, the most visible change will be that the
login form will probably be a bit different, and if your browser remembers
your login information for you then you might have to re-enter it.
== For bots ==
You shouldn't notice any changes due to SessionManager, but do make sure
your code is handling cookies normally instead of using the deprecated
return values from action=login to construct cookies manually.[1] If you
are handling cookies properly and see problems related to session handling
in 1.27.0-wmf.11, file a bug in Phabricator and CC me (Anomie) and Gergő
(Tgr).
For AuthManager, the new features mean that unattended login might no
longer work since the login flow will now natively support user
interaction: the account might have 2-factor enabled, or might need a
password reset, or some other thing that requires user interaction. We've
created two ways to work around this:
- If possible, switch to OAuth. This week (1.27.0-wmf.10) "owner-only"
consumers are being rolled out to make this easier for bot operators: log
into your bot account, go to
https://meta.wikimedia.org/wiki/Special:OAuthConsumerRegistration/propose,
and create a consumer with the "This consumer is for use only by MyBotName"
checkbox checked.The consumer will be approved for use immediately, no
waiting or trying to find someone who can approve the consumer for you.
Owner-only consumers also don't tag every edit, since all the edits will be
from the one account anyway.
- If you need to continue using the existing action=login, next week
(1.27.0-wmf.11) we're rolling out Bot Passwords. This is something like
OAuth-lite, or Google's application passwords: go to Special:BotPasswords,
set one up, and then use new bot-password username and password to login as
you've always done (no code changes, just update your bot's configuration).
It's already live in Beta Labs if you want to test it out.
Login with the "main" account password will continue to work until
AuthManager is deployed, and might continue to work after that too (as long
as nothing requires user interaction).
For bots that run on third-party wikis, Bot Passwords are in core and are
enabled by default, but it's possible a wiki could disable them. OAuth is
an extension.
[1]:
https://lists.wikimedia.org/pipermail/mediawiki-api-announce/2015-December/…
== For user scripts and gadgets ==
Since user scripts and gadgets rely on the user already being logged in,
you shouldn't notice any changes.
== For core and extension developers ==
There's some other useful stuff that has already been merged, written as
part of the groundwork for this project:
- User::newSystemUser(), which replaces directly screwing around with
accounts when an extension needs a user for logged actions.
- Deprecation or removal of much of the password handling logic from the
User class. In particular User::getPassword() no longer works.
- CentralIdLookup, a generic mechanism for looking up a "central" ID for
cross-wiki features instead of everything needing that functionality having
to depend on CentralAuth (and on anything else that might implement global
accounts). If you have some sort of cross-wiki login extension that isn't
CentralAuth, you'll want to implement this class.
If you're dealing with session data,
- Don't use $_SESSION. Instead, use $request->getSession() or
SessionManager::getGlobalSession() to fetch a Session object and access the
data through it. Or continue to use the $request->getSessionData() and
$request->setSessionData() methods.
- Don't use session_id() to test if a session is active. Instead, fetch
a Session object as above and call ->isPersistent().
- Don't use wfSetupSession() to make sure a session is active. Instead,
fetch a Session object as above and call ->persist().
- Don't use the other PHP session_*() functions either.
If you're implementing the UserLoadFromSession hook to bypass the usual
cookie-based session handling (e.g. OAuth, SSLClientAuthentication, or
CentralAuth's centralauthtoken), you'll now want to implement a subclass of
the new SessionProvider class and add it to $wgSessionProviders. OTOH, if
you're using UserLoadFromSession because you're trying to add additional
security checks (e.g. SecureSessions), you'll probably want to look into
the new SessionMetadata and SessionCheckInfo hooks. And if you're using
UserLoadFromSession because you're doing some hack around MediaWiki's
existing login form, you'll want to wait for AuthManager. The same goes for
UserSetCookies.
If you maintain an authentication-related extension that does a login of
some sort, you'll eventually want to be implementing one of AuthManager's
AuthenticationProviders. In particular, an extension implementing
AuthPlugin now will want to implement a PrimaryAuthenticationProvider in
the future. If you're using the hooks that mess with the login form, such
as UserCreateForm or UserLoginForm, you'll likely also be wanting to
implement an AuthenticationProvider of some sort. Other hooks called from
LoginForm might also need attention. You can see the work-in-progress patch
at https://gerrit.wikimedia.org/r/#/c/195297/.
A more detailed overview of the new classes is available at
https://www.mediawiki.org/wiki/User:Anomie/SessionManager_and_AuthManager.
If you have more questions, feel free to ask (email works particularly
well).
== For apps that log in ==
Apps shouldn't notice any changes from SessionManager. If you do see
problems related to session handling in 1.27.0-wmf.11, file a bug in
Phabricator and CC me (Anomie) and Gergő (Tgr).
Once AuthManager comes out, though, you'll need to use the new API
action=clientlogin and action=query&meta=authmanagerinfo which will provide
the information necessary to construct a fully-functional login UI. More
details will be provided once I finish writing the new code ;) but be aware
that there's the possibility that you'll have to redirect to a third-party
website in there (e.g. if a "login with your Google account" extension
happens to be installed).
Do not be tempted to have your app somehow use bot passwords, that's not a
supported use case for that feature. A normal (not owner-only) OAuth
consumer would be fine.
== For operators of third-party wikis ==
If you're using $wgSessionsInObjectCache = false (which was the default
before SessionManager), note that that configuration is no longer
supported. Make sure $wgSessionCacheType is set to something that will
function well in your environment.
Other than that, things should mostly just work on upgrade with both
SessionManager and (in the future) AuthManager. If you use authentication-
or session-related extensions that aren't deployed on WMF wikis, however,
you may want to check with the maintainers of those extensions.
If you're using the OAuth extension, you should also be aware that its
$wgMWOAuthGrantPermissions and $wgMWOAuthGrantPermissionGroups settings are
replaced by the new core settings $wgGrantPermissions and
$wgGrantPermissionGroups.
Please report bugs related to these changes in Phabricator, and CC me
(Anomie) and Gergő (Tgr).
--
Brad Jorsch (Anomie)
Senior Software Engineer
Wikimedia Foundation
https://www.mediawiki.org/wiki/Scrum_of_scrums/2016-01-13
= 2015-01-13 =
== Reading ==
=== Android ===
*v2.1.137 beta published. Includes a new native article toolbar and lower
memory usage.
=== Reading Infrastructure ===
* Nothing blocked this week.
* SessionManager and bot passwords should be going out next week.
== Discovery ==
* Working on load test for Dallas cluster
* Load spikes on weekend for ES getting worse, cause not clear yet,
investigating ( https://grafana.wikimedia.org/dashboard/db/elasticsearch )
** Did some brainstorming, discovered queries generating a lot of ES calls
to handle variants, with very low success rate. Will investigate removing
them.
* Finalizing data models for TextCat language detection library, security
review next
* Testing for upgrading WDQS to Blazegraph 2.0 once it's released
* No blockers
== Community Tech ==
* Working on assessment report for Community Wishlist Top 10 results:
https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey/Top_10/Statu…
** Would like feedback from Wikidata, Multimedia, Analytics, and
Collaboration before publishing
* Working on dead link rescuing bot - talking with Tool Labs and IA
* Waiting on feedback from Kunal on Gadgets 2.0
* Wrapping up work on PageAssessments extension:
https://www.mediawiki.org/wiki/Extension:PageAssessments
== Infrastructure ==
=== RelEng ===
*Blocking: nothing
*Blocked on: nothing
*Updates:
** Differential migration discussion at WikiDev16 went really well, very
positive, no roadblocks placed
** Scap3 discussion at WikiDev16 also really positive, looking for more
early adopters
=== Technical Operations ===
*Blocking: nothing
*Blocked on: nothing
*Updates:
** Started work on the new Quarter goals
=== Services ===
* moved to Node 4.2 - RESTBase, Mobile Content Service, Mathoid
:* in progress: Graphoid and Citoid
* working on enabling pre-generation for Mobile Content Service
=== Security ===
* Should get to Kartographer this week
* Several patches to deploy this week
* Schedule your reviews!
=== Fundraising Tech ===
* cleaning up after December
* updating CiviCRM extensions to use new core features
== Editing ==
=== VisualEditor ===
*Blocking: nothing
*Blocked on: nothing
*Updates:
** Single Edit Tab work nearing completion. Planned to release to one wiki
next week if all goes well for validation before larger rollout.
** Note the OOUI breaking release from yesterday (in -wmf.11); no known
impacts.
=== Parsing ===
*Blocking: nothing
*Blocked on: nothing
*Updates
** Hoping to finish up (this week) puppetizing testing infrastructure on
ruthenium
** Coordinating with reading and services to reduce size of HTML payload.
=== Multimedia ===
*Blocking: nothing
*Blocked on: nothing
*Updates:
** Christmas A/B test for cross-wiki upload tool inconclusive. Not sure
what's next happening.
=== Language ===
*Blocking: nothing
*Blocked on: nothing
=== Collaboration ===
* Mostly Echo stuff. Cross-wiki notification stuff is getting closer.
* MediaWiki-Vagrant code for cross-wiki notifications is implemented and
almost merged. This will also facilitate other local multi-wiki testing,
e.g. Flow.
* Flow Nuke fix merged.
Hi everyone,
As many of you know (because you were here), we had the Wikimedia
Developer Summit 2016 last week. It was wonderful to see so many of
you! Rachel Farrand and Quim Gil ensured we had an excellent venue
and had a wonderful opportunity to work together, and the people here
had some great conversations. Valerie Aurora taught us a lot about
how to run effective meetings, which greatly increased the quality of
the discussions.
The conversations we started here are just that: a start. We covered
a lot of very important topics. Given the time and expense of
bringing everyone to one place, it would be a shame if the
conversations we started ended up needing to start over. Hence, it
was really important to have good notes, to make it easier to pick up
these conversations where we left off.
For many of the sessions, the notes made their way into the Phab task
associated with the meeting. The main WikiDev '16 landing page makes
it a bit easier to find the notes:
<https://www.mediawiki.org/wiki/WikiDev16>
The session leaders were very motivated to make sure we got something
out of the conversations they led, so they will be clarifying the next
steps on their respective sessions. It's certainly easier than it was
this time last week to find out what happened in each respective
session, but there's a lot of work to do. Please help us out!
Rachel sent out a survey to all of you who attended. Please fill this
out! It will help us figure out if we'd like to have another one like
this next year.
If you're interested in real time conversation about WikiDev '16,
either because you were there and want to follow up or you weren't
there and you want to learn what you missed, please attend the RFC
office hour in a few hours (Wednesday 22:00 UTC, 14:00 PST):
<https://phabricator.wikimedia.org/E134>
Rob
Hi everyone,
As many of you know (because you were here), we had the Wikimedia
Developer Summit 2016 last week. It was wonderful to see so many of
you! Rachel Farrand and Quim Gil ensured we had an excellent venue
and had a wonderful opportunity to work together, and the people here
had some great conversations. Valerie Aurora taught us a lot about
how to run effective meetings, which greatly increased the quality of
the discussions.
The conversations we started here are just that: a start. We covered
a lot of very important topics. Given the time and expense of
bringing everyone to one place, it would be a shame if the
conversations we started ended up needing to start over. Hence, it
was really important to have good notes, to make it easier to pick up
these conversations where we left off.
For many of the sessions, the notes made their way into the Phab task
associated with the meeting. The main WikiDev '16 landing page makes
it a bit easier to find the notes:
<https://www.mediawiki.org/wiki/WikiDev16>
The session leaders were very motivated to make sure we got something
out of the conversations they led, so they will be clarifying the next
steps on their respective sessions. It's certainly easier than it was
this time last week to find out what happened in each respective
session, but there's a lot of work to do. Please help us out!
Rachel sent out a survey to all of you who attended. Please fill this
out! It will help us figure out if we'd like to have another one like
this next year.
If you're interested in real time conversation about WikiDev '16,
either because you were there and want to follow up or you weren't
there and you want to learn what you missed, please attend the RFC
office hour in a few hours (Wednesday 22:00 UTC, 14:00 PST):
<https://phabricator.wikimedia.org/E134>
Rob