Re: [Wikitech-l] [Wmfall] Announcement: C. Scott Ananian joins Wikimedia as Senior Features Engineer
Scott - I'm really glad that you've joined WMF engineering! The work on Parsoid is groundbreaking. It will open the door to collaboration at a scale not seen before. And it will require contributors of your level of experience to pull it off. Thanks for coming on board -- I look forward to working with you. And thanks to Terry for investing in growing this mission-critical team. Erik -- Erik Möller VP of Engineering and Product Development, Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Wikimedia engineering June 2013 report
Hi, The report covering Wikimedia engineering activities in June 2013 is now available. Wiki version: https://www.mediawiki.org/wiki/Wikimedia_engineering_report/2013/June Blog version: https://blog.wikimedia.org/2013/07/12/engineering-june-2013-report/ We're also proposing a shorter, simpler and translatable version of this report that does not assume specialized technical knowledge: https://www.mediawiki.org/wiki/Wikimedia_engineering_report/2013/June/summary Below is the full HTML text of the report. As always, feedback is appreciated on the usefulness of the report and its summary, and on how to improve them. -- Major news in June include: - The preparation for the activation of VisualEditorhttps://blog.wikimedia.org/2013/06/06/preparing-for-visualeditor-on-all-wikipedias/to most Wikipedia sites, and its debut on the English Wikipediahttps://blog.wikimedia.org/2013/07/01/visualeditor-beta-rollout/ ; - News around Language engineeringhttps://blog.wikimedia.org/2013/06/03/language-engineering-development-updates-and-events/, including the preparationhttps://blog.wikimedia.org/2013/06/06/universal-language-selector-coming-to-all-wikis/and activationhttps://blog.wikimedia.org/2013/07/01/universal-language-selector-uls-deployed-on-more-than-150-wikis/of the Universal Language Selectors on many wikis; - An explanation of how bugs are discovered and fixedhttps://blog.wikimedia.org/2013/06/04/volunteers-and-staffers-teach-learn-make-at-amsterdam-hackathon/ . - A retrospective on the Amsterdam hackathonhttps://blog.wikimedia.org/2013/06/04/volunteers-and-staffers-teach-learn-make-at-amsterdam-hackathon/ . *Note: We're also providing a shorter, simpler and translatable version of this reporthttps://www.mediawiki.org/wiki/Wikimedia_engineering_report/2013/June/summarythat does not assume specialized technical knowledge. * Personnel Work with us https://wikimediafoundation.org/wiki/Work_with_us Are you looking to work for Wikimedia? We have a lot of hiring coming up, and we really love talking to active community members about these roles. - Software Engineer - Fundraisinghttp://hire.jobvite.com/Jobvite/Job.aspx?j=oawpXfwM - Software Engineer - Language Engineeringhttp://hire.jobvite.com/Jobvite/Job.aspx?j=oH3gXfwH - Director of Program - Mobilehttp://hire.jobvite.com/Jobvite/Job.aspx?j=oGqAXfwn - Software Engineer - Multimedia Systemshttp://hire.jobvite.com/Jobvite/Job.aspx?j=oj40Wfw3 - Senior Software Engineer - Platformhttp://hire.jobvite.com/Jobvite/Job.aspx?j=ouLnWfwi - UX Designer http://hire.jobvite.com/Jobvite/Job.aspx?j=onImXfw8 - Product Manager - Platformhttp://hire.jobvite.com/Jobvite/Job.aspx?j=o3vtXfwI - Dev-Ops Engineer - SREhttp://hire.jobvite.com/Jobvite/Job.aspx?j=ocLCWfwf Announcements - Sean Pringle joined the Technical Operations team as our Storage and Database Engineer (announcementhttp://www.gossamer-threads.com/lists/wiki/wikitech/368588 ). - Brian Wolff https://www.mediawiki.org/wiki/User:Bawolff joined the Wikimedia Platform Engineeringhttps://www.mediawiki.org/wiki/Wikimedia_Platform_Engineeringgroup as Software developer for the Summer, working on multimedia contribution and review (announcementhttp://lists.wikimedia.org/pipermail/wikitech-l/2013-June/069724.html ). - Ken Snider joined the Technical Operations team as an international contractor, poised to fill the Director of Technical Operations position ( announcementhttp://lists.wikimedia.org/pipermail/wikitech-l/2013-June/069844.html ). - Toby Negrin joined the Engineering department as Director of Analytics (announcementhttp://lists.wikimedia.org/pipermail/wikimediaannounce-l/2013-June/000675.html ). Technical Operations *Site infrastructure* As part of our capacity planning work, Mark Bergsma upgraded most of our Varnish infrastructure (in EQIAD ESAMS) with newer and faster servers. He will be adding new mobile Varnish servers in ESAMS next, this coming month. Rob Halsell and Daniel Zahn are pushing ahead with the migration of the other applications https://wikitech.wikimedia.org/wiki/Tampa_cluster from Tampa to EQIAD. New Parsoid application and Varnish servers were also deployed in anticipation of the coming VisualEditor deployment. Meantime, Alexandros Kosiaris is starting the backup project work; read more about the project https://wikitech.wikimedia.org/wiki/Projects#Backup_infrastructureand the technology https://wikitech.wikimedia.org/wiki/Bacula. Mark also put in the finishing touches to deploy all the new network infrastructure at ESAMS. With help from Mark and Leslie Carr, we finally got approval from ARIN for some new IPv4 addresses, needed for our new ULSFO buildup.Many people are refactoring Puppet code with the ultimate goal of having everything organized into Puppet modules. Andrew Bogott, Antoine Musso and Alexandros are setting up an
Re: [Wikitech-l] Quo Vadis, Vagrant
On Sun, Jul 7, 2013 at 6:35 AM, Ori Livneh o...@wikimedia.org wrote: This is now implemented in https://gerrit.wikimedia.org/r/#/c/72343/. It needs a lot of testing, especially on Windows. It works great on my Mac machine. I have tested it with browsertests role. Željko ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Adding to the skin toolbox
I am using the BaseTemplateToolbox. If I print-r($toolbox) at the end of my hook, this is added to toolbox. [proplinkhere] = Array ( [text] = Prop Links Here [href] = /acc_arswiki/index.php?title=Special%3AProplinkhere/Amikacin [id] = t-proplinkhere ) Which is what I added. But it does not show up in the toolbox. Do I have to add t-proplinkhere anywhere? Do I have to do anything with BaseTemplate::makeListItem? I did add this to the i18n message file: 'accesskey-t-proplinkhere' = '', 'tooltip-t-proplinkhere' = 'List all pages that have properties that link to this page. ', Thanks, Mary -Original Message- From: wikitech-l-boun...@lists.wikimedia.org [mailto:wikitech-l-boun...@lists.wikimedia.org] On Behalf Of Daniel Friesen Sent: Thursday, July 11, 2013 5:53 PM To: wikitech-l@lists.wikimedia.org Subject: Re: [Wikitech-l] Adding to the skin toolbox BaseTemplateToolbox is the cleanest hook to use. There's also SkinTemplateToolboxEnd which is hideous but existed before BaseTemplate. So ideally use BaseTemplateToolbox, unless you happen to have an ancient pre-BaseTemplate skin that's still hardcoding the toolbox. https://www.mediawiki.org/wiki/Manual:Hooks/BaseTemplateToolbox https://www.mediawiki.org/wiki/Manual:Hooks/SkinTemplateToolboxEnd On Thu, 11 Jul 2013 14:39:42 -0700, Beebe, Mary J bee...@battelle.org wrote: I am using the Vector skin. I have an extension very similar to whatlinkshere. It needs to take the current page as the parameter just like whatlinkshere. I would like to add it to the toolbox, but actually I do not care where it is in the navigation but the toolbox seems the most logical. We have done this before with other older skins that had something like this section: div id=gumax-special-tools I noticed that getToolBox() is within BaseTemplate. Is there a way to add this method to the tool box? Thanks, Mary Beebe Battelle - Charlottesville, VA Office: 434- 951-2149 **Confidentiality Notice** This message is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and/or otherwise exempt from disclosure under applicable law. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering the message to the intended recipient, any disclosure, dissemination, distribution, copying or other use of this communication or its substance is prohibited. If you have received this communication in error, please return to the sender and delete from your computer system. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l -- ~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://danielfriesen.name/] ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Announcement: C. Scott Ananian joins Wikimedia as Senior Features Engineer
On 07/11/2013 05:53 PM, Jeroen De Dauw wrote: Hey, Welcome to community the Scott! Looks like we are one good engineer stronger now :) Cheers -- Jeroen De Dauw Seconding this - welcome to WMF and thanks for joining us! -- Sumana Harihareswara Engineering Community Manager Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Project idea
On Thu, Jul 11, 2013 at 6:32 PM, Steven Walling steven.wall...@gmail.comwrote: I have no idea how many pageviews we get coming from ChromeOS devices, and I suspect it's hard to differentiate from regular Chrome visits on other systems? Anyway, sales trends clearly suggest they are becoming more of a niche to pay attention to. Actually, ChromeOS's User-Agent string reports the OS distinctly as 'CrOS'... so we should be able to measure it pretty easily compared to other OSes. It might be nice to have an official Wikipedia Chrome app. There are a few in the Web Store now,[2] but they're not great. For Chrome OS users, the main advantages of having an app, even if all it does is redirect to the website, is the ability to add it to your Chrome homescreen and the dock. If you're going to build an OS around the web, web apps should really just be fancy bookmarks. :) I'd recommend against building any specific 'app' for a web-based OS like this, but if we can have a Chrome Web Store entry that conveniently bookmarks us and that makes us easier to use, well that'd be awesome. I'd also kind of like to kill our current Firefox OS app and replace it with a pointer to the mobile web site for the same reason; we have more features on the mobile web site than on the current port-of-a-PhoneGap-app Firefox OS app, which isn't getting maintained. -- brion ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Project idea
On 12.07.2013, 20:07 Yuvi wrote: On Fri, Jul 12, 2013 at 9:30 PM, Brion Vibber bvib...@wikimedia.org wrote: I'd also kind of like to kill our current Firefox OS app and replace it with a pointer to the mobile web site for the same reason; we have more features on the mobile web site than on the current port-of-a-PhoneGap-app Firefox OS app, which isn't getting maintained. +1, PhoneGap sucks. Also I think we have an app on the Blackberry store too, which too should be replaced / killed. And a DelphinBrowser app, apparently already bitrotten to death. -- Best regards, Max Semenik ([[User:MaxSem]]) ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Project idea
On Fri, Jul 12, 2013 at 9:00 AM, Brion Vibber bvib...@wikimedia.org wrote: I'd recommend against building any specific 'app' for a web-based OS like this, but if we can have a Chrome Web Store entry that conveniently bookmarks us and that makes us easier to use, well that'd be awesome. You mean you recommend against OS-specific apps, like we have specific apps for Windows Phone, iOS, and Android? ;) Snark aside: what you proposed is essentially how most Chrome apps work and is easiest to implement. For HTML5 games and such, I'm sure it's more app-like in that you may not be able to launch the game without installing the app, but most people basically just redirect users to the normal site. Obviously this makes the use of the name app seem bizarre, but the advantage for ChromeOS users is that we make it easier to get back to Wikipedia. (One step instead of three.) ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Announcement: C. Scott Ananian joins Wikimedia as Senior Features Engineer
On Thu, Jul 11, 2013 at 11:19 PM, Sumana Harihareswara suma...@wikimedia.org wrote: On 07/11/2013 05:53 PM, Jeroen De Dauw wrote: Hey, Welcome to community the Scott! Looks like we are one good engineer stronger now :) Cheers -- Jeroen De Dauw Seconding this - welcome to WMF and thanks for joining us! Ditto. It's exciting to have you on board. Welcome! ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Project idea
As a ChromeOS user I really just think of it as a laptop with a funky set of apps. I'm pretty sure I wouldn't have thought to search for a wikipedia app for it because I'm so used to getting wikipedia in the browser. On the other hand if the app could modify search key behaviour so I can hit search, type wikipedia, hit tab, type search term, then hit enter, then I'd like that. On the other other hand I already have this behaviour in all browser windows so from (pretty much) anywhere in the OS I can hit ctrl-t, ctrl-l, type wikipedia, hit tab, type search term, then hit enter. Also, it feels like that search key behaviour is up to google anyway and at some point they'll make it work the same as the location bar. Nik On Fri, Jul 12, 2013 at 2:22 PM, Steven Walling steven.wall...@gmail.comwrote: On Fri, Jul 12, 2013 at 9:00 AM, Brion Vibber bvib...@wikimedia.org wrote: I'd recommend against building any specific 'app' for a web-based OS like this, but if we can have a Chrome Web Store entry that conveniently bookmarks us and that makes us easier to use, well that'd be awesome. You mean you recommend against OS-specific apps, like we have specific apps for Windows Phone, iOS, and Android? ;) Snark aside: what you proposed is essentially how most Chrome apps work and is easiest to implement. For HTML5 games and such, I'm sure it's more app-like in that you may not be able to launch the game without installing the app, but most people basically just redirect users to the normal site. Obviously this makes the use of the name app seem bizarre, but the advantage for ChromeOS users is that we make it easier to get back to Wikipedia. (One step instead of three.) ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Weekly deployment highlights - week of July 15th, 2013
Hello and welcome to this week's deployment highlights email for the week of July 15th. For the full list of deployments that are currently scheduled, see: https://wikitech.wikimedia.org/wiki/Deployments#Week_of_July_15th == Monday == * Following the normal cycle, all non-Wikipedia sites (wiktionary, wikinews, etc) are upgrading to MediaWiki 1.22wmf10 * Pending the go/no-go decision later this afternoon (Pacific time), VisualEditor will be enabled for all English Wikipedia users (both logged in and not). == Tuesday == * UniversalLanguageSelector will be rolling out more bugfixes and performance improvements. == Thursday == * test.wikipedia.org, test2., test.wikidata.org, login.wikimedia.org, and mediawiki.org will be upgraded to MediaWiki 1.22wmf11 * The rest will be on 1.22wmf10 As always, please reply if you have any questions! Greg -- | Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E | | identi.ca: @gregA18D 1138 8E47 FAC8 1C7D | ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] WMF Engineering roadmap update
Hello and welcome to the latest edition of the WMF Engineering Roadmap update. This is a larger update than normal as I missed sending this out the past two weeks (one week being the week of July 4th, and the other this was deprioritized due to other needs). My apologies. As always, you can see the full roadmap, with information links, here: http://www.mediawiki.org/wiki/Roadmap == Flow == * June: started architectual discussions. * July: have/or will hire for Front End engineers. * August: work on the API design. * September: First experimental release of the user-to-uesr discussion workflow (probably limited to an opt-in group). * December: Goal date for the full production release of the user-to-user discussion system. == Mobile Apps == * July: Revised login, iOS multi upload, bug fixes, back to regular releases, New detail page, earliy campaign work. == Mobile Web == * July: Watchlist thanking/reverting (in beta). Getting started for mobile in beta. * August: continued watchlist thanking/reverting. Getting started for mobile planned to be stable. == Language == * July: ULS deployment to all wikis has been completed. Urgent bugfixes and performance patches are now being deployed during the weekly scheduled deployment window. == Ops == * July: Analysis and testing of Ceph lead to probable decision of staying with Swift. * September: Migration to eqiad (datacenter in Virginia) from tampa should be complete. * December: Creation and setup of the west coast data center should be complete. == Platform/MW Core == * July: ElasticSearch research (in addition to Solr). Review work of the GLAM Wiki Toolkit. * August: Deploy of either Solr or ElasticSearch to test2.wikipedia.org. Also, a deployment infrastructe sprint will begin. * September: An Admin Tool sprint begins. * October: goal date of new search to English Wikipedia. Also, HipHop deployment tentatively begins. * November: HipHop deployment tentatively completes. * December: A very tentative goal date for a centralized code repository pending other priorities. == QA == * July: more Jenkins job executers for faster full suite runs. Trainings for test development and failure analysis. Target groups tbd. * August: Continued improvements of BetaLabs == Eng Community Team == * August: Puppetize Bugzilla. QA training in automated testing for gadgets. * September: prep for next OPW round * October: Community metrics integration * December: run the application process for the next OPW round Best, Greg -- | Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E | | identi.ca: @gregA18D 1138 8E47 FAC8 1C7D | ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] mod_pagespeed and MediaWiki
On 12.07.2013, 3:16 Max wrote: FYI, Google already sent us a sample config for this module optimized for our mobile site, I'm going to try it tomorrow. And here are the results of my research: https://www.mediawiki.org/wiki/User:MaxSem/mod_pagespeed Briefly, this is interesting stuff, but not usable on WMF, or on any other large MW installations either. -- Best regards, Max Semenik ([[User:MaxSem]]) ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] mod_pagespeed and MediaWiki
On 12 July 2013 23:03, Max Semenik maxsem.w...@gmail.com wrote: And here are the results of my research: https://www.mediawiki.org/wiki/User:MaxSem/mod_pagespeed Briefly, this is interesting stuff, but not usable on WMF, or on any other large MW installations either. Does bugger-all good on small MW sites, too - the bottleneck with those will be CPU or memory well before it's sheer bytes served. - d. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] mod_pagespeed and MediaWiki
[cc'ing Joshua Marantz who leads the mod_pagespeed effort at Google, and Ilya Grigorik, their developer advocate for page performance] The principals behind mod_pagespeed, especially as they related to mobile page load performance as outlined in http://bit.ly/mobilecrp could themselves be implemented within mediawiki. mod_pagespeed itself can't just be dropped in to do the job, and especially doesn't play nicely with the full page edge caching wmf depends on; but it could be used as development guide. For mobile performance especially, the critical points are: * Everything needed to fully render above the fold content should fit within 10 packets, given our current 10 packet tcp initial connection window. * Those = 10 packets must be in the service of a single request. * All css required by that above-the-fold view must be inline. It doesn't have to be all of the css required for the page overall. * Same with javascript - anything not essential to above the fold should be deferred. I can't think of any good reasons why this couldn't be implemented by MobileFrontend. Accomplishing all of what mod_pagespeed addresses for general mediawiki use would likely involve a rewrite of resourceloader. -Asher On Fri, Jul 12, 2013 at 3:03 PM, Max Semenik maxsem.w...@gmail.com wrote: On 12.07.2013, 3:16 Max wrote: FYI, Google already sent us a sample config for this module optimized for our mobile site, I'm going to try it tomorrow. And here are the results of my research: https://www.mediawiki.org/wiki/User:MaxSem/mod_pagespeed Briefly, this is interesting stuff, but not usable on WMF, or on any other large MW installations either. -- Best regards, Max Semenik ([[User:MaxSem]]) ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] SUL2 deploy changed to Wednesday July 17th
And another delay. Due to prioritizing the VisualEditor deploy on Monday, and not wanting to overload too many changes at once, we're going to move the SUL2 deploy to Wednesday July 17th. Greg quote name=Greg Grossmeier date=2013-07-10 time=09:29:38 -0700 Update on deploy date: We are going to delay this rollout until Monday July 15th so we can iron out some last minute issues. We want the first experience anyone has with this to go smoothly so we think the small delay is worth it. If you have informed any Village Pumps of this deploy, please do me a favor and update them with the new date :-). Thanks for your understanding, Greg quote name=Greg Grossmeier date=2013-07-09 time=15:32:48 -0700 Summary: On Thursday July 11th we will be enabling a new centralized login service to make the login experience for users more streamlined. -- | Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E | | identi.ca: @gregA18D 1138 8E47 FAC8 1C7D | -- | Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E | | identi.ca: @gregA18D 1138 8E47 FAC8 1C7D | ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
