Analytics November 2014

analytics@lists.wikimedia.org

29 participants
31 discussions

stat1002 log cleanup
by Nuria Ruiz 05 Nov '14

05 Nov '14

Hello, To comply with our privacy policy we are going to purge logs in 1002 that are older than 90 days. Please let us know whether this is an issue. We hope to have these changes done by the end of next week. A concrete example: Logs in, for example, the eventlogging archiving directory: @stat1002:/a/eventlogging/archive$ will be restricted to the last 90 days. Thanks, Nuria

6 8

Poke for the mailing list admins, whoever they are
by Oliver Keyes 04 Nov '14

04 Nov '14

Could we temporarily moderate Aileen, please? This is getting somewhat ridiculous and cluttering the archives (and my inbox) with automated dross. (Mandatory pause while I wait for Aileen's autoresponder to prove my point) -- Oliver Keyes Research Analyst Wikimedia Foundation

3 3

Google Code-In 2014: Become a mentor and add tasks!
by Andre Klapper 03 Nov '14

03 Nov '14

Hi, Google Code-In (GCI) will soon take place again - a contest for 13-17 year old students to contribute to free software projects. Wikimedia wants to take part again. Last year's GCI results were surprisingly good - see https://www.mediawiki.org/wiki/Google_Code-in_2013 We need your help: 1) Go to https://www.mediawiki.org/wiki/Google_Code-in_2014#Mentors.27_corner and read the information there. If something is unclear, ask! 2) Add yourself to the table of mentors on https://www.mediawiki.org/wiki/Google_Code-in_2014#Contacting_Wikimedia_men… - the more mentors are listed the better our chances are that Google accepts us. 3) Please take ten minutes and go through open recent tickets in https://bugzilla.wikimedia.org in your area of interest. If you see self-contained, non-controversial issues with a clear approach which you can recommend to new developers and would mentor: Add the task to https://www.mediawiki.org/wiki/Google_Code-in_2014#Proposed_tasks Until Sunday November 12th, we need at least five tasks from each of these categories (plus some less technical beginner tasks as well): * Code: Tasks related to writing or refactoring code * Documentation/Training: Tasks related to creating/editing documents and helping others learn more - no translation tasks * Outreach/research: Tasks related to community management, outreach/marketing, or studying problems and recommending solutions * Quality Assurance: Tasks related to testing and ensuring code is of high quality * User Interface: Tasks related to user experience research or user interface design and interaction Google wants every organization to have 100+ tasks available on December 1st. Last year, we had 273 tasks in the end. Note that you could also create rather generic tasks, for example fixing two interface messages from the list of dependencies of https://bugzilla.wikimedia.org/show_bug.cgi?id=38638 Helpful Bugzilla links: * Reports that were proposed for GCI last year and are still open: https://bugzilla.wikimedia.org/buglist.cgi?quicksearch=ALL%20whiteboard%3Ag… * Open Analytics tickets created in the last six months (if I got your products and components right): https://bugzilla.wikimedia.org/buglist.cgi?bug_status=UNCONFIRMED&bug_statu… * 3 existing Analytics "easy" tickets (are they still valid? Are they really self-contained, non-controversial issues with a clear approach? Could some of them be GCI tasks that you would mentor? If so, please tag them as described above!): https://bugzilla.wikimedia.org/buglist.cgi?bug_status=UNCONFIRMED&bug_statu… Could you imagine mentoring some of these tasks? Thank you for your help in reaching out to new contributors and making GCI a success again! Please ask if you have questions. Cheers, andre PS: And in a future Phabricator world, Bugzilla tickets with the 'easy' keyword will become Phabricator tasks with the 'easy' project. -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/

1 0

s1 replica on analytics-store suffering lag of >12 hours
by Christian Aistleitner 03 Nov '14

03 Nov '14

Hi, just a quick heads up that the s1 replication lag on analytics-store.eqiad.wmnet (i.e.: dbstore1002), is currently at 15 hours and increasing. I filed RT ticket 8792: https://rt.wikimedia.org/Ticket/Display.html?id=8792 If you need to query s1, you can use s1-analytics-slave as up-to-date replica instead until the other replica is fixed. Best regards, Christian -- ---- quelltextlich e.U. ---- \\ ---- Christian Aistleitner ---- Companies' registry: 360296y in Linz Christian Aistleitner Kefermarkterstrasze 6a/3 Email: christian(a)quelltextlich.at 4293 Gutau, Austria Phone: +43 7946 / 20 5 81 Fax: +43 7946 / 20 5 81 Homepage: http://quelltextlich.at/ ---------------------------------------------------------------

1 1

Re: [Analytics] [Wikimedia-l] Experimenting on Wikimedians
by Pine W 01 Nov '14

01 Nov '14

Forwarding to Research and Analytics for discussion. Pine On Oct 30, 2014 8:13 PM, "MZMcBride" <z(a)mzmcbride.com> wrote: > Hi. > > Splitting this out from the GLAMs/Chapters thread, I continue to regularly > wonder whether we need stricter guidelines and guidance in the area of > experimenting on Wikimedians. > > Erik mentioned trying to further implement A/B testing in software > development, but to me that quickly raises consent and trust issues. My > view is that Wikimedians should be treated as colleagues, not customers. > > Of course the stark reality is that A/B testing on users (typically > readers, not editors) during the annual Wikimedia Foundation fundraiser > has been a major component of the Wikimedia Foundation's growth. > > Worth repeating, from <https://meta.wikimedia.org/wiki/Experiments>: > > --- > Current practices in Web analytics reflect their commercial origins. For > better or worse, the greatest motor behind the use of Web analytics has > been the profit interests of online retailers and social networks, for > whom the user is a commodity. These profit interests have profoundly > shaped the discourse of Web analytics, setting both the tenor and the tone > of debate (consider the values implicit in "funnels," a term of art). > > A thoughtless application of Web analytics to Wikimedia wikis would import > a moral outlook that is incompatible with (and, indeed, rightfully > offensive to) its community. It also wouldn't work well, because neither > Wikimedia wikis nor their editing communities are for sale. It is > therefore crucial that technical efforts be accompanied by a process of > reflection, the goal of which should be to articulate criteria for Web > analytics that express and promote the broader ambitions of the Wikimedia > movement and the moral commitments that underlie it. > --- > > I think this about sums it up better than I ever could. > > MZMcBride > > > > _______________________________________________ > 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>

1 0

s5 replica on analytics-store suffering lag of >12 hours
by Christian Aistleitner 01 Nov '14

01 Nov '14

Hi, just a quick heads up that the replication lag on analytics-store.eqiad.wmnet (i.e.: s5-analytics-slave, dbstore1002), is currently at 17 hours and increasing. I filed RT ticket 8788: https://rt.wikimedia.org/Ticket/Display.html?id=8788 Best regards, Christian -- ---- quelltextlich e.U. ---- \\ ---- Christian Aistleitner ---- Companies' registry: 360296y in Linz Christian Aistleitner Kefermarkterstrasze 6a/3 Email: christian(a)quelltextlich.at 4293 Gutau, Austria Phone: +43 7946 / 20 5 81 Fax: +43 7946 / 20 5 81 Homepage: http://quelltextlich.at/ ---------------------------------------------------------------

1 1

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

Analytics November 2014