Wikitech-l July 2015

wikitech-l@lists.wikimedia.org

97 participants
78 discussions

Please join the "Making the Wiki Ed dashboard work for outreach projects" hackathon session at Wikimania
by Erica Litrenta 14 Jul '15

14 Jul '15

TL;DR, Whether you are an amateur or an expert coder, or if you are a current or interested user of the WikiEduDashboard or of the Education Extension,* please join us at a hackathon session at Wikimania on Wednesday, 15 July in Workplace 2 - Don Genaro at 1pm. [0]* A long time ago in a galaxy far, far away, the Wikimedia Foundation developed Extension:EducationProgram. It did what we needed it to do at the time, which was to provide a tool that helps organize classes that want to edit Wikipedia articles for course credit. Since its release, the extension has been deployed to 18 Wikimedia projects: it's on 4 sister projects in 16 languages. Recently, the Wiki Education Foundation [1], led by project manager Sage Ross - User:Sage (Wiki Ed), User:Ragesoss - developed a Ruby on Rails app called the WikiEduDashboard [2], which they will use beginning this fall instead of the EducationProgram extension, for the university courses that they support on English Wikipedia. We believe it is possible to use their freely-licensed code to create a clone of this dashboard that can be used for non-Wiki Ed education program courses and other group editing activities on English Wikipedia and, ultimately, on other Wikimedia projects and in other languages. We are asking for community support for this project since this is outside the scope of WMF's engineering team for this year. We see the need for a global dashboard tool and would love to have your help building it! We're planning some exciting improvements to the Wiki Education Dashboard, see Phabricator [3] for the full list. * Full i18n, including right-to-left support. * Generalize the UI to work for any wiki project and not only university courses. * Integration with the Gather extension, to render lists of articles being written and reviewed. * Integration with Campaigns, to track group membership and statistics. * Improvements to the API to simplify some actions taken from the Dashboard. * Potentially using Wikidata as the backend for storing information about courses and editing projects. We look forward to working together to build this powerful tool which will support more education and outreach programs in the movement! Elitre (WMF), on behalf of the WMF's Education team, + Andrew Green, Adam Wight, Sage Ross. [0] https://phabricator.wikimedia.org/T103623 [1] http://wikiedu.org/ [2] https://github.com/WikiEducationFoundation/WikiEduDashboard [3] https://phabricator.wikimedia.org/tag/education-program-dashboard/

3 3

Plans for mobile editing, VisualEditor [and mobile contributions]
by Florian Schmidt 14 Jul '15

14 Jul '15

Hello all together, some time ago, WMF started to re-organize into a new structure to focus on specific topics. Now, I think, the main tasks are done, so that I want to bring a (for me, and I think and hope for some others, too) very important topic back to the ToDo list: mobile editing. In the past, the mobile web team (in which I mostly contributed, too) maintained the mobile wikitext editor in a very basic state, and the VisualEditor team maintained the VisualEditor for tablet users. Now, most people of the former mobile web team moved to the new vertical “Readership”, so I’m pretty sure, that the responsibility for all editing stuff on mobile isn’t in this team anymore (reading ≠ editing), so I think, that the new editing vertical maintains all the editing stuff, including mobile editing. Now I have some questions around this topic: 1. I’m missing MobileFrontend in the list of maintained extensions on https://www.mediawiki.org/wiki/Editing ? Are there plans to move all editing features away from MobileFrontend, or is the editing code in MobileFrontend unmaintained now? How volunteers are able to contribute to the right place? What is the bigger image for editing code in mobile? 2. Is there a roadmap for the mobile VisualEditor? At the moment it’s only available for tablet users (which makes contributing on smartphones a bit hard, there is only a clean wikitext editor, see one of my next points). I know task T93325[1], is that meant to enable mobile VE on smartphones, too? What is the roadmap for it? 3. Are you planning to support a wikitext editor on mobile, too (Like a light WikiEditor)? At the moment, the wikitext editor in mobile is very very basic (basically without any feature). I submitted a change[2] to enable some rally basic features to it, which, technically seems to be merge able, but no-one of editing reviews it, neither it’s possible for a volunteer (me :)) to find out, if such a feature matches the global vision for mobile editing. 4. And the last point (any maybe the most important one): Who is the person (or the group of person) I can contact for mobile related editing things? In the time of the former mobile web team I have known the persons I can ping on irc, e-mail or via mailing lists, now I’m a bit confused, who is responsible for mobile editing, it’s like a gray veil :) It would be great to have these points answered :) [1] https://phabricator.wikimedia.org/T93325 [2] https://gerrit.wikimedia.org/r/#/c/194945/ Have a nice weekend! Best, Florian

2 3

Please join the 2nd edition of the VisualEditor Translathon
by Erica Litrenta 14 Jul '15

14 Jul '15

(Apologies for crossposting.) Hello! We're pleased to announce the 2nd edition of the *VisualEditor Translathon*. It is a translation rally, focused on interface messages and help pages related to VisualEditor [0]. In order to participate, you need to *sign up on the Translathon page* [1]. The top 3 contributors will each win a Wikipedia t-shirt of their choice from the Wikipedia store [2]. Translations made between *July 15th and July 19th* (CDT time zone [3]) qualify [4]. If you are at Wikimania Mexico this year [5], you are also welcome to join a related sprint during the hackathon in *Workplace 1 - Don Américo, Thursday 16 July at 4pm (CDT)* at the conference venue, so you can meet other fellow translators and get support if you need some [6]. Interface messages have the priority. You will need to create an account at translatewiki.net in order to work on them, if you don't have one. *It is recommended to create the account ASAP*, so that it can be confirmed in time. You can also help translate documentation pages about VisualEditor on mediawiki.org. You can use your Wikipedia account to work there. You will find instructions, links and other details on the Translathon page [1]. Thanks for your attention, and happy translating! Elitre (WMF) and Trizek (WMF) [0] https://www.mediawiki.org/wiki/VisualEditor [1] https://translatewiki.net/wiki/Project:VisualEditor/2015_Translathon [2] https://store.wikimedia.org/ . You can choose between any short-sleeve shirt, or other items for the same value. [3] http://www.timeanddate.com/time/zones/cdt [4] This means both new translations, and updates for messages in the "Outdated" tab of the translation interface. [5] https://wikimania2015.wikimedia.org/wiki/Wikimania [6] https://phabricator.wikimedia.org/T91108

1 0

statistics about frequent section titles
by Amir E. Aharoni 13 Jul '15

13 Jul '15

Hi, Did anybody ever try to collect statistics about frequent section titles in Wikimedia projects? For Wikipedia, for example, titles such as "Biography", "Early life", "Bibliography", "External links", "References", "History", etc., appear in a lot of articles, and their counterparts appear in a lot of languages. There are probably similar things in Wikivoyage, Wiktionary and possibly other projects. Did anybody ever try to collect statistics of the most frequent section titles in each language and project? -- Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי http://aharoni.wordpress.com ‪“We're living in pieces, I want to live in peace.” – T. Moore‬

2 1

VE stopped working on 1.25 after import & update of wiki db (1.23->1.25)
by Daren Welsh 12 Jul '15

12 Jul '15

We have an existing wiki using MW 1.23. We are working on a build script to generate a wiki using MW 1.25. Eventually the script will also automate the database import and update, but for now I'm still learning the steps. I built a VM with 1.25 and VE using some scripts that we are building[1]. VE seemed to be happily working. Then I imported our 1.23 SQL database and files (/images). I ran update.php and runJobs.php. Now it seems VE hangs at about the 75% point of the blue "progress bar" after clicking "Edit". Note that I am still able to edit source. I know this is not enough to get a full answer, but I'm hoping you can help me find some more resources to try. For example, are there any significant changes between the REL1_25 branch of Parsoid and HEAD? I see the branch on Gerrit, but I couldn't see that branch in git for a checkout. Thanks, Daren [1] https://github.com/enterprisemediawiki/Meza1 -- __________________ http://enterprisemediawiki.org http://mixcloud.com/darenwelsh http://www.beatportfolio.com

4 5

[RfC] Content model storage
by Legoktm 12 Jul '15

12 Jul '15

Hi, I've written up an RfC to change the way we currently store a page's and revisions' content model and format: <https://www.mediawiki.org/wiki/Requests_for_comment/Content_model_storage> in the database. Please leave comments on the talk page. Thanks! -- Legoktm

2 1

+2 in mediawiki/* for Liangent
by Legoktm 11 Jul '15

11 Jul '15

Hi, Per [1], I gave Liangent +2 powers in mediawiki/* repos. Congratulations! [1] https://phabricator.wikimedia.org/T98386 -- Legoktm

5 4

Flow, LiquidThreads, and XML dumps
by wp mirror 11 Jul '15

11 Jul '15

Dear Sir of Madam, I would like to see what impact Flow will have on dump files. I see that LiquidThreads still appear in the XML dumps of enwikinews (as of 20150602). Will the tables containing Flow records be dumped in SQL or XML format? Are there now any SQL or XML dumps that contain Flow records? If not, can you forecast when Flow will appear in the dumps? SIncerely Yours, Kent

2 1

Re: [Wikitech-l] API BREAKING CHANGE: Default continuation mode for action=query will change at the end of this month
by Mr. Stradivarius 10 Jul '15

10 Jul '15

> On *Wed, Jul 8, 2015 at 6:17 AM, Marco F <* *maic23 at live.de <wikitech-l%40lists.wikimedia.org?Subject=Re%3A%20%5BWikitech-l%5D%20API%20BREAKING%20CHANGE%3A%20Default%20continuation%20mode%20for%0A%20action%3Dquery%20will%20change%20at%20the%20end%20of%20this%20month&In-Reply-To=%3CDUB127-W101D748884FAB0EF70713FC4910%40phx.gbl%3E>> wrote:> *> You can't expect the average user to go to Phabricator or post on this mailing > list. If you are lucky, they complain on the respective talk pages like [1] or > some other place. > > I think, there is be quite a substantial amount of programs around which still > use the old interface and are broken now. Waiting for someone to notice and > fix... > > Marco > > [1] https://commons.wikimedia.org/w/index.php?title=MediaWiki_talk%3AGadget-Cat… I'm sure there are still some out there, but probably not as many as you think. I know that there aren't any gadgets or user scripts on enwiki or mediawikiwiki that use the old syntax, because I cleaned them up personally. I also got myself global interface editor rights and fixed all the gadgets in the MediaWiki namespace on every Wikimedia wiki. That still leaves bots, other external tools, and user scripts that aren't gadgets, so it's hard to say what's still left to fix. But most of the important gadgets are working, at least. Another good idea might be to look through the public repositories for external tools and bot frameworks to check whether they have implemented the change. I think we can safely assume that the big ones like Huggle, Twinkle and AWB have been fixed, due to the lack of noise at enwiki's technical village pump. But there may well be smaller external tools out there that still need fixing. Also, if anyone is interested, I have compiled a list of scripts on all WMF wikis that may need updating.[1] It has 129 pages in at the moment, although some are false positives, and some are personal scripts for inactive users that we don't need to bother with. Strad [1] https://en.wikipedia.org/wiki/User:Mr._Stradivarius/Query-continue

4 4

Interwiki navigation via search box appears to be broken
by Pine W 09 Jul '15

09 Jul '15

For example, searching for "Commons:main" on ENWP no longer takes the user to the Commons main page. Fix please. (: Thanks, Pine

1 1

Data and Developer Hub protoype
by S Page 09 Jul '15

09 Jul '15

http://devhub.wmflabs.org is a prototype of the "Data and developer hub", a portal and set of articles and links whose goal is to encourage third-party developers to use Wikimedia data and APIs. Check it out, your feedback is welcome! You can comment on the talk page of the project page https://www.mediawiki.org/wiki/dev.wikimedia.org , or file Phabricator tickets in the project dev.wikimedia.org [1]. Since December 2013 Moiz Syed and others discussed creating "a thing" to expose our APIs and data to developers. When S Page moved to WMF tech writer, he wrote some articles for this on mediawiki.org and with Quim Gil developed a landing page from the wireframe designs [2]. The prototype is using the Blueprint skin and running on a labs instance, but the articles are all regular wiki pages on mediawiki.org that we regularly import to http://devhub.wmflabs.org Thanks to everyone who participated in the gestation of this idea! -- S Page and Quim Gil == FAQ == Q: How can I feature my awesome API or data set? A: Create a task in the #dev.wikimedia.org and #documentation projects [3] with "Article" in the title. You can draft an article yourself, following the guidelines [4]. Q: Yet another site? Arghh! A: Agreed, T101441 "Integrate new Developer hub with mediawiki.org" [5]. It's a separate site for now in order to present a different appearance. Q: But why a different appearance? Why a separate skin? Our competition for developer mindshare is sites like https://developers.google.com/ . We believe looking like a 2000s wiki page is a *deterrent* to using Wikimedia APIs and data. We hope that many third-party developers join our communities and eventually contribute to MediaWiki, but "How to contribute to MediaWiki" [6] is not the focus, providing free open knowledge is. Q: Why the Blueprint skin? A: The Design team (now Reading Design) developed it for the OOUI Living Style Guide [7] and it has some nice features: a fixed header, and a sidebar that gets out of the way and combines page navigation and the TOC of the current page. Q: So why not use the Blueprint skin on mediawiki.org? A: Agreed, T93613 "Deploy Blueprint on mediawiki.org as optional and experimental skin" is a blocker for T101441. We appreciate help with it and its blockers. Q: I hate the appearance. A: That's not a question :) You can forget the prototype exists and view the same content at https://www.mediawiki.org/wiki/API:Data_and_developer_hub Q: What is "dev.wikimedia.org"? A: http://dev.wikimedia.org will be the well-known shortcut to the landing page. And dev.wikimedia.org is the project name for this "Data and developer hub". Q: I thought dev.wikimedia.org was going to integrate source documentation/replace doc.wikimedia.org/enumerate all Wikimedia software projects/cure cancer, what happened? A: One step at a time. For now, its goal is, to repeat, "to encourage third-party developers to use Wikimedia data and APIs". Q: Why are the pages in the API: namespace? A: That's temporary, they will probably end up in a dev: namespace on mediawiki.org that uses the Blueprint skin by default (T369). Q: Where are the talk pages? A: It's a bug that the sidebar doesn't have a "Discussion" link (T103785). The talk pages on the prototype all redirect to the talk pages for the original pages on mediawiki.org, and Flow is enabled on them. [1] https://phabricator.wikimedia.org/maniphest/task/create/?projects=dev.wikim… [2] https://www.mediawiki.org/wiki/Dev.wikimedia.org#Structure [3] https://phabricator.wikimedia.org/maniphest/task/create/?projects=dev.wikim… [4] https://www.mediawiki.org/wiki/dev.wikimedia.org/Contributing [5] https://phabricator.wikimedia.org/T93613 and its blockers [6] https://www.mediawiki.org/wiki/How_to_contribute (a fine general entry point) [7] http://livingstyleguide.wmflabs.org/ -- =S Page WMF Tech writer

8 16

Plan for a Developer Relations team
by Quim Gil 09 Jul '15

09 Jul '15

Hi, the Engineering Community team is working on a plan to evolve onto a Developer Relations team. This is not just a change of name. See *https://www.mediawiki.org/wiki/Engineering_Community_Team/Developer_Relations_team <https://www.mediawiki.org/wiki/Engineering_Community_Team/Developer_Relatio…>* Your feedback is welcome, in the wiki page or here. Related task: https://phabricator.wikimedia.org/T97283 -- Quim Gil Engineering Community Manager @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil

4 6

2015-07-08 Scrum of Scrums notes
by Grace Gellerman 08 Jul '15

08 Jul '15

https://www.mediawiki.org/wiki/Scrum_of_scrums/2015-07-08

2 1

API BREAKING CHANGE: Default continuation mode for action=query will change at the end of this month
by Brad Jorsch (Anomie) 08 Jul '15

08 Jul '15

As has been announced several times (most recently at https://lists.wikimedia.org/pipermail/wikitech-l/2015-April/081559.html), the default continuation mode for action=query requests to api.php will be changing to be easier for new coders to use correctly. *The date is now set:* we intend to merge the change to ride the deployment train at the end of June. That should be 1.26wmf12, to be deployed to test wikis on June 30, non-Wikipedias on July 1, and Wikipedias on July 2. If your bot or script is receiving the warning about this upcoming change (as seen here <https://www.mediawiki.org/w/api.php?action=query&list=allpages>, for example), it's time to fix your code! - The simple solution is to simply include the "rawcontinue" parameter with your request to continue receiving the raw continuation data ( example <https://www.mediawiki.org/w/api.php?action=query&list=allpages&rawcontinue=1>). No other code changes should be necessary. - Or you could update your code to use the simplified continuation documented at https://www.mediawiki.org/wiki/API:Query#Continuing_queries (example <https://www.mediawiki.org/w/api.php?action=query&list=allpages&continue=>), which is much easier for clients to implement correctly. Either of the above solutions may be tested immediately, you'll know it works because you stop seeing the warning. I've compiled a list of bots that have hit the deprecation warning more than 10000 times over the course of the week May 23–29. If you are responsible for any of these bots, please fix them. If you know who is, please make sure they've seen this notification. Thanks. AAlertBot AboHeidiBot AbshirBot Acebot Ameenbot ArnauBot Beau.bot Begemot-Bot BeneBot* BeriBot BOT-Superzerocool CalakBot CamelBot CandalBot CategorizationBot CatWatchBot ClueBot_III ClueBot_NG CobainBot CorenSearchBot Cyberbot_I Cyberbot_II DanmicholoBot DeltaQuadBot Dexbot Dibot EdinBot ElphiBot ErfgoedBot Faebot Fatemibot FawikiPatroller HAL HasteurBot HerculeBot Hexabot HRoestBot IluvatarBot Invadibot Irclogbot Irfan-bot Jimmy-abot JYBot Krdbot Legobot Lowercase_sigmabot_III MahdiBot MalarzBOT MastiBot Merge_bot NaggoBot NasirkhanBot NirvanaBot Obaid-bot PatruBOT PBot Phe-bot Rezabot RMCD_bot Shuaib-bot SineBot SteinsplitterBot SvickBOT TaxonBot Theo's_Little_Bot W2Bot WLE-SpainBot Xqbot YaCBot ZedlikBot ZkBot -- Brad Jorsch (Anomie) Software Engineer Wikimedia Foundation

12 23

Article about encrypted communications in NYTimes
by Pine W 07 Jul '15

07 Jul '15

FYI: http://mobile.nytimes.com/2015/07/08/technology/code-specialists-oppose-us-… Pine

1 0

Automatic Transfer SVN Extension to GIT
by planetenxin 07 Jul '15

07 Jul '15

Hi list, is there a procedure/best practice to automatically transfer old SVN style extensions to GIT? Is this something the maintainer of an extension needs to do? An example would be: https://www.mediawiki.org/wiki/Extension:DateDiff /planetenxin

4 6

Jenkins upgrade July 8th 8:00am UTC
by Antoine Musso 07 Jul '15

07 Jul '15

Hello, Zeljko and I will upgrade Jenkins on Wednesday July 8th at 8:00am UTC (10:00am CET). There will be roughly half an hour downtime. Zuul will keep queueing the changes and trigger the jobs whenever Jenkins comes back up. In case of crazy side effect, we will revert back to the current version. Expected downtime is half an hour but I scheduled a two hours maintenance window. https://phabricator.wikimedia.org/T101884 https://wikitech.wikimedia.org/w/index.php?title=Deployments&diff=169423&ol… -- Antoine "hashar" Musso

1 0

Video for Safari, IE, and Edge: ogv.js 0.9 and TMH patches (please review)
by Brion Vibber 07 Jul '15

07 Jul '15

I've done some more cleanup and fixes on ogv.js JavaScript Ogg media player, with an 0.9 pre-release build and updated patches for TimedMediaHandler. Would love some code review and testing! *Upstream library release:* https://github.com/brion/ogv.js/releases/tag/0.9 *Live demo site:* https://ogvjs-testing.wmflabs.org/ *TMH patches:* Update to bundled ogv.js libs (went ahead and merged): https://gerrit.wikimedia.org/r/#/c/223261/1 Finish the desktop TMH integration of ogv.js player (need testing and review!): https://gerrit.wikimedia.org/r/#/c/165478/36 Work in progress mobile integration for TMH (needs more upstream updates for controls): https://gerrit.wikimedia.org/r/#/c/217485/ -- brion

1 0

Search engine indexing of userspace - has something changed?
by Dan Garry 07 Jul '15

07 Jul '15

Hello! In this thread <https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(proposals)#Userpage_d…>, there was a discussion about indexing of user space by search engines. In a nutshell, user space pages are not subject to content policies so that users can write drafts freely, and having those pages indexed by search engines like Google is viewed as problematic since those pages can seem fairly official. I seem to recall that it was not the default in the past that user pages were indexed by search engines. I'm trying to figure out if there's some other cause for this that's happened recently, because I'd prefer to avoid piling hacks on and not address the root issue. Does anyone know of anything that's changed recently that might've changed the way that search engines index user space? Thanks, Dan -- Dan Garry Product Manager, Discovery Wikimedia Foundation

4 3

Barry the browser bot
by Jon Robson 07 Jul '15

07 Jul '15

Some of you may have noticed a bot [1] providing reviews for the Mobilefrontend and Gather extensions. This is a grass routes experiment [2] to see if we can reduce regressions by running browser tests against every single commit. It's very crude, and we're going to have to maintain it but we see this as a crude stop gap solution until we get gerrit-bot taking care of this for us. Obviously we want to do this for all extensions but we wanted to get something good enough that is not scaleable to start exploring this. So far it has caught various bugs for us and our browser test builds are starting to finally becoming consistently green, a few beta labs flakes aside [3]. Running tests on beta labs is still useful but now we can use it to identify tests caused by other extensions. We were finding too often our tests were failing due to us neglecting them. In case others are interested in how this is working and want to set one up themselves I've documented this here: https://www.mediawiki.org/wiki/Reading/Setting_up_a_browser_test_bot Please let me now if you have any questions and feel free to edit and improve this page. If you want to jump into the code that's doing this and know Python check out: https://github.com/jdlrobson/Barry-the-Browser-Test-Bot (Patches welcomed and apologies in advance for the code) [1] https://gerrit.wikimedia.org/r/#/q/reviewer:jdlrobson%252Bbarry%2540gmail.c… [2] https://phabricator.wikimedia.org/T100293 [3] https://integration.wikimedia.org/ci/view/Mobile/job/browsertests-MobileFro…

2 1

The end of the Roadmap Phabricator project
by Greg Grossmeier 06 Jul '15

06 Jul '15

Hello all, First, some history and context: The #roadmap project[0] in our Phabricator instance was set up by Erik M as a trial way of tracking upcoming releases, deployments, and generally "new things of note", as these previously weren't tracked in one place. It has a workboard[1] that is is broken up into: * one column for each week for the current month * one column for each remaining month in the current quarter * then "not soon" The scope of this project covered both "things that might break the site or are otherwise risky" and also "things people might expect to be notified about". At the time things got released quite often without a standard way for people to find that they were coming. I helped Erik with maintaining this project because it was also useful for our weekly "roadmap and deployments update" meeting where most WMF engineering managers got together for about 15-30 minutes to go over: * What, of note, is going out next week? * What, of note, is going out in the near term (i.e.: next few weeks)? * Anything else we should know about? Outcomes of this meeting were: * An updated outline of upcoming deployments on the Deployment Calendar[2] ** This helped inform the work of the WMF RelEng and Ops teams, especially * A time/space for people (especially Erik or others with intimate "community knowledge/intuition") to object to something going out at all, or at the proposed time Since this project was set up, Guillaume started the #user-notice and #developer-notice projects [4][5], which cover the "things to tell people about" a lot better, are much more general covering incidents and planned outages as well as code deployments, and are communicated out via volunteer translators to dozens of community notice boards every week. == Current world / Assessment == We are still using the #roadmap project for a lot of things that don't risk deployment/stability disruption, and also updating the Deployments Calendar on wikitech. It is my opinion that there is not enough gain from maintaining both work products to justify the effort, especially as #user-notice and #developer-notice have become so valuable. == Proposal == I propose that we discontinue the use of #roadmap. Potential gaps created by the deprecating of #roadmap and my proposed solutions: * Lack of a project that tracks big upcoming software/product releases ** The #release[3] project was created for this * Lack of a time-scale perspective of upcoming releases/deployments ** I believe that the Deployments Calendar[2], while imperfect (wiki templates), fulfills this * Users aren't informed of upcoming changes ** the #user-notice[4] project in Phabricator should be used for that == Expectations == To successfully do this (deprecate #roadmap) I expect all WMF Engineering teams (as the group of developers I have more influence over versus the Wikimedia engineering community) to pro-actively communicate out their plans, in public, with the appropriate use of the Deployments Calendar and the #user-notice Phabricator project. This means engaging with the Community Engagement/Liaison team when appropriate. In no small way this is me, as Release Manager, showing trust in the work of the WMF Engineering teams (which includes the product managers). Do good things with it :-) Let me know if you have any concerns, Greg [0] https://phabricator.wikimedia.org/project/profile/1109/ [1] https://phabricator.wikimedia.org/project/board/1109/ [2] https://wikitech.wikimedia.org/wiki/Deployments [3] https://phabricator.wikimedia.org/project/profile/1333/ [4] https://phabricator.wikimedia.org/tag/user-notice/ [5] https://phabricator.wikimedia.org/tag/developer-notice/ -- | Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E | | identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |

6 6

Re: [Wikitech-l] [WikimediaMobile] Performance audit example
by Jon Robson 06 Jul '15

06 Jul '15

cc wikitech - I think this is important for all of us to think about - not just those working on mobile, since mobile still loads a lot of what desktop does... On Mon, Jul 6, 2015 at 8:40 AM, Joaquin Oltra Hernandez <jhernandez(a)wikimedia.org> wrote: > Hey, > > I saw the other day a performance audit that Paul Irish did for the mobile > site of reddit. > > It is a great audit and a great example of how to do a performance review of > a site, I encourage all to carefully read it as we are going to have to do > something similar in the following sprints in order to enable us to do more > concrete performance work on the mobile website. > > https://github.com/reddit/reddit-mobile/issues/247 > > Awesome stuff. > > _______________________________________________ > Mobile-l mailing list > Mobile-l(a)lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/mobile-l > -- Jon Robson * http://jonrobson.me.uk * https://www.facebook.com/jonrobson * @rakugojon

2 1

Call for participation in OpenSym 2015, Aug 19-20, San Francisco!
by Dirk Riehle 04 Jul '15

04 Jul '15

Call for participation in OpenSym 2015! Aug 19-20, 2015, San Francisco, http://opensym.org ---- FOUR FANTASTIC KEYNOTES Richard Gabriel (IBM) on Using Machines to Manage Public Sentiment on Social Media Peter Norvig (GOOGLE) on Applying Machine Learning to Programs Robert Glushko (UC BERKELEY) on Collaborative Authoring, Evolution, and Personalization Anthony Wassermann (CMU SV) on Barriers and Pathways to Successful Collaboration More at http://www.opensym.org/category/conference-contributions/keynotes-invited-t… ---- GREAT RESEARCH PROGRAM All core open collaboration tracks, including - free/libre/open source - open data - Wikipedia - wikis and open collaboration, and - open innovation More at http://www.opensym.org/2015/06/25/preliminary-opensym-2015-program-announce… ---- INCLUDING OPEN SPACE The facilities provide room and space for your own working groups. ---- AT A WONDERFUL LOCATION OpenSym 2015 takes place from Aug 19-20 at the Golden Gate Club of San Francisco, smack in the middle of the Presidio, with a wonderful view of the Golden Gate Bridge. More at http://www.opensym.org/os2015/location/ ---- REGISTRATION Is simple, subsidized, and all-encompassing. Find it here: http://www.opensym.org/os2015/registration/ Prices will go up after July 12th, so be sure to register early! ---- We would like to thank our sponsors Wikimedia Foundation, Google, TJEF, and the ACM.

1 0

Blocking Resources from Google crawl
by Jon Katz 03 Jul '15

03 Jul '15

Hi, Wes noticed on Monday that, according to Google, they are unable to reach a growing number of our resources. If you remember, we had a similar issue a couple weeks ago back when we were on http fixed by ( https://gerrit.wikimedia.org/r/#/c/214705/1). The growth of this one starts the day that search traffic started heading to https. Anyone have ideas on what might be causing this? -J Screenshots below, followed by drill-down of specific resources. Today on https://en.wikipedia.org https://www.dropbox.com/s/skmdo1u1dh8jy0z/Screenshot%202015-07-01%2010.23.3… Previous incident on http://en.wikipedia.org https://www.dropbox.com/s/l7vrs4cvs6vga1j/Screenshot%202015-07-01%2010.24.3… Digging into en.wikipedia further we see its mostly caused by blocks for this resource: on Meta.wikimedia.org <http://meta.wikimedia.org/> most of the blocks are for this resource: https://en.wikipedia.org/w/index.php?title=MediaWiki:Common.js/file.js&acti…

3 2

Upcoming in October: Seattle GNU/Linux conference
by Pine W 02 Jul '15

02 Jul '15

The 2015 Seattle GNU/Linux conference (SeaGL) call for proposals is now open. I've submitted a proposal for a 50-minute workshop regarding how to edit Wikipedia, and may submit more proposals in collaboration with my colleagues in Cascadia Wikimedians. I'm sure that SeaGL would be happy to consider technical presentations about MediaWiki, Wikimedia analytics, Wikimedia Labs, our upstream tools, etc. if you're interested. Please consider submitting a proposal and coming to Seattle for the conference. http://seagl.org/ Regards, Pine

1 0

2026

2025

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 July 2015