Wikitech-l October 2013

wikitech-l@lists.wikimedia.org

148 participants
152 discussions

Deletion schema proposal: Bug 55398
by Nathan Larson 18 Oct '13

18 Oct '13

In one of the earlier discussions about revising the deletion schema, Happy-Melon pointed out, "Right now everyone who has ideas for *an* implementation isn't working on it because they don't know if it's *the* implementation we want." It seems to me that if one proposal is clearly superior, we may as well pick that one, so someone can get to work on it; but if the proposals are about equally good, then we may as well pick one at random, or whatever proposal is slightly better than the others, so someone can get to work on that one. http://thread.gmane.org/gmane.science.linguistics.wikipedia.technical/48109 The RFC over at MediaWiki.org hasn't received a lot of comment. Is there any objection to my implementing the "new field" option described at https://www.mediawiki.org/wiki/Requests_for_comment/Page_deletion ? I.e., I would add a new field, page.pg_deleted (analogous to revision.rv_deleted). Also, I would add revision.rv_logid to store the log_id of the deletion event. Upon restoring a page, only the revisions pertaining to the selected deletion event(s) would be restored. So, suppose you revision delete some revisions from a page for copyvio reasons. Those revisions are now updated as rv_deleted=[whatever value we want to use to signify the kind of access restrictions imposed by the deletion], and revision.rv_log_id=1, assuming that is the first log action ever performed on that wiki. Later, you delete the whole page (update rv_log_id=2 for the remainder of that page's revisions) for notability reasons. Then you decide you were mistaken about notability, but the copyvios would still be a problem. You undelete the page, selecting only that second deletion action. You only restore the revisions that have rv_logid=2, and leave the rv_logid=1 revisions deleted. This will render the archive table obsolete, so it can be deprecated/eliminated. I would like to code this for v1.23. https://bugzilla.wikimedia.org/show_bug.cgi?id=55398 Thanks. -- Nathan Larson https://mediawiki.org/wiki/User:Leucosticte

1 0

Next Bugday: ''Pywikibot'' ''20:00 Thursday, October 24, 2013 - Sunday, October 27 22:00'' UTC
by Amir Ladsgroup 18 Oct '13

18 Oct '13

Hello, Please join us on the next Wikimedia Bugday: 20:00 Thursday, October 24, 2013 - Sunday, October 27 22:00 UTC[1] in #pywikipediabot on Freenode IRC [2] We will be triaging bug reports pywikibot [3]. Pywikibot recently moved its code repository from SVN to Git and its bugtracker from SourceForge to Wikimedia Bugzilla. Now many older tickets need retesting and cleanup (around 700 bugs). We will be focusing on retesting, and we will comment on bug reports that need status updates, and have a good time working together on improving Pywikibot! Everyone is welcome to join, and no technical knowledge needed! It's an easy way to get involved in the community or to give something back. This even is part of a weekly QA activity [4], so we encourage you to triage throughout the week and record your activity on the bug day etherpad [5]. This information and more can be found here: https://www.mediawiki.org/wiki/Bug_management/Triage/20131024 For more information on triaging in general, check out https://www.mediawiki.org/wiki/Bug_management/Triage I look forward to seeing you there. Amir on behalf of Pywikibot developers [1] Timezone converter: http://www.timeanddate.com/worldclock/converter.html [2] See http://meta.wikimedia.org/wiki/IRC for more info on IRC chat [3] https://www.mediawiki.org/wiki/Bug_management/Triage/20131024 [4] https://www.mediawiki.org/wiki/QA/Weekly_goals [5] http://etherpad.wmflabs.org/pad/p/BugTriage

1 0

IRC office hour for Flow
by Nick Wilson (Quiddity) 18 Oct '13

18 Oct '13

You are invited to an IRC office hour, 18:00-19:00 UTC on 24 October to discuss Flow. A lot of the documentation is in the process of being overhauled, but these 2 pages are a good primer for our short-term plans, and what we're experimenting with, if you haven't seen them already. https://en.wikipedia.org/wiki/Wikipedia:Flow/MVP https://en.wikipedia.org/wiki/Wikipedia:Flow/Design_FAQ === Event Details === What: Flow Office hour When: October 24, 2013 (Thursday). 1800-1900 UTC http://www.timeanddate.com/worldclock/fixedtime.html?hour=18&min=00&sec=0&d… Where: IRC Channel #wikimedia-office on FreeNode Note: The logs for today's (quiet, accidentally announced with the wrong month) meeting, can be seen at https://meta.wikimedia.org/wiki/IRC_office_hours/Office_hours_2013-10-17 Thanks, Quiddity

1 0

Re: [Wikitech-l] [Product] Bugs on the deployment train
by Arthur Richards 17 Oct '13

17 Oct '13

+teampractices and wikitech-l for more input On Wed, Oct 16, 2013 at 11:22 AM, Arthur Richards <arichards(a)wikimedia.org>wrote: > I generally agree with James'/VE's approach. I'm not sure we can > reasonably come up with a sound metric (eg 'degredation that affects > roughly one percent of users') as it may not always be easily measurable. I > think a gut-check, qualitative assessment should suffice for these kinds of > issues, and can probably be broken into a few buckets: > > *) critical functionality is BROKEN (eg edits are not being saved, article > content is not accessible), there is a security concern, or a legal issue - > this needs to be fixed ASAP, like possibly before the next lightning deploy > *) semi-critical functionality is broken but doesn't impede basic usage of > critical site components (imo: reading, editing [in that order]) - (eg the > watchlist star on an article doesn't accurately indicate if an article is > being watched) - fixed and backported with earliest possible lightning > deploy window > *) annoyances (styling not quite right, obscure javascript errors), > non-security/legal issues in beta/alpha versions - fixed with next > deployment train > > This has generally been our approach to date on the mobile web team, > although I don't think we've ever been explicit about a rubric. > > > On Tue, Oct 15, 2013 at 1:53 PM, James Forrester <jforrester(a)wikimedia.org > > wrote: > >> Kenan, >> >> For VE we backport (cherry pick) fixes of major issues ASAP (generally by >> grabbing the next available Lightning Deploy window after we've tested it), >> but for inconveniences (i.e., things not quite as intended but still >> workable, or only affecting a few users) we generally just go for the next >> week's deployment train instead. Otherwise, yeah, they just join the >> backlog. >> >> J. >> >> >> On 15 October 2013 13:49, Kenan Wang <kwang(a)wikimedia.org> wrote: >> >>> Hey, >>> >>> The mobile team just got onto the deployment train. We're currently >>> looking to understand what we do when we find bugs caused by the previous >>> release during the deployment train. I proposed a three tiered triage >>> system to my team: >>> >>> Current train: degradation that affects roughly one percent of users in >>> a noticeable way >>> Current iteration, next train: degradation that affects less than one >>> percent of users in a noticeable way >>> Backlog: degradation that affects less than .1 percent of users in a >>> noticeable way, or affects users in a cursory way >>> >>> But was wondering if there were any other systems that teams had in >>> place to deal with this issue. >>> >>> Also, if you fix a bug does your team typically deploy during the next >>> deployment window available or do you wait to deploy until you have a >>> couple of fixes? >>> >>> -- >>> >>> Kenan Wang >>> Product Manager, Mobile >>> Wikimedia Foundation >>> >>> _______________________________________________ >>> Wmfproduct mailing list >>> Wmfproduct(a)lists.wikimedia.org >>> https://lists.wikimedia.org/mailman/listinfo/wmfproduct >>> >>> >> >> >> -- >> James D. Forrester >> Product Manager, VisualEditor >> Wikimedia Foundation, Inc. >> >> jforrester(a)wikimedia.org | @jdforrester >> > > > > -- > Arthur Richards > Software Engineer, Mobile > [[User:Awjrichards]] > IRC: awjr > +1-415-839-6885 x6687 > -- Arthur Richards Software Engineer, Mobile [[User:Awjrichards]] IRC: awjr +1-415-839-6885 x6687

2 1

Welcome Gergő Tisza!
by Rob Lanphier 17 Oct '13

17 Oct '13

Hi everyone, I'm pleased to announce Gergő Tisza is joining our Mulitmedia team today as a Software Engineer on the team. He'll be working most closely with Mark Holmquist and Fabrice Florin on new media handling features (first up: helping Mark finish off the new Media Viewer). He joins us most recently from Rocket Internet Gmbh, where he helped relaunch the company website, and he has several years of PHP experience before that. Gergő has been editing Wikipedia for about 9 years, as an anon for his first year, and then as User:Tgr. He's most active on Hungarian Wikipedia, but does some editing on the other wikis as well. He's also active in many other ways: as one of the founding members of Wikimedia Hungary, serving on the board for some of the time since then, as well as helping build some of their fundraising infrastructure. He also helped out with Wiki Loves Monuments, for example working out a bot to import images off of one of the more common Hungarian image hosters. He's also been very active in our Wikimedia Ambassadors group, helping smooth the rollout of several new features. He plans to move to San Francisco in the coming months, but will be splitting his time between Berlin, Germany and Sopron, Hungary until he can make the move to the U.S. Welcome, Gergő! Rob

4 3

[IRC] wm-bot semi outage
by Petr Bena 17 Oct '13

17 Oct '13

Hi, because of this bug: https://bugzilla.wikimedia.org/show_bug.cgi?id=55690 wm-bot is unable to write logs to file storage. Unfortunatelly since 10 minutes ago, the mysql storage broke as well, I have no idea why but I am afraid that only fix that comes to my mind now involves bot restart which isn't possible because all logs that couldn't be written are cached in operating memory (so if I restarted wm-bot we would loose 2 - 3 days of logs of all channels that are in RAM now). So, if someone wondered what is up with public channel logging, this is a reason why there are logs missing, not only on file storage at bots.wmflabs.org/~wm-bot/logs but also sql at http://tools.wmflabs.org/wm-bot/logs/ I hope wmf will soon start selling "I love gluster" t-shirts :-) I would get one

3 5

Inspecting page performance with mw.loader.inspect()
by Ori Livneh 17 Oct '13

17 Oct '13

If you are know how to use your browser's JavaScript console, you can now get an ordered list of all ResourceLoader modules that are loaded on the page, sorted by the total size of each module's JavaScript and CSS assets -- simply run "mw.loader.inspect();". It works best in newer versions of Chromium / Chrome, where it takes advantage of the availability of console.table(). It looks like this: http://i.imgur.com/zGymrsF.png In the course of testing this feature yesterday, Matt Flaschen spotted and fixed redundant module loading in TimedMediaHandler (see bug 55550). That's pretty cool, no? Do remember that size != performance, though -- just because a module is small does not mean that it is performant. (The reverse is also true.) This tool also does not account for factors like gzip compression. So no burning developers at the stake, please :) But curious poking is definitely encouraged. Thanks to Timo & Roan for helping this along. --- Ori Livneh ori(a)wikimedia.org

5 11

Operations team announcements: Ryan and Leslie
by Ken Snider 17 Oct '13

17 Oct '13

Hello! I'm extremely pleased to announce that we've had two promotions within the Technical Operations team! Leslie Carr has been promoted to Senior Operations Engineer (Networking). As many of you know, along with Mark, Leslie has been instrumental in securing preferred rates and contracts with with connectivity providers and vendors on the networking side of our infrastructure - in a world where human connections are every bit as important as topographic ones, Leslie has maintained a vast network of contacts to help ensure that we're receiving competitive pricing, fair peering, and a plethora of other perks that come part and parcel with maintaining solid relationships in the networking arena, while also taking point on many of the technical aspects of our network infrastructure as well. We're lucky to have her, and I look forward to working with her as the team completes the setup of ULSFO and begins work on our next data-centre project. Ryan Lane has also been promoted to Senior Operations Engineer. Ryan has served as the lead on the Labs project, a component of our infrastructure that has become increasingly critical to projects both within WMF engineering (with Beta Labs), as well as with various volunteer projects (via Tool Labs). Ryan is about to head up the migration of this infrastructure from Tampa to Ashburn as part of our plan to sunset the Tampa data-centre. Additionally, Ryan has also played a key role in several non-labs-related projects, including most recently our HTTPS-as-default project, as well as work on integrating git-deploy into the mediawiki deployment pipeline. Ryan's work has been invaluable, and this promotion well-deserved. Thanks! --Ken.

9 8

Global Day of Code Retreat
by Michelle Grover 17 Oct '13

17 Oct '13

Hi folks, I had the opportunity to go to the local Software Craftmanship Meetup here in Mass last night which was fun and mind bending because I’m old and forgot about things like tail call recursion (see Zack’s blog post if you’d like to see what we worked on… http://zdsbs.blogspot.com/) So December 14th has been deemed “Global Day of Code Retreat” If you’ve never heard about it please take a look http://gdcr.coderetreat.org. Just thought I would pass it on to others in case there’s any interest. Thanks!

1 0

Which MariaDB engine does Wikimedia use?
by David Gerard 16 Oct '13

16 Oct '13

Does Wikimedia use InnoDB, Maria or something else as the database engine for its MariaDB servers? - d.

5 7

← Newer
1
...
6
7
8
9
10
11
12
...
16
Older →

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 October 2013