Wikitech-l April 2017

wikitech-l@lists.wikimedia.org

81 participants
87 discussions

MediaWiki Language Extension Bundle 2017.04 release
by Kartik Mistry 28 Apr '17

28 Apr '17

Hello all, I would like to announce the release of MediaWiki Language Extension Bundle 2017.04. This bundle is The bundle is compatible with MediaWiki 1.27 and 1.28 or above and requires PHP 5.5.9 or above. Next MLEB is expected to be released in 3 months. If there are major changes or important bug fixes, we will do intermediate release. Please give us your feedback at [[Talk:MLEB|https://www.mediawiki.org/wiki/Talk:MLEB]]. * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2017.04.tar… * sha256sum: 4207398d7ed3ea9c793f35f88e75f29672b33aee4d0baf01afc869517c629c65 Quick links: * Installation instructions are at: https://www.mediawiki.org/wiki/MLEB * Announcements of new releases will be posted to a mailing list: https://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n * Report bugs to: https://phabricator.wikimedia.org/ * Talk with us at: #mediawiki-i18n @ Freenode Release notes for each extension are below. -- Kartik Mistry == Highlights and upgrade notes == == Babel == * TTO fixed disappearing language names on Category: and File: pages. == CLDR == * Reedy updated to CLDR 31. == CleanChanges, LocalisationUpdate == * Localisation updates only. == Translate == * Bartosz Dziewoński fixed "Mark as reviewed" tooltip positioning. * David Causse added support for Elastic5, Multi-DC for TTMServices, freezing writes. * Federico Leva fixed import of the new translations in Special:ImportTranslations. * Geoffrey Mon added insertables suggester class for $1, $2 and allow multiple suggesters. * MarcoAurelio modified log message to match with all other logs listed in Special:Log. * Niklas Laxström added support to allow moving all pages for translation admins (translate-manage). * TTO updated translator-stats to account for expiring user groups. * datguy added confirmation box in Special:ManageTranslatorSandbox when approving or rejecting a translator. (T60706) == UniversalLanguageSelector == * Bartosz Dziewoński fixed language change tooltip position. (T161203) * Niklas Laxström added link to Compact Language Links info page in the beta feature description. * Niklas Laxström fixed broken site picks feature for Compact Language Links. (T157344) === Fonts === * Kartik Mistry added Sundanese (su) font. (T162221) === Input methods === * Amir Aharoni fixed name of Arabic keyboard. * Amir Aharoni and Felix Nartey added keyboard for Ga language. * Amir Aharoni added Akan keyboard also for Twi language. * fgaim added new IMEs for Eritrean languages: Tigrinya (ti), Tigre (tig), Blin (byn). * WikiDiscoverer fixed autonym for Gõychi Konknni (gom) language. -- Kartik Mistry/કાર્તિક મિસ્ત્રી | IRC: kart_ {kartikm, 0x1f1f}.wordpress.com

1 0

Sitelink removal in Wikidata
by Amir Ladsgroup 28 Apr '17

28 Apr '17

Hey, One common form of vandalism in Wikidata is removing sitelinks (we already have an abuse filter flagging them). One of my friends in Persian Wikipedia (who is not a wikidata editor and only cares about Persian Wikipedia) asked me to write a tool that lists all Persian Wikipedia sitelink removals. So I wrote something small and fast but it's usable for any wiki. For example English Wikipedia: http://tools.wmflabs.org/dexbot/tools/deleted_sitelinks.php?wiki=enwiki It's slow due to nature of the database query but once it responds, you might find good things to revert. Since this is the most useful for Wikipedia editors who don't want to patrol Wikidata (in that case, this query <https://www.wikidata.org/w/index.php?namespace=&tagfilter=new+editor+removi…> is the most useful) I'm reaching to wider audiences. Sorry for spamming. HTH Best

5 12

Community Tech team seeking back-end developer for anti-harassment tools
by Ryan Kaldari 28 Apr '17

28 Apr '17

Sorry for the spam, but the Community Tech team at the WMF is currently looking for an experienced back-end developer for the anti-harassment tools team (a sub-team of Community Tech). To read about the sort of work that team will be doing, see https://meta.wikimedia.org/wiki/Community_health_initiative#Anti-Harassment…. We would really, really love to find a developer who is already familiar with Wikipedia and the workflows of the community. If this sounds interesting to you, please submit a resume and cover letter at https://boards.greenhouse.io/wikimedia/jobs/546212?gh_src=lis07f1#.WQKV9cm1… .

1 0

1.29 branched, master is now 1.30
by Chad 27 Apr '17

27 Apr '17

Hi, What it says in the subject :) I've made the REL1_29 branch from master (as of 273eea7357c546d1a1aafd73320e10e8ddac79eb) and have bumped the version to 1.29.0-rc.0 (from alpha). All extensions, skins and vendor have been branched as well. I've just landed the change to master that bumps it to 1.30.0-rc.0. Let the backports begin! (I want to be generous this time too, so bring 'em at me) -Chad

1 0

2017-04-26 Scrum of Scrums meeting notes
by Grace Gellerman 26 Apr '17

26 Apr '17

https://www.mediawiki.org/wiki/Scrum_of_scrums/2017-04-26 *= 2017-04-26 = * contact: https://www.mediawiki.org/wiki/Wikimedia_Engineering == Call outs:== * Datacenter switch back Wednesday, May 3rd 2017 14:00 UTC (user visible, requires read-only mode) ** https://wikitech.wikimedia.org/wiki/Switch_Datacenter * RelEng/Ops: Reading Web needs your help! Config is being ignored and shipping feature that communities have explicitly asked to be disabled and we don't understand why. https://phabricator.wikimedia.org/T163114 == Product == === Reading === ==== Web ==== * Mostly bug fixing and improving code quality for pending Page previews launch * Need help from RelEng/Ops to address `Regression: Fix config to disable related pages where it's not wanted( https://phabricator.wikimedia.org/T163114)`. Config is being ignored and shipping feature that communities have explicitly asked to be disabled and we don't understand why. ==== iOS ==== * Last Week ** Continued work on 5.4.1 - https://phabricator.wikimedia.org/project/view/2600/ *** Regression testing, new public beta *** Crash fixes & performance enhancements ** 5.5 - https://phabricator.wikimedia.org/project/view/2602/ *** Places (UserTesting feedback) *** Article footer content rendered in HTML/CSS rather than native views * This Week ** Submit 5.4.1 to the App Store ** Continue work on 5.5 *** Updates to Places from user feedback ==== Android ==== * Beta released last week containing Wikidata title description editing expanded to many more languages, as well as various offline UX improvements ** Hotfix release Friday (4/21), promoted to prod yesterday: https://lists.wikimedia.org/pipermail/mobile-l/2017-April/010503.html * Planning is underway for implementing offline ZIM compilations (Q4 goal) ** https://phabricator.wikimedia.org/project/view/2723/ * Continuing work on cross-platform consolidation of CSS & JS * Current release board: https://phabricator.wikimedia.org/project/view/2352/ ==== Reading Infrastructure ==== * ORES: working on api.php abuse + DB size issues, hoping to reenable after data center switchback * librarized https://www.mediawiki.org/wiki/Testing-access-wrapper * MCS: stop annoucement of past survey, fix handling of links in section titles === Editing === ==== UI Standardization ==== * This week: ** Continued work to provide WikimediaUI Base variables in core https://phabricator.wikimedia.org/T123359 * Updates: ** OOjs UI: *** Release of v0.21.2 with 11 UI/a11y improvements https://phabricator.wikimedia.org/diffusion/GOJU/browse/master/History.md – among those: **** MediaWiki theme: Full WCAG level AA contrast support of widgets accomplished **** MediaWiki theme: Fix IE 7 oversized buttons **** MediaWiki theme: Improve SearchWidget design **** Set ARIA `role=combobox` on DropdownWidget and LookupElement too (Bartosz Dziewoński) **** Set `aria-owns` for everything with a dropdown list (ARIA `role=combobox`) (Bartosz Dziewoński) ==== Parsing ==== * Parsoid: Audio / video support in place -- we plan to deploy today. * Linter: Improved documentation and guidance for fixing linter errors @ https://www.mediawiki.org/wiki/Help:Extension:Linter * Tidy replacement: Updated documentation @ https://www.mediawiki.org/wiki/Parsing/Replacing_Tidy/FAQ * Language Variant tweaks in preprocessor: Fixups required documented @ https://www.mediawiki.org/wiki/Parsoid/Language_conversion/Preprocessor_fix… ... an editor has been diligently fixing them. We plan to make an announcement about this upcoming change soon and then merge the core patch ( https://gerrit.wikimedia.org/r/#/c/333997/ ) after that. ==== Language ==== * CX reenabled; We're watching logs and ready to disable if needed. Incident report in progress. ** https://phabricator.wikimedia.org/T163344 * OOjs UI migration work in progress. ==== Collaboration ==== * RCFilters: Optimization so if we know a query will return 0 results, we won't do the query at all. Some of these no-result queries have extremely poor performance. * Working on GuidedTour to make people aware of RCFilters beta feature * Working on next generation of RCFilters, including namespace and user filters, saved settings, and more sophisticated time filtering. * DId a deploy Monday to enable RCFilters on English Wikipedia, plus almost all non-ORES wikis. Some issues with preferences, but these have been partly tracked down. * Other bug fixes === Community Tech === No blockers * Rollling out Cookie Blocking to all wikis next Monday * Further polish work on CodeMirror extension (syntax highlighting) * Getting community feedback on LoginNotify extension (currently on Beta Cluster for testing) * User rights expiration is live on all wikis == Technology == === Research === * Reader research surveys are most likely to go out next week ** We will be running these surveys in 14 languages with the help of Reading team ** https://meta.wikimedia.org/wiki/Research_talk:Characterizing_Wikipedia_Read… ** https://phabricator.wikimedia.org/T151835 == Wikidata == * Focusing on the Lexeme extensions UI, example: http://wikidata-lexeme.wmflabs.org/index.php/Lexeme:L2 * Had to work around a change in core that blocked undeleting Wikidata entities: https://phabricator.wikimedia.org/T163144 * Going to deploy Echo notifications when linking pages via Wikidata: https://phabricator.wikimedia.org/T110604 == German Technical Wishlist == * Planning next steps for the book referencing wish: https://phabricator.wikimedia.org/T151301 === Discovery === * No blockers * Building infrastructure for machine learning assisted ranking (aka MjoLniR) * Chinese analyzer seems to be doing well, enabling soon. Working on Hebrew analyzer. * Completed analysis of second sister wiki search A/B test: https://commons.wikimedia.org/wiki/File%3ASecond_Test_Of_Cross-wiki_Search_… * Published notes from discussion on scoring functions: https://www.mediawiki.org/wiki/User:TJones_(WMF)/Notes/Some_Thoughts_on_the… * Updated WDQS dashboard to include traffic from all SPARQL endpoints: https://discovery.wmflabs.org/wdqs/ * Updated the external search dashboard to display non-bot traffic ( https://discovery.wmflabs.org/external/, task T161932) * Portal statistics (task T128546) and translations (task T142582) were updated * Working on Wikidata search improvement * Working on Mediawiki API integration for WDQS === Analytics === * Ongoing work on EventLogging analysis support in Hadoop - Not yet finished * Ongoing work on Wikistats 2.0 data back-end - Finalizing Design * Started to define webrequest tagging project * Daily uniques are in Pivot http://bit.ly/2oZU5gt * Waiting for feedback on Wikistats 2.0 consultation * Dashiki configuration articles on meta still broken, can't fix them until the codfw-related deployment moratorium is over === TechOps === * '''Blocked''' ** None * '''Blocking''' ** None? * '''Updates''' ** Wrapping up switchover action items https://etherpad.wikimedia.org/p/codfw-switchover-AprMay2017 ** ToolsProxy incident report https://wikitech.wikimedia.org/wiki/Incident_documentation/20170419-ToolsPr… === Security === * Reviews ** WikibaseMediaInfo ** TemplateStyles === Services === * Blockers: none * Updates: ** Service-runner doesn't support node 0.1x any more *** https://github.com/wikimedia/service-runner/pull/163 === RelEng === * '''Blocked''' ** None * '''Blocking''' ** None? ** Config symlinks should be touched when they're deployed, Reading callout above https://phabricator.wikimedia.org/T126306 * '''Updates''' ** New version of scap out https://github.com/wikimedia/scap/blob/release/debian/changelog#L1 (config diffs in a basic format, env announce in IRC) ** 1.29 is coming...see wikitech email for more info === Fundraising Tech === * More Paypal Express Checkout fixes * Investigating potential extra session creation on paymentswiki * Planning Ingenico integration changeover, which will include moving a lot of functionality from MW extension to lib * Coordinating with Comms to update the WMF logo in various places: https://phabricator.wikimedia.org/T144254 * CentralNotice: Banner sequence feature is in code review https://phabricator.wikimedia.org/T144453 * CiviCRM: getting rid of the rest of our local core hacks, using upstream buildkit in CI * Found a dozen repos we can delete

1 0

Issue loading JS with ResourceLoader but not with addScript
by James Montalvo 26 Apr '17

26 Apr '17

I'm having an issue with getting ResourceLoader to properly load the Masonry library [1]. This issue was not present on MW 1.25 but is on MW 1.27. If I do the following: $out->addModules( 'ext.masonrymainpage.libs' ); // or as dependency to base $out->addModules( 'ext.masonrymainpage.base' ); Then I get the following error in my browser: Uncaught Error: Module "jquery" is not loaded. at require (load.php?debug=true&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=ciafJ7Ly:12581) at masonry.pkgd.js?c5dde:29 at masonry.pkgd.js?c5dde:39 require @ load.php?debug=true&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=ciafJ7Ly:12581 (anonymous) @ masonry.pkgd.js?c5dde:29 (anonymous) @ masonry.pkgd.js?c5dde:39 load.php?debug=true&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=ciafJ7Ly:11145 Use of "wgCategories" is deprecated. Use mw.config instead. get @ load.php?debug=true&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=ciafJ7Ly:11145 (anonymous) @ load.php?debug=true&lang=en&modules=site&only=scripts&skin=vector&version=680c78b07fb0:273 However, if I load Masonry not from the ext.masonrymainpage.libs module, but instead using OutputPage::addScript() then I have no issues: global $wgServer, $wgExtensionAssetsPath; $scriptURL = "$wgServer/$wgExtensionAssetsPath/MasonryMainPage/masonry.pkgd.js"; $out->addScript( "<script type='text/javascript' src='$scriptURL'></script>" ); $out->addModules( 'ext.masonrymainpage.base' ); Can anyone help me figure out how to do this the right way? Thanks, James [1] https://github.com/desandro/masonry

3 4

REL1_29 approaching, pencils down
by Chad 25 Apr '17

25 Apr '17

Hi, We're coming up on the month of May, which means we'll be working on a 1.29 release! As the initial step, I'd like to create a branch for REL1_29 this week barring any major objections. I'm thinking Thursday evening after we've finished this week's train. Then we'll be in the normal patch master + backport process we all know and love until we do the release (looking at May 25th). -Chad

1 0

The codfw deployment server is Naos
by Riccardo Coccioli 24 Apr '17

24 Apr '17

= TL;DR - The codfw deployment server is now Naos: naos.codfw.wmnet [1]. Its SSH fingerprints are available at [2]. - Mira is no longer a deployment server. - Naos is also the current active deployment server until May 3rd [3], [4]. - As always, please use the DNS record deployment.eqiad.wmnet to know which deployment server is the active one. = Detailed version: Few days before the datacenter switchover to codfw performed last week [3], [4], with perfect timing, the existing codfw deployment server Mira manifested hardware issues. Being Mira an old server, also out of warranty, a new deployment server in the codfw datacenter was deployed and configured. As a result, from now on, the deployment server for the codfw datacenter is Naos: naos.codfw.wmnet [1]. You can find its SSH fingerprints in [2]. As part of the datacenter switchover procedures [4], also the deployment server was switched to codfw, hence Naos is currently the active deployment server, until the switchback to eqiad as master datacenter, scheduled on May 3rd [3], [4]. The DNS entries for both deployment.eqiad.wmnet and deployment.codfw.wmnet always point to the active deployment server and should be used to verify which one is the active one. As always, a large message of the day (MOTD) is shown to alert people to not use the passive deployment server on login, and it is now shown on both Tin and Mira. I've also updated all the references to Mira that I've found on Wikitech, but please verify if you have any direct reference to it that might need to be updated. Thanks, Riccardo [1] https://wikitech.wikimedia.org/wiki/Naos [2] https://wikitech.wikimedia.org/wiki/Help:SSH_Fingerprints/naos.codfw.wmnet [3] https://blog.wikimedia.org/2017/04/18/codfw-temporary-editing-pause/ [4] https://wikitech.wikimedia.org/wiki/Switch_Datacenter -- Riccardo Coccioli Software Engineer, Technical Operations Wikimedia Foundation

1 0

Presentation Code of Conduct Committee candidates and community review
by Quim Gil 24 Apr '17

24 Apr '17

Following the process described in the Code of Conduct for Wikimedia technical spaces <https://www.mediawiki.org/wiki/Code_of_Conduct>, the Wikimedia Foundation’s Technical Collaboration team has selected five candidates to form the first Code of Conduct Committee and five candidates to become auxiliary members. Here you have their names in alphabetical order. For details about each candidate, please check https://www.mediawiki.org/wiki/Code_of_Conduct/Committee_members Committee member candidates: - Amir Sarabadani (Ladsgroup) - Lucie-Aimée Kaffee (Frimelle) - Nuria Ruiz (NRuiz-WMF) - Sébastien Santoro (Dereckson) - Tony Thomas (01tonythomas) Auxiliary member candidates: - Ariel Glenn (ArielGlenn) - Caroline Becker (Léna) - Florian Schmidt (Florianschmidtwelzow) - Huji - Matanya This list of candidates is subject to a community review period of two weeks starting today. If no major objections are presented about any candidate, they will be appointed in six weeks. You can provide feedback on these candidates, via private email to techconductcandidates(a)wikimedia.org. This feedback will be received by the Community Health <https://meta.wikimedia.org/wiki/Technical_Collaboration/Community_health> group handling this process, and will be treated with confidentiality. We want to thank all the people who has considered the possibility to support the Code of Conduct with their participation in this Committee. 77 persons have been contacted during the selection process, counting self-nominations and recommendations. From these, 21 made it to a short list of candidates confirmed and (according to our estimation) a potential good fit for the Committee. Selecting the five candidates for the Committee has been hard, as we have tried to form a diverse group that could work together effectively in the consolidation of the Code of Conduct. Selecting the five auxiliary members has been even harder, and we know that we have left out candidates who could have contributed just as much. Being the first people assuming these roles, we have tended a bit towards more technical profiles with good knowledge of our technical spaces. We believe that future renewals will offer better chances to other profiles (not so technical and/or not so Wikimedia veteran), adding a higher diversity and variety of perspectives to the mix. On Thu, Mar 9, 2017 at 12:30 PM, Quim Gil <qgil(a)wikimedia.org> wrote: > Dear Wikimedia technical community members, > > https://www.mediawiki.org/wiki/Code_of_Conduct > > The review of the Code of Conduct for Wikimedia technical spaces has been > completed and now it is time to bootstrap its first committee. The > Technical Collaboration team is looking for five candidates to form the > Committee plus five additional auxiliary members. One of them could be you > or someone you know! > > You can propose yourself as a candidate and you can recommend others > *privately* at > techconductcandidates AT wikimedia DOT org > > We want to form a very diverse list of candidates reflecting the variety > of people, activities, and spaces in the Wikimedia technical community. We > are also open to other candidates with experience in the field. Diversity > in the Committee is also a way to promote fairness and independence in > their decisions. This means that no matter who you are, where you come > from, what you work on, or for how long, you are a potential good member of > this Committee. > > The main requirements to join the Committee are a will to foster an open > and welcoming community and a commitment to making participation in > Wikimedia technical projects a respectful and harassment-free experience > for everyone. The committee will handle reports of unacceptable behavior, > will analyze the cases, and will resolve on them according to the Code of > Conduct. The Committee will also handle proposals to amend the Code of > Conduct for the purpose of increasing its efficiency. The term of this > first Committee will be one year. > > Once we have a list of 5 + 5 candidates, we will announce it here for > review. You can learn more about the Committee and its selection process at > https://www.mediawiki.org/wiki/Code_of_Conduct/Committee and you can ask > questions in the related Talk page (preferred) or here. > > You can also track the progress of this bootstrapping process at > https://www.mediawiki.org/wiki/Talk:Code_of_Conduct# > Bootstrapping_the_Code_of_Conduct_Committee > > PS: We have many technical spaces and reaching to all people potentially > interested is hard! Please help spreading this call. > > -- > Quim Gil > Engineering Community Manager @ Wikimedia Foundation > http://www.mediawiki.org/wiki/User:Qgil > -- Quim Gil Engineering Community Manager @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil

1 2

Re: [Wikitech-l] Fair use image indicated as free use?
by Fako Berkers 23 Apr '17

23 Apr '17

Hi all, Thanks for the feedback on my question. I see that the image got a different template assigned to it and now the API response is fine. I'll spread the news about that. I have one follow up question. When an image didn't get the right template/license assigned. Is there a tool/bot that people can use to correct these mistakes? For instance can a bot remove images where they aren't supposed to be? If my tool ever becomes wide spread I'd like there to be an easy way to update images like the one we saw before the weekend. Thanks a lot, Fako

1 0

← Newer
1
2
3
4
5
6
7
8
9
Older →

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 April 2017