Wikitech-l August 2018

wikitech-l@lists.wikimedia.org

101 participants
92 discussions

Remove 'jquery.expandableField ' module without deprecation
by Krinkle 17 Aug '18

17 Aug '18

Hi, The 'jquery.expandableField' created in 2011 for use by the Vector skin (back when skins were still part of core). More specifically, it was part of an experimental option brought in via the Vector *extension*. It was never enabled by default and the option was removed in 2013. [1] The underlying plugin was never removed and remained to this day, despite being unmaintained and having known defects. [2] It is not used anywhere in Wikimedia Git, nor anywhere else indexed by MediaWiki Codesearch, [3] and also not used in any site script or user script (mwgrep). Amazing! Based on our policy for PHP, [4] I'm announcing here that the module will be removed in MediaWiki 1.32. Patch: https://gerrit.wikimedia.org/r/#/c/mediawiki/core/+/453454/ -- Timo [1] https://gerrit.wikimedia.org/r/#/c/mediawiki/extensions/Vector/+/84195/ [2] https://phabricator.wikimedia.org/T29647 , https://phabricator.wikimedia.org/T48515 [3] https://codesearch.wmflabs.org/search/?q=jquery.expandableField [4] https://www.mediawiki.org/wiki/Deprecation_policy

1 0

Tidy removed on all Wikimedia wikis (final update)
by Subramanya Sastry 17 Aug '18

17 Aug '18

Hello everyone, On 6th July 2017, we made an announcement [1] about our plans to replace Tidy with RemexHtml on the Wikimedia cluster. On 5th July 2018, we made the final switchover from Tidy [2]. For those of you interested, we published a blog post [3] documenting the process and steps in this project. What next? ---------- RemexHtml is the default in MediaWiki since 1.31. We are in the process of removing all traces of Tidy from Wikimedia's configuration files and from MediaWiki itself. We'll keep the ParserMigration extension enabled in its current form for another couple of months. After this period, the ParserMigration extension will be disabled completely alongwith all associated Tidy configuration. It will be re-purposed at a later time as required to compare impacts of other parser changes. We haven't figured out the timeline yet, but at some point in the coming weeks, we'll disable most of the high-priority linter categories that only make sense in the context of replacing Tidy. If you have any thoughts about retaining or dropping these categories, please leave a note on mw:Help_talk:Extension:Linter [4]. Thanks! ------- As noted in the blog post [3], this was a collaborative effort between the several teams at the Wikimedia Foundation and volunteer editing communities on various wikis. Everyone involved played important and specific roles in getting us to this important milestone. An active embrace by various wikis of this effort has let the Foundation make this much-needed and important upgrade of a key piece of our platform. In that context, I want to take this opportunity to specifically name and thank some of these individuals. Tim Starling, C.Scott Ananian, Kunal Mehta, Arlo Breault, and yours truly did all the technical work in core, Parsoid, and the extensions. Erica Litrenta and Sherry Snyder helped develop the community engagement plan with various wikis and specific editors. Sherry, in particular helped a lot in the final months as we were trying to get more wikis to fix pages. James Forrester helped review and provide feedback at various stages, especially with the phased deployment. A number of other developers and staff were involved in review, feedback, during RFC discussions, and in helping with fixing templates where I couldn't do so myself. Here is a subset of users across several wikis that I had an opportunity to interact with and observe who helped in various ways: developing bots and gadgets, writing help pages, asking clarification questions, providing feedback, reporting bugs on wiki and Phabricator, and fixing lots of pages and templates on their home and other wikis. User:Daimano Eaytoy, User:Sakretsu, User:Anamalocaris, User:Izno, User:Lsj, User:xaosflux, User:PerfektesChaos, User:Lómelinde, User:Ikhitron, User:星耀晨曦, User:Deryck Chan, User:Sunpriat, User:Stryn, User:MawaruNeko, User:NicoV, User:Bdijkstra, User:Skalman, User:Shakespearefan00, User:Billinghurst, User:MarcoSwart, User:Mackensen, User:Andriy.v, User:Jonesey95, User:TheDJ, and the anonymous wiki user whoever you are. :-) Obviously, there were a number of others users involved in this effort. Please feel free to raise your hand or recognize other's contributions on this thread! My thanks to you all! Subbu. 1. https://lists.wikimedia.org/pipermail/wikitech-ambassadors/2017-July/001625… 2. https://phabricator.wikimedia.org/T175706#4399641 3. https://blog.wikimedia.org/2018/07/09/tidy-html5-replacement/ 4. https://www.mediawiki.org/wiki/Help_talk:Extension:Linter

3 2

Re: [Wikitech-l] Sensitive IRC bots - be careful out there!
by Daniel Zahn 16 Aug '18

16 Aug '18

Hey Jon, you should be unbanned. I asked in #freenode and they removed it. <@Unit193> mutante: I've removed it at this point. -- Daniel Zahn <dzahn(a)wikimedia.org> Operations Engineer

1 1

2018-08-15 Scrum of Scrums meeting notes
by Grace Gellerman 16 Aug '18

16 Aug '18

https://www.mediawiki.org/wiki/Scrum_of_scrums/2018-08-15 =2018-08-15= Yesterday was WMF holiday, though a few teams worked and entered updates: == Callouts == * Fundraising campaigns https://meta.wikimedia.org/wiki/CentralNotice/Calendar * OOUI v0.28.0 released, minor release with breaking changes https://phabricator.wikimedia.org/diffusion/GOJU/browse/master/History.md;v… *** New OOUI “Tutorials” section https://doc.wikimedia.org/oojs-ui/master/demos/tutorials/index.html – thanks GSOC student Hagar Shilo! *** Possible breakages limited only to removal of long-time deprecated icons, please update your icon references if you haven't yet. == Audiences == === Contributors === ==== Community Tech ==== * Blocked by: * Blocking: * Updates: ** ==== Anti-Harassment Tools ==== * Blocked by: * Blocking: * Updates: ** ==== Editing ==== * Blocked by: * Blocking: ** Updates: ** ==== Growth ==== * Blocked by: * Blocking: * Updates: ** ==== Language ==== * Blocked by: * Blocking: * Updates: ** === Readers === ==== iOS native app ==== * Blocked by: - * Blocking: * Updates: **6.0 still in beta ( https://phabricator.wikimedia.org/tag/ios-app-v6.0-walrus-on-a-unicycle/), working on 6.0.1 ( https://phabricator.wikimedia.org/tag/ios-app-v6.0.1-walrus-on-a-golf-cart/) ==== Android native app ==== * Blocked by: * Blocking: * Updates: ** ==== Readers Web ==== * Blocked by: * Blocking: * Updates: ** Mobile website (MinervaNeue / MobileFrontend): *** Invest in the MobileFrontend & MinervaNeue frontend architecture: T199452 T188261 T197133 *** Page issues UI and instrumentation: T201124 T191528 T197932 T191532 *** Other fixes and hygiene: T193172 T173527 T197931 T197497 T198947 T201131 T140804 ** Desktop website (Popups): *** SVG optimization (thanks Volker!) T185596 *** Replace deprecated jQuery dependency T198579 ** WikidataPageBanner *** Only move/restyle subtitle for pages where banner is present T199855 ** PDF rendering (Proton): *** Improve Chromium halt behavior and resource management T181623 T181623 ==== Readers Infrastructure ==== * Blocked by: * Blocking: * Updates: ** Maps: *** Upgrade of node-mapnik deployed successfully to Beta Cluster *** Planning production upgrade to Debian Stretch *** Working on a method for invalidating an area of map tiles ** MCS announcement for Android app multi-language features released: up from Aug 9th until Aug 16th T191640 ** Continuing work on mobile-html endpoint improvements (see open subtasks of T177433) ==== Multimedia ==== * Updates ** Job to get additional search data from wikidata in progress ** search prototyping continues ** design continues for adding structured statements for artwork ==== Parsing ==== * Blocked by: * Blocking: * Updates: === Audiences Design === ==== UI Standardization ==== * Blocked by: * Blocking: * Updates: ** OOUI v0.28.0 released, breaking change release *** Including new OOUI “Tutorials” section https://doc.wikimedia.org/oojs-ui/master/demos/tutorials/index.html – thanks GSOC student Hagar Shilo! *** Possible breakages limited only to removal of long-time deprecated icons, please consider updating your icon pack references if you haven't done so in the deprecating phase. ** Finished SVG optimization in Popups, all major Foundation products optimized! https://phabricator.wikimedia.org/T185596 ** Style Guide Imagery work https://phabricator.wikimedia.org/T194686 == Technology == === Analytics === * Blocked by: * Blocking: * Updates: ** === Cloud Services === * Blocked by: * Blocking: * Updates: ** === Core Platform === * Blocked by: * Blocking: * Updates: ** Design work for T194697 "multiblocks" ** Platform Evolution stakeholder meetings and planning for Wikimedia Technical Conference ** Gathering input from non-Wikimedia MediaWiki community at https://www.mediawiki.org/wiki/MediaWiki_Stakeholders%27_Group/TechConf_Inp… === Fundraising Tech === * Blocked by: * Blocking: * Updates: ** === Performance === * Blocked by: ** * Blocking: ** * Updates: ** === Release Engineering === * Blocked by: * Blocking: * Updates: ** === Research === * Blocked by: * Blocking: * Updates: === Scoring Platform === * Blocked by: * Blocking: * Updates: === Search Platform === * Blocked by: * Blocking: * Updates: ** === Security === * Blocked by: * Blocking: * Updates: ** === Site Reliability Engineering === * Blocked by: * Blocking: * Updates: ** == Wikidata == * Blocked by: * Blocking: * Updates: ** == German Technical Wishlist == * Blocked by: * Blocking: * Updates: ** == Multi-Content Revisions == * Blocked by: * Blocking: * Updates: ** populateContentTables.php now running simultaneously on s1, s2, s3, s5, s6, s7 (T183488) *** anticipated to run for 2 more weeks ** progress continues on phase 2 (file caption support) development tasks == SoS Meeting Bookkeeping == * Updates: **

1 0

introduction
by Jack Gleeson 16 Aug '18

16 Aug '18

Hello Awah Nadege Tayebatu! I would recommend that you look here to get started https://www.mediawiki.org/wiki/How_to_become_a_MediaWiki_hacker Jack On 16 August 2018 at 12:09, Nadege Awah <awahnadege02(a)gmail.com> wrote: > Dear sir/madame; > > I am Awah Nadege Tayebatu, female and a Cameroonian. I am an Applied > Geology student of the University of Buea, Cameroon. I will love to > contribute code to MediaWiki and so will appreciate some guide on how to > start contributing and some learning resources i can use as a beginner. > > Thank you. > _______________________________________________ > Wikitech-l mailing list > Wikitech-l(a)lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikitech-l

2 1

How to do HTML in a Wiki Page
by David Whitten 16 Aug '18

16 Aug '18

I have a program that generates HTML, complete with anchors and links that refer to them. (some of the anchor links cross files) I have not successfully put "<A>" tags into my wiki page. The <H1> etc markers with "=" generate them, but I want to put in some of my own. I don't want to break any existing anchors either. I hope to use the maintenance scripts to convert the HTML pages into WIKI pages, and I understand that I will essentially be using only the contents of the <BODY> tags to be the body of the wiki page, as the <HEAD> and <HTML> tags will be part of the page generated by the wiki. Does anyone have any guidance or web pages I should read? Thank you, David 713-870-3834

2 1

Re: [Wikitech-l] My Phabricator account has been disabled
by Yaron Koren 16 Aug '18

16 Aug '18

Nuria Ruiz <nuria(a)wikimedia.org> wrote: > The CoC will prioritize the safety of the minority over the comfort of the > majority. This is an odd thing to say, in this context. I don't believe anyone's safety is endangered by hearing the phrase in question, so it seems like just an issue of comfort on both sides. And who are the minority and majority here? > The way the bug was closed might be incorrect (I personally as an engineer > agree that closing it shows little understanding of how technical teams do > track bugs in phab, some improvements are in order here for sure) but the > harsh interaction is just one out of many that have been out of line for > while. This seems like the current argument - that it's not really about the use of a phrase, it's about an alleged pattern of behavior by MZMcBride. What this pattern is I don't know - the one example that was brought up was a blog post he wrote six years ago, which caused someone else to say something mean in the comments. (!) As others have pointed out, there's a lack of transparency here. -Yaron

21 38

My Phabricator account has been disabled
by MZMcBride 15 Aug '18

15 Aug '18

Hi. My Phabricator account has been disabled. I don't seem to have any e-mail about this action, so I'm mostly just curious who did it and why. If there's a log entry somewhere, that would be nice, but I don't know how transparent Phabricator or its admins are. I suppose it would also be nice to know if the person ever plans on undoing this unexplained disablement. I have over 56,000 unread e-mails in my "Phabricator" folder, so if I've overlooked an explanatory e-mail, please let me know! In the meantime, I guess I'll just, uhh, log out to view Phabricator. MZMcBride

34 91

C-team Statement on the Code of Conduct
by Victoria Coleman 15 Aug '18

15 Aug '18

Hello everyone, The executive leadership team, on behalf of the Foundation, would like to issue a statement of unequivocal support for the Code of Conduct[1] and the community-led Code of Conduct Committee. We believe that the development and implementation of the Code are vital in ensuring the healthy functioning of our technical communities and spaces. The Code of Conduct was created to address obstacles and occasionally very problematic personal communications that limit participation and cause real harm to community members and staff. In engaging in this work we are setting the tone for the ways we collaborate in tech. We are saying that treating others badly is not welcome in our communities. And we are joining an important movement in the tech industry to address these problems in a way that supports self-governance consistent with our values. This initiative is critical in continuing the amazing work of our projects and ensuring that they continue to flourish in delivering on the critical vision of being the essential infrastructure of free knowledge now and forever. Toby, Maggie, Eileen, Heather, Lisa, Katherine, Jaime, Joady, and Victoria https://www.mediawiki.org/wiki/Code_of_Conduct <https://www.mediawiki.org/wiki/Code_of_Conduct>

5 4

ForkableMaintenance: thoughts and help with tests/code coverage
by Brion Vibber 14 Aug '18

14 Aug '18

Hey all! While working on some maintenance scripts for TimedMediaHandler I've been trying to make it easier to do scripts that use multiple parallel processes to run through a large input set faster. My proposal is a ForkableMaintenance class, with an underlying QueueingForkController which is a refactoring of the OrderedStreamingForkController used by (at least) some CirrusSearch maintenance scripts. Patch in progress: https://gerrit.wikimedia.org/r/#/c/mediawiki/core/+/451099/ The expected use case is a relatively long loop of reading input data interleaved with running CPU-intensive or DB-intensive jobs, where the individual jobs are independent and order of input is not strongly coupled. (Ordering of _running_ of items on the child processes is not guaranteed, but the order of result processing is guaranteed to be in the same order as input, making output across runs predictable for idempotent processing.) A simple ForkableMaintenance script might look like: class Foo extends ForkableMaintenance { // Handle any input on the parent thread, and // pass any data as JSON-serializable form into // the queue() method, where it gets funneled into // a child process. public function loop() { for ( $i = 0; $i < 1000; $i++) { $this->queue( $i ); } } // On the child process, receives the queued value // via JSON encode/decode. Here it's a number. public function work( $count ) { return str_repeat( '*', $count ); } // On the parent thread, receives the work() return value // via JSON encode/decode. Here it's a string. public function result( $data ) { $this->output( $data . "\n" ); } } Because data is serialized as JSON and sent over a pipe, you can't send live objects like Titles or Pages or Files, but you can send arrays or associative arrays with fairly complex data. There is a little per-job overhead and multiple threads can cause more contention on the database server etc, but it scales well on the subtitle format conversion script I'm testing with, which is a little DB loading and some CPU work. On an 8-core/16-thread test server: threads runtime (s) speedup 0 320 n/a 1 324 0.987654321 2 183 1.74863388 4 105 3.047619048 8 66 4.848484848 16 58 5.517241379 I've added a phpunit test case for OrderedStreamingForkController to make sure I don't regress something used by other teams, but noticed a couple problems with using this fork stuff in the test runners. First, doing pcntl_fork() inside a phpunit test case has some potential side effects, since there's a lot of tear-down work done in destructors even if you call exit() after processing completes. As a workaround, when I'm having the child procs send a SIGKILL to themselves to terminate immediately without running test-case destructors. Second, probably related to that I'm seeing a failure in the code coverage calculations -- it's seeing some increased coverage on the parent process at least but seems to think it's returning a non-zero exit code somewhere, which marks the whole operation as a failure: https://integration.wikimedia.org/ci/job/mediawiki-phpunit-coverage-patch-d… Worst case, can probably exclude these from some automated tests but that always seems like a bad idea. :D If anybody else is using, or thinking about using, ForkController and its friends and wants to help polish this up, give a shout! -- brion

4 8

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

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 August 2018