Wikitech-l June 2014

wikitech-l@lists.wikimedia.org

139 participants
147 discussions

Config class and 1.23
by Kevin Israel 04 Jun '14

04 Jun '14

Should the Config and GlobalConfig classes and the associated RequestContext methods be reverted from 1.23 as an incomplete feature? As far as I can tell, it is not yet used anywhere, so reverting it should be easy. getConfig() was added to IContextSource in 101a2a160b05[1]. Then the method was changed to return a new class of object (Config) instead of a SiteConfiguration object in fbfe789b987b[2]; however, the Config class faces significant changes in I5a5857fc[3]. [1]: https://gerrit.wikimedia.org/r/#/c/92004/ [2]: https://gerrit.wikimedia.org/r/#/c/109266/ [3]: https://gerrit.wikimedia.org/r/#/c/109850/ -- Kevin Israel - MediaWiki developer, Wikipedia editor http://en.wikipedia.org/wiki/User:PleaseStand

7 9

Huggle 3 released / Mac people needed
by Petr Bena 04 Jun '14

04 Jun '14

Good news Everyone <ref>https://www.youtube.com/watch?v=T2BNmn8TYdE</ref> We just released a stable version of huggle 3 which is likely full of some "unstable features" (some call these bugs). DWRTLD (don't want to read too long documents): Huggle is a fast-diff browser for mediawiki that allows you to revert bad edits very quickly. It works on many wmf projects and can be installed to any mediawiki wiki. It works on all major operating systems and you can find out more here: https://en.wikipedia.org/wiki/WP:Huggle EOF We didn't release any mac bundle, because we have nobody with a mac in our team, so in case you have mac and you have some programming skills, you can figure out how to build huggle (need Qt and CMake) and once you do that, let us know how you did it, so that we can update the manual. If you are willing to contribute more permanently, you can become release manager for Mac builds and provide them for download every new release. Let us know in e-mail or irc://chat.freenode.net/#huggle Thank you

4 4

Accessing current template information on wiki commons description page
by james harvey 04 Jun '14

04 Jun '14

Given a Wikimedia Commons description page URL - such as: https://commons.wikimedia.org/wiki/File:Van_Gogh_-_Starry_Night_-_Google_Ar… I would like to be able to programmatically retrieve the information in the "Summary" header. (Values for "Artist", "Title", "Date", "Medium", "Dimensions", "Current location", etc.) I believe all this information is in "Template:Artwork". I can't figure out how to get the wikitext/json-looking template data. If I use the API and call: https://commons.wikimedia.org/w/api.php?action=query&format=xml&titles=File… Then I don't get the information I'm looking for. This shows the most recent revision, and its changes. Unless the most recent revision changed this data, it doesn't show up. To see all the information I'm looking for, it seems I'd have to specify rvlimit=max and go through all the past revisions to figure out which is most current. For example, if I do so and I look at revid 79665032, that includes: "{{Artwork | Artist = {{Creator:Vincent van Gogh}} | . . . | Year = 1889 | Technique = {{Oil on canvas}} | . . ." Isn't there a way to get the current version in whatever format you'd call that - the wikitext/json looking format? In my API call, I can specify rvexpandtemplates which even with only the most recent revision gives me the information I need, but it's largely in HTML tables/divs/etc format rather than wikitext/json/xml/etc.

4 5

Re: [Wikitech-l] [Wikimedia-l] Quarterly reviews of high priority WMF initiatives
by Tilman Bayer 03 Jun '14

03 Jun '14

Minutes and slides from last week's quarterly review of the Foundation's Mobile Contributions team are now available at https://meta.wikimedia.org/wiki/Metrics_and_activities_meetings/Quarterly_r… . 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 Operations Analyst (Movement Communications) Wikimedia Foundation IRC (Freenode): HaeB

1 0

[ImageMap] Looking for a reviewer: Link directly to media file when [[Media:...]] namespace is used within an imagemap.
by Remco de Boer 03 Jun '14

03 Jun '14

Hi, I'm looking for someone to review and (hopefully) accept a very small (3 line) patch I wrote for the ImageMap extension. The patch improves the behavior of image maps with links to [[Media:...]] files. Instead of linking to the image page, these links should go directly to the media file (comparable to how regular [[Media:...]] links in wiki text work). My patch has been open for over three months now, and there is no registered maintainer of the ImageMap extension ( https://www.mediawiki.org/wiki/Developers/Maintainers#MediaWiki_extensions_…). I've tried to ping some folks whom I thought might be able to review my patch, but none of them has responded. The patch is in Gerrit, and can be viewed at https://gerrit.wikimedia.org/r/#/c/114439/ Kind regards, Remco de Boer

2 1

new auth/debug/Zero RfCs, + adding more office hours
by Sumana Harihareswara 03 Jun '14

03 Jun '14

Some newer RfCs that you ought to know about, mostly draft-ish and in progress. Please comment on their talkpages. * https://www.mediawiki.org/wiki/Requests_for_comment/SOA_Authentication "With many more entry points and the need for inter-service authentication, a service-oriented architecture requires a stronger authentication system." * https://www.mediawiki.org/wiki/Requests_for_comment/Debugging_at_production… "Sometimes we have to debug on production wiki, but don't want to show internal information to normal users..." * https://www.mediawiki.org/wiki/Requests_for_comment/Unfragmented_ZERO_design "In order to significantly reduce varnish fragmentation and reduce the complexity, Zero team would like to unify HTML served to all Zero partners's users...." Also: I've heard feedback that the RfC process ought to move faster, and that we ought to have more people from more disciplines take a look at changes that users will visually notice. Sounds good to me. So: * I'm going to add more IRC discussion hours that will be more for *discussing* specific RfCs and getting general community feedback, rather than asking for go/no-go decisions. These will be in addition to the weekly decision-oriented meetings. It seems like people get a lot out of having these real-time conversations in addition to the option to comment onwiki and onlist, so this is a way to push the most complex topics forward. This will also allow us to have more chats that suit different timezones. We will also sometimes piggyback them onto the videostreamed Tech Talks, with simultaneous Etherpad notes + IRC. * I'm going to make more of an effort to invite specific people from diverse disciplines to RfC discussions, e.g., QA people for debugging stuff, design/product people for user-visible changes, etc. I've been doing this but I'll be more systematic. Please help me out by spreading the word to people whom you think will be interested. -- Sumana Harihareswara Senior Technical Writer Wikimedia Foundation

3 2

Re: [Wikitech-l] 404 errors
by ENWP Pine 03 Jun '14

03 Jun '14

Ori, thanks for following up. I think I saw somewhere that there is a list of postmortems for tech ops disruptions that includes reports like this one. Do you know where the list is? I tried a web search and couldn't find a copy of this report outside of this email list. I personally find this report interesting and concise, and I am interested in understanding more about the tech ops infrastructure. Reports like this one are useful in building that understanding. If there's an overview of tech ops somewhere I'd be interested in reading that too. The information on English Wikipedia about WMF's server configuration appears to be outdated. Thanks, Pine > Date: Thu, 29 May 2014 22:38:10 -0700 > From: Ori Livneh <ori(a)wikimedia.org> > To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org> > Subject: Re: [Wikitech-l] 404 errors > Message-ID: > <CAHXK4ByYa8ae0EVGAUFWSCrjZtAQh+sjTW6ccJ14mB8o-teSoQ(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > On Thu, May 29, 2014 at 1:34 PM, ENWP Pine <deyntestiss(a)hotmail.com> wrote: > > > Hi, I'm getting some 404 errors consistently when trying to load some > > English Wikipedia articles. Other pages load ok. Did something break? > > > > TL;DR: A package update went badly. > > Nitty-gritty postmortem: > > At 20:25 (all times UTC), change Ie5a860eb9[0] ("Remove > wikimedia-task-appserver from app servers") was merged. There were two > things wrong with it: > > 1) The appserver package was configured to delete the mwdeploy and apache > users upon removal. The apache user was not deleted because it was logged > in, but the mwdeploy user was. The mwdeploy account was declared in Puppet, > but there was a gap between the removal of the package and the next Puppet > run during which the account would not be present. > > 2) The package included the symlinks /etc/apache2/wmf and > /usr/local/apache/common, which were not Puppetized. These symlinks were > unlinked when the package was removed. > > Apache was configured to load configuration files from /etc/apache2/wmf, > and these include the files that declare the DocumentRoot and Directory > directives for our sites. As a result, users were served with 404s. At > 20:40 Faidon Liambotis re-installed wikimedia-task-appserver on all > Apaches. Since 404s are cached in Varnish, it took another five minutes for > the rate of 4xx responses to return to normal (20:45).[1] > > [0]: https://gerrit.wikimedia.org/r/#/c/136151/ > [1]: > https://graphite.wikimedia.org/render/?title=HTTP%204xx%20responses%2C%2020… >

4 3

Search results on English Wikipedia not updating
by ENWP Pine 03 Jun '14

03 Jun '14

Hi, It appears that suggested search results are not being updated on English Wikipedia. The article [[Veterans Health Administration scandal of 2014]] doesn't appear in suggested search results when I type "Veterans Health Administration", and when I searched earlier today "VA scandal" in suggested search results showed its previous redirect destination instead of its current destination, although actually clicking on "VA scandal" redirected to the correct page. Any idea what's happening? Thanks, Pine

2 1

MediaWiki 1.23.0-rc.3 release candidate is available
by Markus Glaser 03 Jun '14

03 Jun '14

The third (and hopefully final) release candidate for 1.23.0 (1.23.0-rc.3) is now available for download. The changes since 1.23.0-rc.2 are as follows: * (bug 65225) jquery.suggestions: Handle CSS ellipsis better for IE. * (bug 65765) Add ar_text to the list from Revision::selectArchiveFields(). * DerivativeContext::setConfig should take a Config object. * Make abstract Config class truly implementation-agnostic. * (bug 65748) Officially deprecate skin autodiscovery. Full release notes: https://git.wikimedia.org/blob/mediawiki%2Fcore.git/1.23.0-rc.3/RELEASE-NOT… https://www.mediawiki.org/wiki/Release_notes/1.23 ********************************************************************** Download: http://download.wikimedia.org/mediawiki/1.23/mediawiki-core-1.23.0-rc.3.tar… http://download.wikimedia.org/mediawiki/1.23/mediawiki-1.23.0-rc.3.tar.gz GPG signatures: http://download.wikimedia.org/mediawiki/1.23/mediawiki-core-1.23.0-rc.3.tar… http://download.wikimedia.org/mediawiki/1.23/mediawiki-1.23.0-rc.3.tar.gz.s… Public keys: https://www.mediawiki.org/keys/keys.html Markus Glaser (Release Team)

1 0

php[world] Conference (November 12-14th, 2014)
by Terry Chay 02 Jun '14

02 Jun '14

Hey all, I got this e-mail because of my participation at various PHP and open source conferences. However, this new conference is more trying to focus around the PHP ecosystem of applications (MediaWiki, Wordpress, Drupal, …) which for a long time have had their own separate conferences (Berlin Hackathon, WordCamp, DrupalCon, …) independent of the normal PHP/LAMP ones (php|tek, ZendCon, OSCON, FOSDEM, …). Since I'm now a useless middle manager, haven't ever been a MediaWiki developer, and haven't developed on WordPress for at least a couple years, this conference doesn't apply to me. But you might be interesting in presenting a paper or attending. Take care, terry terry chay 최태리 Director of Features Engineering Wikimedia Foundation “Imagine a world in which every single human being can freely share in the sum of all knowledge. That's our commitment.” p: +1 (415) 839-6885 x6832 m: +1 (408) 480-8902 e: tchay(a)wikimedia.org i: http://terrychay.com/ w: http://meta.wikimedia.org/wiki/User:Tychay aim: terrychay Begin forwarded message: > From: php[architect] <promo(a)phparch.com> > Subject: Announcing php[world] Conference : Call for Papers Open! > Date: June 2, 2014 at 11:03:26 AM PDT > To: Terry <tchay(a)wikimedia.org> > Reply-To: <us6-49e37686e2-060218f07e(a)conversation01.mailchimpapp.com> > > Announcing php[world] - Call for Papers > November 10-14 - Washington, DC, USA > Is this email not displaying correctly? > View this email in your browser > > Bringing the world of PHP one step closer together... > We are excited to introduce a brand new conference from the team at php[architect]. This conference, php[world], is designed to bring together all of the various PHP communities into one place to share ideas. > > Our php[tek] conference is known as the definitive conference in the US for the core PHP developer. For this new conference, we wanted to create an environment that appealed to all the different communities that exist in the PHP ecosystem. Whether you are a core PHP developer, a heavy framework user (such as Zend Framework or Symfony), or a WordPress, Drupal, Joomla, or Magento developer … this conference will be for you! > > Details are still coming together, but lots of information has already been posted on the php[world] website and more updates will appear soon! > > > Call for Papers > Speaking of which, to make this conference happen and to bring these communities together, we need lots of paper submissions from a broad spectrum of speakers. Simply put ... we want to hear from you! > > Our Call for Papers is open until June 20th, but don't delay, get your submissions in early! > > > > > Registration > We've opened up registration as well, including some steep Early Bird discounts. If you aren't interested in speaking but want to make sure that you don't miss this event, you should pick up your tickets immediately before the prices rise. > > > > Share > Tweet > +1 > Share > Copyright © 2014 php[architect], All rights reserved. > You are receiving this email because you have done business with php[architect] in the past. > > Our mailing address is: > php[architect] > 201 Adams Avenue > Alexandria, VA 22301 > > Add us to your address book > > > unsubscribe from this list update subscription preferences > >

1 0

Jump to page:

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 June 2014