This exercise might be interesting for technical minds with good memory.
---------- Forwarded message ----------
From: Heather Walls <hwalls(a)wikimedia.org>
Date: Fri, Nov 13, 2015 at 1:59 AM
Subject: [Wikimedia-l] 15 years! Help us add what's missing
To: Wikimedia Mailing List <wikimedia-l(a)lists.wikimedia.org>
Dear everyone,
Help us collect the 15 best things about the Wikimedia movement (and
Wikipedia) from the last 15 years!
Community members all over the world and the Communications team, have been
preparing to celebrate the start of Wikipedia and the Wikimedia movement.
On January 15, 2016, it will have been 15 years of collaborating,
collecting, verifying, and making knowledge free for the whole world.
As part of our annual report, we plan to once again share stories -- this
time celebrating the joy of knowledge and discovery. We want to include
some of the most amazing, strange, cool, and unbelievable things about the
last 15 years.
There is a page started on Meta.[1] We know they balance to enWP right now,
so we are especially appreciative of additions about the rest of the
movement. Please add things we've missed, make corrections to anything
that's not correct, and commenting on your favorite.
Thanks so much for taking the time to improve this!
The WMF Communications team
1. https://meta.wikimedia.org/wiki/Wikipedia_15/15_years
--
*Heather Walls *Wikimedia Foundation
annual.wikimedia.org <https://annual.wikimedia.org/2014/>
_______________________________________________
Wikimedia-l mailing list, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l(a)lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
<mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe>
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
[x-posted announcement]
Hello,
The next office hour of the Wikimedia Language Engineering team is
scheduled for next Wednesday, November 25th 2015 at 13:00 UTC. Similar to
our recent office hours, this is also going to be an online discussion over
Hangout/Youtube with a simultaneous IRC conversation. Due to the limitation
of Google Hangouts, only a limited number of slots are available. Hence, do
please let us know (on the event page) if you would like to participate on
the Hangout. The IRC channel #wikimedia-office and the Q&A channel for the
youtube broadcast will be open for interactions during the session.
Our last online round-table session was held in September 2015. You can
watch the recording here: https://www.youtube.com/watch?v=nW5l7fNeMQg
Please read below for the event details and do let us know if you have any
questions.
Thank you
Runa
== Details ==
# Event: Wikimedia Language Engineering office hour session
# When: November 25th, 2015 (Wednesday) at 13:00 UTC (check local time
http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151125T1300)
# Where: https://plus.google.com/u/0/events/cprj7uhtiercilrilp2gfpca8dg and
on IRC #wikimedia-office (Freenode)
# Agenda: Content Translation updates and Q & A
--
Language Engineering Manager
Outreach and QA Coordinator
Wikimedia Foundation
Does this new Pageview API have any source code or repo one could use
outside of Wikimedia? It looks really interesting.
Yours,
Chris Koerner
clkoerner.com
Dear Data Enthusiasts,
In collaboration with the Services team, the analytics team wishes to
announce a public Pageview API
<https://wikimedia.org/api/rest_v1/?doc#!/Pageviews_data/get_metrics_pagevie…>.
For an example of what kind of UIs someone could build with it, check out
this excellent demo <http://analytics.wmflabs.org/demo/pageview-api> (code)
<https://gist.github.com/marcelrf/49738d14116fd547fe6d#file-article-comparis…>
.
The API can tell you how many times a wiki article or project is viewed
over a certain period. You can break that down by views from web crawlers
or humans, and by desktop, mobile site, or mobile app. And you can find
the 1000 most viewed articles
<https://wikimedia.org/api/rest_v1/metrics/pageviews/top/es.wikipedia/all-ac…>
on any project, on any given day or month that we have data for. We
currently have data back through October and we will be able to go back to
May 2015 when the loading jobs are all done. For more information, take a
look at the user docs
<https://wikitech.wikimedia.org/wiki/Analytics/AQS/Pageview_API>.
After many requests from the community, we were really happy to finally
make this our top priority and get it done. Huge thanks to Gabriel, Marko,
Petr, and Eric from Services, Alexandros and all of Ops really, Henrik for
maintaining stats.grok, and, of course, the many community members who have
been so patient with us all this time.
The Research team’s Article Recommender tool <http://recommend.wmflabs.org/>
already uses the API to rank pages and determine relative importance. Wiki
Education Foundation’s dashboard <https://dashboard.wikiedu.org/> is going
to be using it to count how many times an article has been viewed since a
student edited it. And there are other grand plans for this data like
“article finder”, which will find low-rated articles with a lot of
pageviews; this can be used by editors looking for high-impact work. Join
the fun, we’re happy to help get you started and listen to your ideas.
Also, if you find bugs or want to suggest improvements, please create a
task in Phabricator and tag it with #Analytics-Backlog
<https://phabricator.wikimedia.org/tag/analytics-backlog/>.
So what’s next? We can think of too many directions to go into, for
pageview data and Wikimedia project data, in general. We need to work with
you to make a great plan for the next few quarters. Please chime in here
<https://phabricator.wikimedia.org/T112956> with your needs.
Team Analytics
>
> Finally! I waited so many years for a formal tool like that. Thank you!
>
Itzik, I remember your requests for this type of data from a long long time
ago, when I was just starting at the foundation!! You and the many others
with similar requests are the people we were thanking in the announcement :)
And demo on wmflabs is great, but it will be great to add option to export
> the data to CSV file. Also, the data are only from the begging of October,
> any chance we can load past data as well?
>
So, I agree with what Madhu said that you could file a Phabricator ticket
for this. But for now, we're not looking to build a UI for it that is
production ready. The demo was meant just to show that it's very simple to
do so. It took one of our engineers only a few days and under 300 lines of
code to get this done. We'd like to be patient and see if the community at
large has an interest in running something like stats.grok.se now that
heavy lifting of data is no longer required, and performance is guaranteed
by us within reasonable expectations.
In the next RFC meeting, we will discuss the following RFC:
* API-driven web front-end
<https://phabricator.wikimedia.org/T111588>
The meeting will be on the IRC channel #wikimedia-office on
chat.freenode.net at the following time:
* UTC: Wednesday 22:00
* US PST: Wednesday 14:00
* Europe CET: Wednesday 23:00
* Australia AEDT: Thursday 09:00
-- Tim Starling
Nick Wilson discovered a security issue that affects Flow when used with
caching proxies such as Varnish:
https://phabricator.wikimedia.org/T116095 (this task will be opened soon).
In such a setup, topics in cache would remain accessible after the board
was deleted.
We have deployed the fix to the cluster and merged it to the Flow
repository.
Let us know if you are using REL1_24 or REL1_25 of Flow and this issue
affects you.
Thanks,
Matt Flaschen
Hello all,
Glad to inform that the results of Outreachy round 11 are out, and one of
our candidate - Josephine Lim made it to the program for her proposal
on Easier categorization of pictures in Upload to Commons Android app -
https://phabricator.wikimedia.org/T115101. Congratulations to the candidate
and the mentors involved. The select should follow up with the mentors to
finish the 'Community bonding period' as per [1].
We had around 13 strong proposals submitted in the Outreachy application
system for 9 projects -
https://phabricator.wikimedia.org/tag/outreachy-round-11/ - but the
Outreachy organization team made their rule of "Little or No-Commitment
during Dec-March", and our applicants had to back off, considering most of
them where University students.
The applicants who couldn't make it this time are welcome to accomplish the
project as per the proposal considering they have mentors ready ( if there
is agreement from both sides ). This should possibly make them really
strong candidates for the next round of GSoC/Outreachy, which is the bright
side.
Special thanks to all the mentors, who actively ranked the applicants
before the deadline, and making it smooth for the administration team. The
total listing of selections from all Organizations can be found over here -
https://wiki.gnome.org/Outreachy/2015/DecemberMarch
[1]
https://www.mediawiki.org/wiki/Outreach_programs/Life_of_a_successful_proje…
Thanks,
Tony Thomas <http://blog.tttwrites.in/>
ThinkFOSS <http://www.thinkfoss.com>
*"where there is a wifi, there is a way"*