Hi folks,
One thing we'd love to get better at is taking and publishing useful
notes from our meetings. An example of that is ArchCom meetings, for
which we have been taking notes for a while, but I haven't gotten
around to publishing. Another example is our weekly tech Engineering
Tech managers meetings, which are increasing in importance as we head
into budget setting season.
Is there anyone available to be a volunteer scribe for ArchCom and/or
Tech/Eng management meetings? For logistical reasons, I would prefer
existing WMF employee offers over non-WMF offers, but beggars can't be
choosers ;-)
The next meeting opportunity is in 15 hours: the ArchCom is having
it's weekly 1pm PST (21:00 UTC) meeting just prior to the 2pm PST
public IRC meeting. If you're interested, please let me know! The
best way to express your volunteer interest is by adding your sig on
the bottom of this page:
<https://www.mediawiki.org/wiki/User:RobLa-WMF/Scribes>
...and discussion is welcomed on the associated talk page.
Rob
---------- Forwarded message ----------
From: Chen Davidi <chen(a)wikimedia.org.il>
Date: Wed, Dec 23, 2015 at 9:02 AM
Subject: [Wikitech-ambassadors] Wikimedia Hackathon Jerusalem 2016:
registration is now open!
To: wikitech-ambassadors(a)lists.wikimedia.org, wikitech-l(a)lists.wikimedia.org,
wikitech-announce(a)lists.wikimedia.org, engineering(a)lists.wikimedia.org,
wikimedia-l(a)lists.wikimedia.org
Hi everyone,
I'm thrilled to tell you all that the registration for Wikimedia Hackathon
2016 is now open!
The Hackathon will be held in Jerusalem, between March 31st to April 3rd,
2016, by Wikimedia Israel.
Scholarship applications are open until January 22nd.
You know the drill!
Registration here -
https://docs.google.com/forms/d/17WFRHTCX5_dnCD5hFk1gHEQUz6pTrKp85QsX01rJGa…
More info and updates on
https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2016
If you have any questions, please contact us at
hackathon2016(a)wikimedia.org.il
Hope to see you all in Jerusalem!
Chen Davidi-Almog,
Activity & Resources Coordinator.
Wikimedia Israel
An Outreachy candidate for http://mediawiki.org/wiki/Accuracy_review who
went ahead and started unpaid has been making good progress, and is about
to land the central guts of the project on github. It's a new way to
transition from creating to maintaining Wikipedia articles, with an
emphasis on detecting outdated statistics, fighting bias including paid
advocacy of all kinds, and proofreading WEP student work. It's been going
slow, mostly because the original trial run architecture was too dependent
on email.
However, before she gets there, could one or two people who are maybe
beginner or intermediate with Python but advanced with Mediawiki or PHP
please test her user authentication and login framework?
https://github.com/priyankamandikal/wikireview/
<https://github.com/priyankamandikal/wikireview/issues>
It's built for PythonAnywhere because it shouldn't run on Wikimedia
servers, because of the safe harbor DMCA provisions precluding editorial
control by web hosts. Please report any issues on github and note your
results on the Phabricator task to prevent duplication of effort.
Thanks in advance!
Best regards,
Jim Salsman
Hi folks,
Over the past few weeks (including WikiDev '16) we've had several
conversations the Wikimedia software development governance model.
For a lot of people, the most important aspect of this is MediaWiki.
More generally, though, the scope is about we deploy to Wikimedia
sites that we intend to maintain, enhance, and further leverage.
On Wednesday, January 20, we intend to continue this conversation, and
welcome your participation:
<https://phabricator.wikimedia.org/E135>
In particular, we plan to discuss the work that Gabriel Wicke started:
<https://phabricator.wikimedia.org/T123606>
"WIP RFC: Improving and scaling our technical decision making process"
...which is mainly a pointer to:
<https://www.mediawiki.org/wiki/Requests_for_comment/Governance>
I've quoted the current text as of this writing below, and you're
welcome to reply on list or on the talk page (though let's try to
ensure a summary of important comments gets captured on T123606).
Based on the conversations I've been part of (and Gabriel's initial
writeup), Rust's governance model seems to be the leading candidate to
iterate toward. This doesn't necessarily mean making one big change
with a fanfare-laden launch, but let's discuss.
Wait until Wednesday's IRC session if you have to (22:00 UTC, 14:00
PST), but we'd love to hear your thoughts sooner.
Rob
p.s. Here's the link to the RFC
<https://www.mediawiki.org/wiki/Requests_for_comment/Governance>
...and below is the plain text from [mw:Requests for comment/Governance].
Problem statement
[Goal: Describe the problem we are seeing with the current process,
and why it is important to solve them.]
Difficulty of making clear and accepted decisions on important and
broad topics.
Scaling the decision making process.
Stakeholder involvement & legitimacy.
Clarity and transparency of decision making process.
Prior art
[Goal: Give a brief summary and pointers to options we looked at.]
IETF process
Python PEP process
Rust
Debian
W3C
See also this prior etherpad discussion.
Strawman proposal
[Goal: Summarize key ideas that we consider worth adopting, and point
to prior art. Provide rationale by explaining how each addresses
specific issues.]
More structured RFC decision process
Based on the Rust decision making process.
Nominate a shepherd from a (sub)team to guide an RFC through the process.
Makes sure that stakeholders are informed.
Guides the discussion.
Once the discussion plateaus or stalls & in coordination with
the RFC author(s), announces and widely publicizes a "Final Comment
Period", which is one week.
At the end of the "Final Comment Period", the (sub)team decides
based on the points made in the RFC discussion, and justifies its
decision based on the overall project principles and priorities. If
any new facts or aspects are surfaced in this discussion, a new Final
Comment Period needs to be started before making a decision.
Scaling the decision making process with sub-teams
Based on Rust subteams.
The core team is responsible for creating sub-teams, with a member
of the core team as its team leader. Initial membership is determined
by the leader, later changes are by consensus within the team.
Each sub-team has a specific vision and problem set to work on,
and the team leader is responsible for keeping the team on topic.
Sub-teams are empowered to decide on RFCs within their scope. The
team leader is responsible for elevating RFCs with unclear or broader
scope to the core team.
Henning,
If we're going to solve the problem of dead links, it needs to involve
automation, at least for the heavy lifting. Obviously, if a human
contributor can add a better source, that's great. But there are more dead
links than people willing to replace them.
On English Wikipedia, there's Category:All articles with dead external
links, and it contains more than 134,000 articles[1] -- and those are just
the pages where somebody's added the Dead link template. There are a lot of
missing references -- not just on English WP, but on all the projects --
and connecting those links to a live archive makes them useful again.
For links that were moved, we may be able to collect and use that
information -- I know that we're looking into what kind of metadata we can
collect when a new link is added to the page. But I think finding
alternative sources has to come from human contributors, and that's hard to
scale.
Danny
PM, Community Tech
[1]:
https://en.wikipedia.org/wiki/Category:All_articles_with_dead_external_links
On Mon, Dec 28, 2015 at 9:51 AM, Henning Schlottmann <h.schlottmann(a)gmx.net>
wrote:
> On 16.12.2015 21:12, Danny Horn wrote:
>
> > #1. Migrate dead links to the Wayback Machine (111 support votes)
>
> I really hope, you don't follow that wish, as it is detrimental to the
> quality of Wikipedia.
>
> Switching dead links to the archive is a move to a dead end, instead of
> looking for
>
> a) the new correct URL, as many links were just moved.
> b) alternative sources for the same fact.
>
> Ciao Henning
>
>
>
> _______________________________________________
> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
> 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>
>
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.