Wikitech-l February 2014

wikitech-l@lists.wikimedia.org

152 participants
162 discussions

Language Engineering IRC Office Hour on February 12, 2014 (Wednesday) at 1700 UTC
by Runa Bhattacharjee 06 Feb '14

06 Feb '14

[x-posted] Hello, The Wikimedia Language Engineering team will be hosting the monthly IRC office hour on February 12, 2014 (Wednesday) at 1700 UTC/ 0900 PDT on #wikimedia-office. This time we would be talking about the recent changes made to the Universal Language Selector (ULS) - the MediaWiki extension that provides unified language configuration[1] - and the impact on the Wikimedia wikis. We look forward to addressing any questions you may have about this. Please see below for the event details. Questions can also be sent to me before the event. See you all at the IRC office hour! Thanks Runa [1] https://www.mediawiki.org/wiki/Universal_Language_Selector Event Details: ========== # Date: February 12, 2014 # Time: 1700-1800 UTC, 0900-1000 PDT ( http://www.timeanddate.com/worldclock/fixedtime.html?iso=20140212T1700) # IRC channel: #wikimedia-office on irc.freenode.net Agenda: ====== 1. Universal Language Selector (ULS) update and developments 2. Q & A -- Language Engineering - Outreach and QA Coordinator Wikimedia Foundation

1 0

IRC meeting for RFC review
by Tim Starling 06 Feb '14

06 Feb '14

I would like to have an open IRC meeting for RFC review, on Tuesday 24 September at 22:00 UTC (S.F. 3pm). We will work through a few old, neglected RFCs, and maybe consider a few new ones, depending on the interests of those present. The IRC channel will be #mediawiki-rfc. -- Tim Starling

11 16

Bugzilla Etiquette
by Andre Klapper 05 Feb '14

05 Feb '14

Today I removed the "This page is currently a draft" banner on https://www.mediawiki.org/wiki/Bug_management/Bugzilla_etiquette as the comment rate on its Discussion page has been very low recently, hence I assume consensus has been found. The page is the outcome of lots of discussion among numerous community members (as a "Bugzilla etiquette guideline drafted: help complete it" banner was shown for several weeks on mediawiki.org). I would like to thank everybody who participated and helped in creating this document! andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/

2 1

Sphinx Documentation CI Build Task
by Matthew Walker 05 Feb '14

05 Feb '14

With some help from Hashar and Marktraceur I added some new CI build jobs for some fundraising stuff -- I noticed we had a job that indicates it'll build sphinx documentation so I figured I might as well add that and see where I get. ... Which is not very far -- the build fails with *19:11:58* + python setup.py build_sphinx*19:11:58* python: can't open file 'setup.py': [Errno 2] No such file or directory This makes sense; I don't have a setup.py file. But I cannot create it because I also don't know what's expected to be in that file and there doesn't seem to be anything on wikitech about this... I've used sphinx before via makefile and sphinx-build but clearly we are doing something different. Guidance please! :D ~Matt Walker Wikimedia Foundation Fundraising Technology Team

1 1

Timeline Generator for mediawiki
by Amanpreet Singh 04 Feb '14

04 Feb '14

Hi everyone, I recently came across a mentorship project at https://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#Provid… After having discussion on this topic with some people, I want to know what is the usability of this project. Is it really necessary. What features necessary to be added through this project? How this features can be visualized ( I mean live examples ) Project has been mentioned at :- 1.https://bugzilla.wikimedia.org/show_bug.cgi?id=43616 2.https://bugzilla.wikimedia.org/show_bug.cgi?id=54221<https://bugzilla.wikimedia.org/show_bug.cgi?id=54221#c0> apsdehal -- Amanpreet Singh, IIT Roorkee

1 0

Re: [Wikitech-l] Monthly point releases
by Mark A. Hershberger 04 Feb '14

04 Feb '14

Mz writes: > I received this message twice. Ten-four! My apologies to you and the list. I re-sent it because I saw it on mediawiki-l but not on wikitech-l. > Can you please create a 2014 timeline of expected releases? Or at least > the first half of 2014? Yes. I'll do that this week, maybe even tonight. Mark.

1 0

Monthly point releases
by Mark A. Hershberger 04 Feb '14

04 Feb '14

Subject: Monthly point releases Based on the issues raised during a meeting we had at the Architecture Summit a couple of weeks ago, those of us involved in MediaWiki release management have decided to introduce a monthly point-release cycle. On the last Thursday of every month we'll collect fixes that have been made and release them for download. We plan to continue to use the "Known Issues" subpage[1] to drive the issues that are incorporated into the release. This means that if you have an issue that you think should be addressed before the next major release, you can add it to the "Known Issues" page. We'll review it and, if we agree that it is an appropriate issue for a point release, then we'll try to get it resolved. Of course, this is a community-driven effort, so issues that have working code attached are more likely to be resolved in a point release than requests without code. If you cannot provide patches, that doesn't mean that your issue won't be fixed. Instead, you can help us find someone to fix it and further help by testing any fixes provided. We hope that this will mean a more usable MediaWiki. Thanks, Mark. [1] https://www.mediawiki.org/wiki/MediaWiki_1.22/Known_issues

4 3

Please update for the latest security patch
by Chris Steipp 04 Feb '14

04 Feb '14

Hi lists, If you haven't patched with the last security release, or know of a wiki that hasn't patched yet, please do so immediately. An exploit was released on the full disclosure mailing list over the weekend[1] that targets the vulnerability in the PdfHandler extension. If you're not able to patch for some reason, you may be able to work around the issue: * If you have never allowed .djvu files to be uploaded, but you do allow pdf files, you can simply disable the PdfHandler extension (typically by remove the include in your LocalSettings.php). * If you have any .djvu files saved on your wiki, then there is no workaround-- you need to apply the security patch to MediaWiki core. If anyone is running an unsupported branch of MediaWiki (1.20 was recently EOL'ed), and needs help creating a patch for their instance, I'm happy to try and work with you to get the vulnerability closed. Contact me off list, or on irc. [1] - http://seclists.org/fulldisclosure/2014/Feb/6

1 0

Bugzilla Weekly Report
by reporter 03 Feb '14

03 Feb '14

MediaWiki Bugzilla Report for January 27, 2014 - February 03, 2014 Status changes this week Reports changed/set to UNCONFIRMED: 8 Reports changed/set to NEW : 19 Reports changed/set to ASSIGNED : 17 Reports changed/set to REOPENED : 8 Reports changed/set to PATCH_TO_RE: 82 Reports changed/set to RESOLVED : 245 Reports changed/set to VERIFIED : 5 Total reports still open : 13803 Total bugs still open : 8037 Total non-lowest prio. bugs still open: 7830 Total enhancements still open : 5766 Reports created this week: 297 Resolutions for the week: Reports marked FIXED : 180 Reports marked DUPLICATE : 22 Reports marked INVALID : 18 Reports marked WORKSFORME: 14 Reports marked WONTFIX : 9 Specific Product/Component Resolutions & User Metrics Created reports per component MediaWiki extensions Flow 34 VisualEditor Editing Tools 15 MediaWiki extensions MobileFrontend 11 VisualEditor General 11 MediaWiki Skin and page rendering 10 Created reports per product MediaWiki extensions 131 MediaWiki 60 Wikimedia 35 VisualEditor 32 Wikipedia App 10 Top 5 bug report closers ebernhardson [AT] wikimedia.or15 neverett+bugzilla [AT] wikimed15 matma.rex [AT] gmail.com 13 jrobson [AT] wikimedia.org 10 umherirrender_de.wp [AT] web.d9 Most urgent open issues Product | Component | BugID | Priority | LastChange | Assignee | Summary -------------------------------------------------------------- Analytics | Tech communit | 57038 | Highest | 2013-12-23 | acs[AT]bitergia.com | Metrics about contributors with +2 pe MediaWiki ext | Diff | 58274 | Highest | 2014-01-22 | wikibugs-l[AT]lists. | Implement an order-aware MapDiffer MediaWiki ext | Echo | 53569 | Highest | 2014-02-02 | wikibugs-l[AT]lists. | [Regression] Echo: Sending 2 e-mails MediaWiki ext | Flow | 58016 | Highest | 2014-01-27 | wikibugs-l[AT]lists. | Flow: Suppression redacts the wrong u MediaWiki ext | Translate | 60306 | Highest | 2014-01-29 | ori[AT]wikimedia.org | TypeError: mw.uls is undefined on [[m MediaWiki ext | WikidataRepo | 58166 | Highest | 2013-12-09 | wikidata-bugs[AT]lis | label/description uniqueness constrai MediaWiki ext | WikidataRepo | 57918 | Highest | 2014-01-13 | wikidata-bugs[AT]lis | show diffs for sorting changes MediaWiki ext | WikidataRepo | 52385 | Highest | 2014-01-16 | wikidata-bugs[AT]lis | Query by one property and one value ( MediaWiki ext | WikidataRepo | 60127 | Highest | 2014-01-17 | wikidata-bugs[AT]lis | Implement DB schema for query indexes VisualEditor | Editing Tools | 50768 | Highest | 2014-01-22 | rmoen[AT]wikimedia.o | VisualEditor: Better reference UI for VisualEditor | MediaWiki int | 48429 | Highest | 2014-01-21 | krinklemail[AT]gmail | VisualEditor: Support editing of sect Wikimedia | Apache config | 31369 | Highest | 2014-01-20 | bugzilla+org.wikimed | Non-canonical HTTPS URLs quietly redi Wikimedia | General/Unkno | 49189 | Highest | 2014-01-16 | springle[AT]wikimedi | New fields: ar_id, el_id. Wikimedia | General/Unkno | 60710 | Highest | 2014-02-02 | wikibugs-l[AT]lists. | multiversion/getMWVersion prints vers Wikimedia | Mailing lists | 60215 | Highest | 2014-01-30 | wikibugs-l[AT]lists. | Mails to any wikimedia.org account/li Wikimedia Lab | Infrastructur | 48501 | Highest | 2014-01-23 | greg[AT]wikimedia.or | beta: Get SSL certificates for *.{pro

1 0

Tor exemption process (was: Re: Jake requests enabling access and edit access to Wikipedia via TOR)
by Erik Moeller 02 Feb '14

02 Feb '14

On Mon, Jan 13, 2014 at 9:10 AM, Chris Steipp <csteipp(a)wikimedia.org> wrote: >> To satisfy Applebaum's request, there needs to be a mechanism whereby >> someone can edit even if *all of their communications with Wikipedia, >> including the initial contact* are coming over Tor or equivalent. >> Blinded, costly-to-create handles (minted by Wikipedia itself) are one >> possible way to achieve that; if there are concrete reasons why that >> will not work for Wikipedia, the people designing these schemes would >> like to know about them. > This should be possible, according to https://meta.wikimedia.org/wiki/NOP, > which Nemo also posted. The user sends an email to the stewards (using tor > to access email service of their choice). Account is created, and user can > edit Wikimedia wikis. Or is there still a step that is missing? I tested the existing process by creating a new riseup.net email account via Tor, then requesting account creation and a global exemption via stewards(a)wikimedia.org. My account creation request was granted, but for exemption purposes, I was requested to go through the process for any specific wiki I want to edit. In fact, the account was created on Meta, but not exempted there. The reason I gave is as follows: "My reason for editing through Tor is that I would like to write about sensitive issues (e.g. government surveillance practices) and prefer not to be identified when doing so. I have some prior editing experience, but would rather not disclose further information about it to avoid any correlation of identities." This seems like a valid reason for a global exemption to me, so I'm not sure the current global policy is sufficient. Erik -- Erik Möller VP of Engineering and Product Development, Wikimedia Foundation

11 18

Jump to page:

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