FYI. A performance regression was found and we rolled back all wikis to
1.25wmf14. Follow the bug mentioned for updates.
----- Forwarded message from Ori Livneh <ori(a)wikimedia.org> -----
> Date: Wed, 4 Feb 2015 02:49:37 -0800
> From: Ori Livneh <ori(a)wikimedia.org>
> To: "Development and Operations engineers (WMF only)" <engineering(a)lists.wikimedia.org>
> Subject: [Engineering] wmf15 performance regression
>
> Hello,
>
> The roll-out of wmf15 to non-Wikipedias appears to have introduced a
> significant performance regression, which registered as a 1-second increase
> in median page load times across the cluster. The regression abated when I
> rolled back <https://gerrit.wikimedia.org/r/#/c/188409/>.
>
> http://i.imgur.com/2sPxYNg.png
> http://i.imgur.com/NFbyOBu.png
>
> There should be no MediaWiki deployments until this bug is isolated and
> resolved.
> Tracked in <https://phabricator.wikimedia.org/T88528>.
>
> Ori
> _______________________________________________
> Engineering mailing list
> Engineering(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/engineering
----- End forwarded message -----
--
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |
Minutes and slides from last week's quarterly review meeting of the
Foundation's Collaboration team (which was formerly called the Core
features team and is working on the Flow project) have appeared here:
https://meta.wikimedia.org/wiki/WMF_Metrics_and_activities_meetings/Quarter…
On Wed, Dec 19, 2012 at 6:49 PM, Erik Moeller <erik(a)wikimedia.org> wrote:
> Hi folks,
>
> to increase accountability and create more opportunities for course
> corrections and resourcing adjustments as necessary, Sue's asked me
> and Howie Fung to set up a quarterly project evaluation process,
> starting with our highest priority initiatives. These are, according
> to Sue's narrowing focus recommendations which were approved by the
> Board [1]:
>
> - Visual Editor
> - Mobile (mobile contributions + Wikipedia Zero)
> - Editor Engagement (also known as the E2 and E3 teams)
> - Funds Dissemination Committe and expanded grant-making capacity
>
> I'm proposing the following initial schedule:
>
> January:
> - Editor Engagement Experiments
>
> February:
> - Visual Editor
> - Mobile (Contribs + Zero)
>
> March:
> - Editor Engagement Features (Echo, Flow projects)
> - Funds Dissemination Committee
>
> We’ll try doing this on the same day or adjacent to the monthly
> metrics meetings [2], since the team(s) will give a presentation on
> their recent progress, which will help set some context that would
> otherwise need to be covered in the quarterly review itself. This will
> also create open opportunities for feedback and questions.
>
> My goal is to do this in a manner where even though the quarterly
> review meetings themselves are internal, the outcomes are captured as
> meeting minutes and shared publicly, which is why I'm starting this
> discussion on a public list as well. I've created a wiki page here
> which we can use to discuss the concept further:
>
> https://meta.wikimedia.org/wiki/Metrics_and_activities_meetings/Quarterly_r…
>
> The internal review will, at minimum, include:
>
> Sue Gardner
> myself
> Howie Fung
> Team members and relevant director(s)
> Designated minute-taker
>
> So for example, for Visual Editor, the review team would be the Visual
> Editor / Parsoid teams, Sue, me, Howie, Terry, and a minute-taker.
>
> I imagine the structure of the review roughly as follows, with a
> duration of about 2 1/2 hours divided into 25-30 minute blocks:
>
> - Brief team intro and recap of team's activities through the quarter,
> compared with goals
> - Drill into goals and targets: Did we achieve what we said we would?
> - Review of challenges, blockers and successes
> - Discussion of proposed changes (e.g. resourcing, targets) and other
> action items
> - Buffer time, debriefing
>
> Once again, the primary purpose of these reviews is to create improved
> structures for internal accountability, escalation points in cases
> where serious changes are necessary, and transparency to the world.
>
> In addition to these priority initiatives, my recommendation would be
> to conduct quarterly reviews for any activity that requires more than
> a set amount of resources (people/dollars). These additional reviews
> may however be conducted in a more lightweight manner and internally
> to the departments. We’re slowly getting into that habit in
> engineering.
>
> As we pilot this process, the format of the high priority reviews can
> help inform and support reviews across the organization.
>
> Feedback and questions are appreciated.
>
> All best,
> Erik
>
> [1] https://wikimediafoundation.org/wiki/Vote:Narrowing_Focus
> [2] https://meta.wikimedia.org/wiki/Metrics_and_activities_meetings
> --
> Erik Möller
> VP of Engineering and Product Development, Wikimedia Foundation
>
> Support Free Knowledge: https://wikimediafoundation.org/wiki/Donate
>
> _______________________________________________
> Wikimedia-l mailing list
> Wikimedia-l(a)lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
--
Tilman Bayer
Senior Analyst
Wikimedia Foundation
IRC (Freenode): HaeB
One of the things we talked about at the MW dev summit recently was the
need to have a clearer roadmap of what's being worked on, what's going to
be worked on, and how that's going to fit in with third-party users as well
as Wikimedia's big sites.
I've started putting together a 'mind-map'-esque roadmap diagram, currently
in a Google Drive drawing:
https://docs.google.com/a/wikimedia.org/drawings/d/18fpigtf0mXIu9ShvJmqEQJv…
This is open for commenting but not for editing as I don't quite trust
Google's versioning tools. :) But I would love more feedback on this,
especially for third-party goals that we (WMF Engineering) may need to
support or plan around even if we don't do it ourselves.
Currently the diagram contains some major projects being worked on at WMF
or WMDE already (color coded green), plus blue boxes for things that seem
to be popular ideas already, purple for stuff I think might be awesome, and
red for some crazy stuff that I still think would be awesome. ;)
The projects are roughly divided up horizontally by area and vertically by
depth/relation.
Please note this is a preliminary document and should not be taken as WMF
plans or endorsements of which projects will get done (even when it's
complete it's going to include some "maybes" and "crazies" :)
If a major initiative seems to be left off don't be offended! Let me know
and I'll try and work it in the map. :)
-- brion
This is a call to all Wikimedia tech contributors with contacts in France.
We need your help reaching out to new developers!
We have the Wikimedia Hackathon in Lyon (23-25 May), which is a good excuse
to focus our developer outreach efforts in France already now. Google
Summer of Code and Outreachy (was FOSS Outreach Program for Women) are
around the corner. Can we coordinate an action between you, your contacts,
Wikimedia France, WMF Engineering Community team... ?
Please subscribe and participate in these tasks:
Promote GSoC, FOSS OPW, and Wikimedia Hackathon in France
https://phabricator.wikimedia.org/T88274
Engage with established technical communities at the Wikimedia Hackathon
2015
https://phabricator.wikimedia.org/T76325
PS: for similar calls focusing on Russia, China, Japan, and your preferred
country, see https://phabricator.wikimedia.org/T925
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
Minutes and slides from three recent quarterly review meetings held
last week are now available:
Language Engineering team:
https://meta.wikimedia.org/wiki/WMF_Metrics_and_activities_meetings/Quarter…
MediaWiki Core team
https://meta.wikimedia.org/wiki/WMF_Metrics_and_activities_meetings/Quarter…
Talent & Culture team (slides only:)
https://commons.wikimedia.org/wiki/File:WMF_Quarterly_Review-_2014-15_Q2_-_…
On Wed, Dec 19, 2012 at 6:49 PM, Erik Moeller <erik(a)wikimedia.org> wrote:
> Hi folks,
>
> to increase accountability and create more opportunities for course
> corrections and resourcing adjustments as necessary, Sue's asked me
> and Howie Fung to set up a quarterly project evaluation process,
> starting with our highest priority initiatives. These are, according
> to Sue's narrowing focus recommendations which were approved by the
> Board [1]:
>
> - Visual Editor
> - Mobile (mobile contributions + Wikipedia Zero)
> - Editor Engagement (also known as the E2 and E3 teams)
> - Funds Dissemination Committe and expanded grant-making capacity
>
> I'm proposing the following initial schedule:
>
> January:
> - Editor Engagement Experiments
>
> February:
> - Visual Editor
> - Mobile (Contribs + Zero)
>
> March:
> - Editor Engagement Features (Echo, Flow projects)
> - Funds Dissemination Committee
>
> We’ll try doing this on the same day or adjacent to the monthly
> metrics meetings [2], since the team(s) will give a presentation on
> their recent progress, which will help set some context that would
> otherwise need to be covered in the quarterly review itself. This will
> also create open opportunities for feedback and questions.
>
> My goal is to do this in a manner where even though the quarterly
> review meetings themselves are internal, the outcomes are captured as
> meeting minutes and shared publicly, which is why I'm starting this
> discussion on a public list as well. I've created a wiki page here
> which we can use to discuss the concept further:
>
> https://meta.wikimedia.org/wiki/Metrics_and_activities_meetings/Quarterly_r…
>
> The internal review will, at minimum, include:
>
> Sue Gardner
> myself
> Howie Fung
> Team members and relevant director(s)
> Designated minute-taker
>
> So for example, for Visual Editor, the review team would be the Visual
> Editor / Parsoid teams, Sue, me, Howie, Terry, and a minute-taker.
>
> I imagine the structure of the review roughly as follows, with a
> duration of about 2 1/2 hours divided into 25-30 minute blocks:
>
> - Brief team intro and recap of team's activities through the quarter,
> compared with goals
> - Drill into goals and targets: Did we achieve what we said we would?
> - Review of challenges, blockers and successes
> - Discussion of proposed changes (e.g. resourcing, targets) and other
> action items
> - Buffer time, debriefing
>
> Once again, the primary purpose of these reviews is to create improved
> structures for internal accountability, escalation points in cases
> where serious changes are necessary, and transparency to the world.
>
> In addition to these priority initiatives, my recommendation would be
> to conduct quarterly reviews for any activity that requires more than
> a set amount of resources (people/dollars). These additional reviews
> may however be conducted in a more lightweight manner and internally
> to the departments. We’re slowly getting into that habit in
> engineering.
>
> As we pilot this process, the format of the high priority reviews can
> help inform and support reviews across the organization.
>
> Feedback and questions are appreciated.
>
> All best,
> Erik
>
> [1] https://wikimediafoundation.org/wiki/Vote:Narrowing_Focus
> [2] https://meta.wikimedia.org/wiki/Metrics_and_activities_meetings
> --
> Erik Möller
> VP of Engineering and Product Development, Wikimedia Foundation
>
> Support Free Knowledge: https://wikimediafoundation.org/wiki/Donate
>
> _______________________________________________
> Wikimedia-l mailing list
> Wikimedia-l(a)lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
--
Tilman Bayer
Senior Analyst
Wikimedia Foundation
IRC (Freenode): HaeB
Hello,
I'm working on adding performance instrumentation to the Parsoid codebase
with statsd/node-txstatsd, and then visualizing the metrics via Grafana.
I'm at the stage where I'm looking to add the metrics' namespaces and
schema to the WMF Grafana configs.
It looks like WMF has Grafana working with Graphite/Carbon as a metrics
database and ElasticSearch as the db database, where can I find the
production Carbon config files to input the settings for my metrics?
Also, from my research WMF's carbon data retention schema is set to
'1m:1y, 10m:10y', should I default to this as my retention schema?
Note that the metrics are fired off anytime the Parsoid API is used, so
each datapoint doesn't necessarily represent a minute/second/etc of data.
Thanks,
Christy
Hi Folks,
Thank you for your feedback around the collections project*. One of the
strongest pieces of feedback was that the project name was easily confused
with the collections:extension. Yes.
As a result, the collections project is now named "project gather". This
is effective immediately. The name of the product itself is yet to be
settled-on, but the lists themselves are still referred to as collections
in mocks etc.
There is now a project page up on media wiki:
https://www.mediawiki.org/wiki/Gather
Comments welcome!
Best,
J
* for context, see thread with subject: "New feature in development:
collections"
or first email from that thread repasted here:
Hi,
For those of you I haven't yet met, I am a new product manager in SF,
working with the mobile web team (I look forward to meeting you)!
I just wanted to let you all know about a new project we are starting for
Wikipedia's mobile website. The project has been dubbed "Collections", and
our pilot will let users create and share collections of articles. Here
are some ways that this project is exploring new ways to move our mission
forward:
- *New ways to contribute: * through curation, wikipedia readers who are
not interested in traditional editing can have meaningful, creative
interactions with our content
- *Personal:* gives users a way to make content more relevant
for them "Peter's
list of most important Philosophers" is not subject to consensus
or editing
by others. For the time being, a list will only be accessible via shared
url.
- *Shareable: *this project will experiment with the ability to use
Wikipedia to share ones' perspective with others and, in doing so,
encourage new users to engage
- *[Future] Browseable:* because each list is not exhaustive, there
is a possibility of using popular lists to promote meaningful content.
It's nice to know the full list of statisticians
<https://en.wikipedia.org/wiki/List_of_statisticians> is there, but I
might want to find a subset that have been picked out by a human for one
reason or another.
Though the pilot is targeting and supporting readers, we think there are
also potential use cases for editors that we could explore in the future.
One can easily imagine lists for editors to track or share their
contributions, such as: "Articles that I want to write/expand during 2015"
or "Articles I created in 2013".
A fair amount of thought has gone into why we are launching this particular
project and how we might approach it, but we have just started exploratory
development work last week. Here is the team:
Jon Robson
Rob Moen
Joaquin Hernandez
Moiz Syed
[me]
*Ask:*
[I know that this project overlaps with several existing features in terms
of raw functionality, so if you have any relevant experience with either
the editing or technical support of lists, collections extension (books) or
watchlist and are interested in sharing your experience, please feel reach
out to me directly. We very much want to learn from previous efforts]
Also, please reach out to me or anyone else on the team if you have any
questions or concerns about the feature, team, etc.
Best,
Jon
(Apologies in advance for the cross-post)
I’d like to let you know that tickets are now available for SMWCon Spring 2015. Get them here: http://smwcons2015.eventbrite.com
SMWCon (http://semantic-mediawiki.org/wiki/SMWCon_Spring_2015), the twice-yearly conference about Semantic MediaWiki, is coming to St. Louis this Spring.
The event, organized by local volunteers, will be hosted at T-Rex May 6-8. Attendance is open to anyone wanting to learn about the intersection of the semantic web and collaborative wikis.
==What is Semantic MediaWiki?==
Semantic MediaWiki (https://semantic-mediawiki.org/wiki/Semantic_MediaWiki) (SMW) is a free, open-source extension to MediaWiki – the wiki software that powers Wikipedia – that lets you store and query data within the wiki's pages.
Semantic MediaWiki is also a full-fledged framework, in conjunction with many spinoff extensions, that can turn a wiki into a powerful and flexible knowledge management system. All data created within SMW can easily be published via the Semantic Web, allowing other systems to use this data seamlessly.
Semantic MediaWiki is used on sites like Gamepedia’s League of Legends wiki (http://lol.gamepedia.com/League_of_Legends_Wiki), the W3C’s WebPlatform.org (https://docs.webplatform.org/wiki/Main_Page) and Practical Plants (http://practicalplants.org). It’s also used by numerous organizations internally to document and share information. At past SMWCon’s we’ve had folks from NATO, NASA, MITRE, and Cirque du Soleil talking about how they use a wiki within their organizations.
==What is SMWCon?==
SMWCon is a twice annual gathering of SMW administrators, developers, and users who come together to discuss the latest in SMW developments, share what they’re working on, and learn how others are using SMW in various industries.
SMWCon Spring 2015 is a 3-day event. The first day focuses on tutorials and introductions to Semantic MediaWiki. The second day is a traditional single-track series of presentations from various folks within the community. The third day is a continuation of talks, and breakout sessions for groups to discuss project work - planning for new development, documentation, or other SMW-related efforts.
The conference is May 6-8, 2015 and will be at T-Rex, a local tech incubator and co-working space. We’ll have breakfast for all three days, lunch for two, and a social night out at a local venue.
If you’re thinking about attending, visit the conference page (http://semantic-mediawiki.org/wiki/SMWCon_Spring_2015) and add your name to the list. That’s right, just edit the page. It’s a wiki after all.
Formal registration and tickets can be found at http://smwcons2015.eventbrite.com We have Early-bird and Academic pricing available.
==Speakers Wanted==
We’re looking for folks to share their experience using wikis - from the technology and administration to the community building and philosophy behind open collaborative sharing platforms like Semantic MediaWiki. If you’d like to present, you guessed it, just edit the conference page (http://semantic-mediawiki.org/wiki/SMWCon_Spring_2015) with your proposed talk.
I hope you’ll attend this year and please help spread the word to anyone you think might be interested.
For more information or questions, contact the local chair, Chris Koerner, at Chris.Koerner(a)Mercy.Net.
This electronic mail and any attached documents are intended solely for the named addressee(s) and contain confidential information. If you are not an addressee, or responsible for delivering this email to an addressee, you have received this email in error and are notified that reading, copying, or disclosing this email is prohibited. If you received this email in error, immediately reply to the sender and delete the message completely from your computer system.
