Wikitech-l April 2015

wikitech-l@lists.wikimedia.org

98 participants
74 discussions

Anonymous editing impact on mobile
by Jon Robson 29 Apr '15

29 Apr '15

Anonymous editing was enabled on mobile web on 30th March 2015 to all users (previous it was available in an experimental mode of the site). Now we have almost a month's worth of data I thought it would be a good time to check the impact... it's a little disappointing to be honest... but it depends what we are optimising and consider the most important. Quick summary: * All edits up 154% * Edits from logged in users down 152% * Errors up 600% * No noticeable impact on the new active editor graph [0] (editors that hit 5 edits in the month period) * First edits by logged in users down 176% (although this could arguably be said to be compensated by anonymous edits) * New account creation up by 192% Follow ups * Aaron H, it would be great if you could report back with some findings on the quality of the edits during this same period. * Can anyone provide theories why registrations jumped so much? This might be related to the change or because of something else Details on the queries I ran: In March for a 26 day period before the change: * 170,948 total edits [1] * 169,845 non-anonymous edits [6] ** by 40,658 distinct users [7] * 26,617 users completely their first ever edit [11] * 9,528 errors [8] * 219,012 accounts created on mobile [12] For a similar 26 day period in April * 263,986 total edits [2] * 136,079 non-anonymous edits [4] ** by 26,823 distinct users [5] * 15,109 users completely their first ever edit [10] * 58,394 errors [9] * 419,976 accounts created on mobile [13] [0] http://mobile-reportcard.wmflabs.org/ [1] select count(*) from MobileWebEditing_8599025 where event_action = 'success' and timestamp > 20150301000000 and timestamp < 20150327000000 [2] select count(*) from MobileWebEditing_8599025 where event_action = 'success' and timestamp > 20150401000000 and timestamp < 20150427000000 [3] https://phabricator.wikimedia.org/T97494 [4] select count(*) from MobileWebEditing_8599025 where event_action = 'success' and timestamp > 20150401000000 and timestamp < 20150427000000 and event_username is NOT NULL [5] select count(distinct event_username) from MobileWebEditing_8599025 where event_action = 'success' and timestamp > 20150401000000 and timestamp < 20150427000000 and event_username is NOT NULL [6] select count(*) from MobileWebEditing_8599025 where event_action = 'success' and timestamp > 20150301000000 and timestamp < 20150327000000 and event_username is NOT NULL [7] select count(distinct event_username) from MobileWebEditing_8599025 where event_action = 'success' and timestamp > 20150301000000 and timestamp < 20150327000000 and event_username is NOT NULL [8] select count(*) from MobileWebEditing_8599025 where event_action = 'error' and timestamp > 20150301000000 and timestamp < 20150327000000 [9] select count(*) from MobileWebEditing_8599025 where event_action = 'error' and timestamp > 20150401000000 and timestamp < 20150427000000 [10] select count(*) from MobileWebEditing_8599025 where event_action = 'success' and timestamp > 20150401000000 and timestamp < 20150427000000 and event_userEditCount = 0 [11] select count(*) from MobileWebEditing_8599025 where event_action = 'success' and timestamp > 20150301000000 and timestamp < 20150327000000 and event_userEditCount = 0 [12] select count(*) from ServerSideAccountCreation_5487345 where event_displayMobile = 1 and timestamp > 20150301000000 and timestamp < 20150327000000 [13] select count(*) from ServerSideAccountCreation_5487345 where event_displayMobile = 1 and timestamp > 20150401000000 and timestamp < 20150427000000

6 8

Bugs to fix for MediaWiki 1.25.0
by Andre Klapper 29 Apr '15

29 Apr '15

The MediaWiki 1.25.0 tarball release is planned for 2015-05-25 [1],[2]. There are currently 21 open tickets in the "MW-1.25-release" project: https://phabricator.wikimedia.org/maniphest/query/BPlQRzYIEE31/#R Seven tickets have patches awaiting review: https://phabricator.wikimedia.org/maniphest/query/tfwMAVRECGaZ/#R The other 14 tickets welcome help / input / code: https://phabricator.wikimedia.org/maniphest/query/HWHn.kQ9k7xU/#R If you are aware of open tasks in Wikimedia Phabricator that must be fixed before releasing 1.25.0, please associate the "MW-1.25-release" to these open tasks (or create a dedicated task if none exists yet). Thanks for your help! andre [1] https://www.mediawiki.org/wiki/Version_lifecycle [2] https://www.mediawiki.org/wiki/MediaWiki_1.25#Release_schedule -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/

2 2

RFC meeting this week
by Tim Starling 29 Apr '15

29 Apr '15

In the next RFC meeting, we will discuss the following RFC: * Integrate file revisions with description page history <https://phabricator.wikimedia.org/T96384> The meeting will be on the IRC channel #wikimedia-office on chat.freenode.net at the following time: * UTC: Wednesday 21:00 * US PDT: Wednesday 14:00 * Europe CEST: Wednesday 23:00 * Australia AEST: Thursday 07:00 -- Tim Starling

1 0

GSoC and Outreachy results out!
by Niharika Kohli 28 Apr '15

28 Apr '15

Hello everyone! After a long and intense selection process, Google and GNOME Foundation have finally announced the list of GSoC and Outreachy selects for the current round. I'm pleased to announce we have 9 interns for GSoC and 1 for Outreachy! Congratulations to everyone selected and to the mentors who have put in much hard work in selecting worthy candidates. Also thanks to those who put in hard work but could not be selected. We had limited projects and had to make some hard decisions. We hope you'll keep contributing to Mediawiki and try again for the next GSoC/Outreachy round. We have a general guide to being a successful intern at https://www.mediawiki.org/wiki/Outreach_programs/Life_of_a_successful_proje… It's still under development and we'll be adding more details to it as we move forward in the program. The main pages for the respective programs are at https://www.mediawiki.org/wiki/Google_Summer_of_Code_2015 and https://www.mediawiki.org/wiki/Outreachy/Round_10 The students selected are: Outreachy: 1. Dibya Singh (Phenix303) from India Project: One-stop Translation Search Mentors: Nemo_bis and Nikerabbit Google Summer of Code: 2. Frédéric Bolduc (ferdbold) from Quebec Project: GraphData extension for VE Mentors: Mooeypoo and Mvolz 3. Ankita Kumari (ankita-ks) from India Project: Unified language proofing tools integration framework Mentors: Aharoni and Eranroz 4. Jiarong Wei (VcamX) from Hangzhou, Zhejiang Project: Implement OAuth support for Pywikibot Mentors: Jayvdb and Halfak 5. Tina Johnson (tinajohnson) from India Project: Newsletter Mediawiki Extension Mentors: Quim Gil and Tony Thomas 6. Vivek Ghaisas (polybuildr) from India Project: Extension to identify and delete spam pages Mentors: Yaron Koren and Jan 7. Sumit Asthana (codezee) from India Project: Wikivoyage Pagebanner Extension Mentors: Nicolas Raoul and Jdlrobson 8. Alexander Jones (happy5214) from United States Project: Implement Flow support in Pywikibot Mentors: Jayvdb and Mattflaschen 9. Jan Lebert (sitic) from Germany Project: An enhanced cross-wiki watchlist Mentors: Yuvipanda, Legoktm 10. Sarvesh Gupta (s1991) from India Project: Allow contributors to update their own details in tech metrics Mentors: Alvaro, Daniel Let's all welcome them into the Wikimedia family! Thanks, Niharika.

5 4

Re: [Wikitech-l] [Social-media] Improving the security of our users on Wikimedia sites
by Pine W 27 Apr '15

27 Apr '15

Thanks for your work on this, Chris. Forwarding to Wikitech-l. Pine On Apr 20, 2015 4:58 PM, "Chris Steipp" <csteipp(a)wikimedia.org> wrote: > > On Apr 20, 2015 4:13 PM, "Andrew Sherman" <asherman(a)wikimedia.org> wrote: > > > > Hello Everyone, > > > > We just published "Improving the security of our users on Wikimedia > sites" to the blog. URL: > > > > https://blog.wikimedia.org/2015/04/20/improving-security-for-our-users/ > > > > Thanks to Chris for writing and helping us edit this post. > > > > Below are some proposed social media messages. Tweak as needed. > > > > Twitter > > > > We teamed up with @iSECPartners and @OpenTechFund to assess the security > of our sites. Check out the report here [link] > > > > FB/G+ > > > > We teamed up with iSEC Partners to assess the security of our sites and > protect the privacy of our users. Their engineers developed attacks against > the current version of MediaWiki to identify security flaws, in a new > report sponsored by the Open Technology Fund. [link] > > Maybe just "MediaWiki" instead of "the current version of MediaWiki", > since we did a release to specifically fix issues that they found. Might > confuse some people as is. > > > > > Thanks, > > -- > > Andrew Sherman > > Digital Communications | Wikimedia Foundation > > > > E: asherman(a)wikimedia.org > > WMF: ASherman (WMF) > > _______________________________________________ > Social-media mailing list > Social-media(a)lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/social-media > >

5 6

Efficiently find the last content edit of an article?
by Daniel Barrett 27 Apr '15

27 Apr '15

What is the best way (in code) to locate the most recent revision of article in which the text actually changed? That is, the revision was not a "move" or other non-editing operation? I figure the logic would be something like: $r = GetTheMostRecentRevision(); IF $r NOT a "Move" THEN return $r ELSE walk the list of revisions until the SHA1 value changes but I don't know how to determine that a revision is a "Move." Thanks for any tips! DanB

2 1

Designing a MediaWiki Skin
by Nasir Khan 27 Apr '15

27 Apr '15

Hi, I was trying to develop a MediaWiki skin based on Bootstrap3. I am facing several type of issues at the time of doing this. MediaWiki is forcing me to use the default vector styles and for may of the pages it is "very hard" to use own CSS classes, for example Special:Allpages[1]. I am lucky that my skin/bootstrap default is similar with the MediaWiki UI and i enabled it in everywhere. But even this could not cover the page " Special:Allpages ". I found it very complex to develop a new skin for MediaWiki and it forces everyway to use the default vector skin. About a year ago i headed a project on "Separating skins from core MediaWiki", could anyone please let me know the progress and current status of that project. [1] - http://en.banglapedia.org/index.php?title=Special:AllPages -- *Nasir Khan Saikat* www.nasirkhn.com

5 7

Wikimedia Foundation quarterly reviews
by Tilman Bayer 26 Apr '15

26 Apr '15

Hi all, the quarterly reviews for the past quarter (January-March 2015) took place last week. Minutes and slides are now available for the following meetings: Community Engagement, Advancement (Fundraising and Fundraising Tech): https://meta.wikimedia.org/wiki/WMF_Metrics_and_activities_meetings/Quarter… Mobile Web, Mobile Apps, Wikipedia Zero: https://meta.wikimedia.org/wiki/WMF_Metrics_and_activities_meetings/Quarter… Parsoid, Services, MediaWiki Core, Tech Ops, Release Engineering, Multimedia, Labs, Engineering Community: https://meta.wikimedia.org/wiki/WMF_Metrics_and_activities_meetings/Quarter… Editing (covering VisualEditor), Collaboration (covering Flow), Language Engineering: https://meta.wikimedia.org/wiki/WMF_Metrics_and_activities_meetings/Quarter… As mentioned in February [1], the quarterly review process has been extended to basically all groups in the Foundation since Lila took the helm last year, and it was further refined this quarter, reducing the number of meetings to six overall, each combining several areas. Minutes and slides from the remaining two meetings should come out soon, too. (And naturally, all the engineering team names above refer to the structure before the reorganization that has just been announced.) [1] https://lists.wikimedia.org/pipermail/wikimedia-l/2015-February/076835.html 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

1 1

Serious unfixed wikidata bug
by John 26 Apr '15

26 Apr '15

T43345 <https://phabricator.wikimedia.org/T43345>is classified as a high priority, and hasn't been fixed for three years. Getting a column added to indicate that a language link is stored in a foreign repo shouldn't be this hard. I can think of quite a few cases where this data could be leveraged in one way or another. Wikidata is extremely widely used, and we still dont have this basic feature implemented, who needs pressured to get progress made on this? this should be a fairly straight up and trivial feature to get going.

2 2

[Hackathon] Reminder : Registration
by Alex Cella 24 Apr '15

24 Apr '15

Hey all, This email to remind you to register if you want to attend the European Hackathon. We already have many people registered and we'll soon be full. Registration ends on the 8th of March. If you want to join this great week-end, you can register here: https://dons.wikimedia.fr/civicrm/event/register?reset=1&id=8 You can't apply for a Scholarship anymore! A page is dedicated to give you more information: http://www.mediawiki.org/wiki/Wikimedia_Hackathon_2015 The Phabricator listing considered tasks is : https://phabricator.wikimedia.org/tag/wikimedia-hackathon-2015/ In any case, if you have some more questions, I'll be glad to help you! :) Best, *Alexandre Cella* ASSISTANT LEVÉE DE FOND ET MÉCÉNAT FUNDRAISING AND SPONSORSHIP ASSISTANT *WIKIMEDIA FRANCE* +33 6 18 16 16 19 www.wikimedia.fr 40 rue de Cléry, 75002 Paris *Vos dons réguliers aident à faire fonctionner Wikipédia ! Soutenez Wikimédia France aujourd'hui* : https://dons.wikimedia.fr

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Wikitech-l April 2015