Wikitech-l April 2017

wikitech-l@lists.wikimedia.org

81 participants
87 discussions

[MediaWiki-announce] Security Release: 1.28.1 / 1.27.2 / 1.23.16
by Chad Horohoe 07 Apr '17

07 Apr '17

Hello! I would like to announce the release of MediaWiki 1.28.1, 1.27.2 and 1.23.16! These releases fix five security issues in core and one for the extension SyntaxHighlight_GeSHi. Download links are given at the end of this email. Please note that next month is the End-Of-Life date for MediaWiki 1.23. This means that MediaWiki 1.23.16 will be the last security release for that version, barring any unforeseen issues. We would strongly encourage users of MediaWiki 1.23 to upgrade to MediaWiki 1.27, released in June 2016, or a yet newer version as soon as possible. MediaWiki 1.27 will be supported until June 2019. See <https://www.mediawiki.org/wiki/Version_lifecycle> for more information. This release also serves as a maintenance release for these branches. == Security fixes == * (T109140) (T122209) Special:UserLogin and Special:Search allow redirect to interwiki links. (CVE-2017-0363, CVE-2017-0364) * (T144845) XSS in SearchHighlighter::highlightText() when $wgAdvancedSearchHighlighting is true. (CVE-2017-0365) * (T125177) API parameters may now be marked as "sensitive" to keep their values out of the logs. (CVE-2017-0361) * (T150044) "Mark all pages visited" on the watchlist now requires a CSRF token. (CVE-2017-0362) * (T156184) Escape content model/format url parameter in message. (CVE-2017-0368) * (T151735) SVG filter evasion using default attribute values in DTD declaration. (CVE-2017-0366) * (T48143) Spam blacklist ineffective on encoded URLs inside file inclusion syntax's link parameter. (CVE-2017-0370) * (T108138) Sysops can undelete pages, although the page is protected against it. (CVE-2017-0369) The following only affects 1.27 and above and is not included in the 1.23 upgrade: * (T161453) LocalisationCache will no longer use the temporary directory in its fallback chain when trying to work out where to write the cache. (CVE-2017-0367) The following fix is for the SyntaxHighlight extension: * (T158689) Parameters injection in SyntaxHighlight results in multiple vulnerabilities. (CVE-2017-0372) == Links to all mentioned tasks == https://phabricator.wikimedia.org/T109140 https://phabricator.wikimedia.org/T122209 https://phabricator.wikimedia.org/T144845 https://phabricator.wikimedia.org/T125177 https://phabricator.wikimedia.org/T150044 https://phabricator.wikimedia.org/T156184 https://phabricator.wikimedia.org/T151735 https://phabricator.wikimedia.org/T161453 https://phabricator.wikimedia.org/T48143 https://phabricator.wikimedia.org/T108138 https://phabricator.wikimedia.org/T158689 == Release notes == Full release notes for 1.28.1: <https://www.mediawiki.org/wiki/Release_notes/1.28> Full release notes for 1.27.2: <https://www.mediawiki.org/wiki/Release_notes/1.27> Full release notes for 1.23.16: <https://www.mediawiki.org/wiki/Release_notes/1.23> For information about how to upgrade, see <https://www.mediawiki.org/wiki/Manual:Upgrading> ********************************************************************** 1.23.16 ********************************************************************** Download: https://releases.wikimedia.org/mediawiki/1.23/mediawiki-1.23.16.tar.gz Download without bundled extensions: https://releases.wikimedia.org/mediawiki/1.23/mediawiki-core-1.23.16.tar.gz Patch to previous version (1.23.15), without interface text: https://releases.wikimedia.org/mediawiki/1.23/mediawiki-1.23.16.patch.gz Interface text changes: https://releases.wikimedia.org/mediawiki/1.23/mediawiki-i18n-1.23.16.patch.… GPG signatures: https://releases.wikimedia.org/mediawiki/1.23/mediawiki-core-1.23.16.tar.gz… https://releases.wikimedia.org/mediawiki/1.23/mediawiki-1.23.16.tar.gz.sig https://releases.wikimedia.org/mediawiki/1.23/mediawiki-1.23.16.patch.gz.sig https://releases.wikimedia.org/mediawiki/1.23/mediawiki-i18n-1.23.16.patch.… Public keys: https://www.mediawiki.org/keys/keys.html ********************************************************************** 1.27.2 ********************************************************************** Download: https://releases.wikimedia.org/mediawiki/1.27/mediawiki-1.27.2.tar.gz Download without bundled extensions: https://releases.wikimedia.org/mediawiki/1.27/mediawiki-core-1.27.2.tar.gz Patch to previous version (1.27.1), without interface text: https://releases.wikimedia.org/mediawiki/1.27/mediawiki-1.27.2.patch.gz Interface text changes: https://releases.wikimedia.org/mediawiki/1.27/mediawiki-i18n-1.27.2.patch.gz GPG signatures: https://releases.wikimedia.org/mediawiki/1.27/mediawiki-core-1.27.2.tar.gz.… https://releases.wikimedia.org/mediawiki/1.27/mediawiki-1.27.2.tar.gz.sig https://releases.wikimedia.org/mediawiki/1.27/mediawiki-1.27.2.patch.gz.sig https://releases.wikimedia.org/mediawiki/1.27/mediawiki-i18n-1.27.2.patch.g… Public keys: https://www.mediawiki.org/keys/keys.html ********************************************************************** 1.28.1 ********************************************************************** Download: https://releases.wikimedia.org/mediawiki/1.28/mediawiki-1.28.1.tar.gz Download without bundled extensions: https://releases.wikimedia.org/mediawiki/1.28/mediawiki-core-1.28.1.tar.gz Patch to previous version (1.28.0), without interface text: https://releases.wikimedia.org/mediawiki/1.28/mediawiki-1.28.1.patch.gz Interface text changes: https://releases.wikimedia.org/mediawiki/1.28/mediawiki-i18n-1.28.1.patch.gz GPG signatures: https://releases.wikimedia.org/mediawiki/1.28/mediawiki-core-1.28.1.tar.gz.… https://releases.wikimedia.org/mediawiki/1.28/mediawiki-1.28.1.tar.gz.sig https://releases.wikimedia.org/mediawiki/1.28/mediawiki-1.28.1.patch.gz.sig https://releases.wikimedia.org/mediawiki/1.28/mediawiki-i18n-1.28.1.patch.g… Public keys: https://www.mediawiki.org/keys/keys.html _______________________________________________ MediaWiki announcements mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce

3 2

Update on Discovery search efforts and upcoming releases
by Deborah Tankersley 07 Apr '17

07 Apr '17

tl;dr: Search continues to expand functionality by displaying more information on the search results page Ever started searching for something on Wikipedia and wondered—*really*, is that all that there is? Does it feel like you’re somehow playing hide and seek with all the knowledge that’s out there? And...wouldn’t it be great to see articles or categories that are similar to your search query and maybe some related images or links to other languages in which to read that article? Or, maybe you just want to read and contribute to projects other than Wikipedia but need a jump start with a few short summaries from sister projects. The Discovery Search team has been testing out some really cool new features that will enable some fun and fascinating clicking—down the rabbit hole of Wikipedia.[1] But first, let’s recap what we’ve been doing recently. We've been doing tons of work creating, updating, and finessing the search back end to enhance search queries. There have been many complex things that have happened, things like: adding ascii-folding and stemming, detecting when a visitor might be typing in a language that is different than the Wikipedia that they are on, switching from tf-idf to BM25, dropping trailing question marks, and updating to ElasticSearch version 5. [2][3][4][5][6][7] Whew! We have much more planned in the coming months—machine learning with ‘learning to rank’, investigating and deploying new language analyzers, and, after exhaustive analysis, removing quotes within queries by default.[8][9][10][11] We’ll also be working closely with the new Structured Data team in their brand new work on Commons.[12][13] We also want to improve the part that our readers and editors interface with: the search results page! We started brainstorming during the late summer of 2016 on what we could do to make search results better—to easily find interesting, relevant content and to create a more intuitive viewing experience.[14] We designed and refined numerous ideas on how to improve the search results page and received lots of good feedback from the community.[15] Empowered by the feedback, we began testing starting with a display of results from the Wikimedia sister projects next to the regular search results.[16] The idea for this test was to enable discovery into other projects—projects that our visitors might not have known about—by displaying interesting results in small snippets. The sidebar display of the sister projects borrows from a similar feature in use on the Italian, Catalan and French Wikipedias. We've run two A/B tests on the sister project search results with detailed analysis and, after a bit of final touches to the code, we will release the new functionality into production on all Wikipedias near the end of April 2017. Our next A/B test will be to add additional information and related results for each search query. This will be in the form of an ‘explore similar’ link that, when someone interacts with the link, an expanded display will appear with related pages, categories and links to the article in other languages—all of which might lead to further knowledge discovery.[17] We know that not every search query will return exactly what folks were looking for, but we feel that adding links to similar, but related information would be helpful and, possibly, super interesting! We also plan on doing a few more A/B tests in the coming year: * Test a new display that will show the pronunciation of a word with its definition and part of speech—all from existing data in Wiktionary. Initially this will be in English only. * Test placing a small image (from the article) next to each search result that is displayed on the page. * Test an additional future using a new auto completion metadata display in the search box that is located on the top right of most pages in Wikipedia, similar to what happens on the Wikipedia.org portal.[18] For the more technical minded, there is a way to test out these new features in your own browser. To display the sister project search results, it will require a bit of URL manipulation; but for the explore similar and Wiktionary widget, you can modify your common.js file to test an early version of the features. Detailed information is available on MediaWiki.org.[19] Once the testing, analysis and feedback cycle is done for each new feature, we’d like to slowly implement them into production on all Wikipedias throughout the rest of the year. We’re really hoping that these enhancements to how search works will further the usefulness of search and make our readers and editors more productive. Cheers from the Discovery Search team! [1] https://xkcd.com/214/ [2] https://www.mediawiki.org/wiki/User:TJones_(WMF)/Notes/R e-Ordering_Stemming_and_Ascii-Folding_on_English_Wikipedia [3] https://blog.wikimedia.org/2016/07/27/wikipedia-language-search/ [4] https://en.wikipedia.org/wiki/Tf%E2%80%93idf [5] https://en.wikipedia.org/wiki/Okapi_BM25 [6] https://www.mediawiki.org/wiki/User:TJones_(WMF)/Notes/Drop ping_Final_Question_Marks_in_the_Top_10_Wikipedias [7] https://phabricator.wikimedia.org/T154501 [8] https://en.wikipedia.org/wiki/Learning_to_rank [9] https://phabricator.wikimedia.org/T154511 [10] https://commons.wikimedia.org/wiki/File:From_Zero_to_ Hero_-_Anticipating_Zero_Results_From_Query_Features,_Ignoring_Content.pdf [11] https://www.mediawiki.org/wiki/User:TJones_(WMF)/Notes/ Quotes_and_Questions [12] https://commons.wikimedia.org/wiki/Commons:Structured_data [13] https://blog.wikimedia.org/2017/01/09/sloan-foundation-structured-data/ [14] https://www.mediawiki.org/wiki/Cross-wiki_Search_Result_Improvements [15] https://www.mediawiki.org/wiki/Talk:Cross-wiki_Search_ Result_Improvements [16] https://www.mediawiki.org/wiki/Cross-wiki_Search_Result _Improvements/Testing#A.2FB_test:_Add_cross-wiki_search_ results_in_a_right_hand_sidebar [17] https://www.mediawiki.org/wiki/Cross-wiki_Search_Result _Improvements/Testing#A.2FB_test:_Add_.27explore_similar. 27_pages_and_categories_for_search_results [18] https://www.wikipedia.org/ [19] https://www.mediawiki.org/wiki/Cross-wiki_Search_Result _Improvements/self-guided_testing -- deb tankersley irc: debt Product Manager, Discovery Wikimedia Foundation

1 0

Question about wikidata dump bz2 file
by Trung Dinh 06 Apr '17

06 Apr '17

Hi everyone, I realized the dump file for wikidata is no longer in the format wikidatawiki-2017XXXX-pages-articles.xml.bz2 anymore.

1 0

Improvements to Phabricator Search Deployed
by Mukunda Modell 06 Apr '17

06 Apr '17

Hello Wikimedia developers! I've just deployed the latest batch of Phabricator updates. Normally I wouldn't write an announcement for routine upgrades, however, this update is different. This week's update includes notable improvements to Phabricator's global search functionality which I have been working on for the past week. *Bugs Fixed:* Several minor bugs have been resolved, most notably, longstanding bug which prevented viewing results numbered 100+ has been resolved [1]. *Better Search Results:* There have been many small improvements to search query parsing, performance & reliability in the past few weeks. A few of these are launching today but the most visible change is a significantly improved search results page with document body highlighting[2]. This feature shows a snippet of documents with the matching search terms highlighted in bold. Previously, Phabricator only displayed the title of each result with matching terms highlighted only if they appeared within the title. With today's release, the matching terms are highlighted from the body of the document as well and this takes advantage of an Elasticsearch feature[3] to accurately highlight the terms which actually lead to the result being included in the search result. *Welcome to The Future:* Some of you might be thinking that this is just too much. Such unnecessary features are just extravagant and wasteful. To that I say: why should we let advanced technologies like cascading style sheets sit idle, neglected. We can do better than a 1970s search experience. We deserve to have our search terms rendered as stylized hypertext with bold, beautiful letters and contextually accurate emphasis. We deserve modern conveniences and I don't feel the least bit guilty about that. It's the 90s[4], after all. *Upstream Status:* This new functionality has been submitted upstream for inclusion in Phabricator, however, as of today it remains in differential pending code review. The feature is likely to evolve further before finally making it into the upstream. It is a fairly large patch which adds a new "Engine Extension" infrastructure to phabricator. This foundation can be used to add various enhancements to the search results views (e.g. customized views for each object type.) This also lays the foundation for resolving https://secure.phabricator.com/T8646, although that bug doesn't really affect Wikimedia's developers because we have disabled Phabricator's integrated wiki. 1. https://phabricator.wikimedia.org/T92960 2. https://phabricator.wikimedia.org/T162284 3. https://www.elastic.co/guide/en/elasticsearch/reference/current/search-requ… 4. https://vimeo.com/29455771 That's all for now, I hope you enjoy these improvements to Phabricator search experience! Mukunda Modell Release Engineer & Phabricator Admin Wikimedia Foundation, Inc.

1 0

[MediaWiki-announce] Security pre-release announcement: 1.28.1 / 1.27.2 / 1.23.16
by Chad Horohoe 05 Apr '17

05 Apr '17

Hi, Tomorrow, April 6th we will be performing a security release of MediaWiki for all supported branches. The new versions will be 1.28.1, 1.27.2 and 1.23.16. This will resolve 9 issues in MediaWiki core, and one in a bundled extension. Have a great day, -- Chad Horohoe & Sam Reed _______________________________________________ MediaWiki announcements mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce

1 0

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

05 Apr '17

https://www.mediawiki.org/wiki/Scrum_of_scrums/2017-04-05 = 2017-04-05 = contact: https://www.mediawiki.org/wiki/Wikimedia_Engineering == Call outs == * Analytics: Planning wikistats 2.0 prototype consultation - Please share your thoughts on the UI prototype https://analytics-prototype.wmflabs.org (emails with where to share soon) * Parsoid drops node 0.10 support -- announcement and details coming this week. * ParserMigration extension now live on all wikis -- announcement and details coming next week. * Services: New version of the PDF render service still awaits checking from WMDE *** https://en.wikipedia.beta.wmflabs.org/api/rest_v1/#!/Page_content/get_page_… *** https://phabricator.wikimedia.org/T160764 * RelEng: May need Ops help deploying 3d2png via scap3 (worked on Beta Cluster), need some +2 in puppet * FR-tech's new job runner / cron complement script to replace our Jenkins instance is working like a charm. Anyone else want to use it for scheduled jobs? ** https://github.com/wikimedia/wikimedia-fundraising-process-control == Product == === Reading === ==== Web ==== * Last week: ** Reading Off-site * Next week: ** Deploy PagePreviews to Hungarian and Hebrew wikipedias. ** PagePreviews instrumentation related bugfixes. ** Improved print styles for MobileFrontend ==== Android ==== * Last week: ** Reading Off-site. ** A nasty little crash in production for logged-in users caused by a small, unexpected change to the userjs response format. () * This week / early next week: a new release to beta and production thereafter, including the following: ** A substantially better offline experience! (our Q3 goal: https://phabricator.wikimedia.org/tag/android-app-goals-2017-jan-mar-q3/) ** Wikidata description editing expanded from three languages to all except the top 10 by page views as measured in the app. * Kanban: https://phabricator.wikimedia.org/project/view/2352/ ====Reading Infrastructure==== * TemplateStyles: ** CSS sanitizer library https://gerrit.wikimedia.org/r/#/q/project:css-sanitizer ** will be taken over by MediaWiki Platform * Mobile Content Service: https://phabricator.wikimedia.org/project/view/2445/ ** Deployed: Added 13 more languages to the featured article. ==== iOS ==== * Last Week ** Reading Offsite * This week ** 5.4.1 - https://phabricator.wikimedia.org/project/view/2600/ *** Monitor crash reports, fix major issues ** 5.5 - https://phabricator.wikimedia.org/project/view/2602/ *** Places *** JavaScript consolidation with Android *** Image caching fixes ==== Community Tech ==== * Cookie blocks deployed to English Wikipedia, more wikis to follow * LoginNotify in testing on beta cluster * CodeMirror bug fixes, colour tweaks * Various improvements to the new XTools, nothing to show * No blockers === Editing === ==== Parsing ==== * ParserMigration extension has now been deployed on all wikis. You can enable it on the Editing tab of your Special:Preferences page. Clicking it will add a sidebar link called "Edit with migration tool". This opens a page for editing that shows you a side-by-side preview of the page with the default (production) parser and an experimental / proposed-migration of the parser. For example, currently, this lets you compare output with Tidy and output with RemexHTML (a PHP-only replacement for Tidy that is based on HTML5 semantics). You should also be able to directly exercise it via https://en.wikipedia.org/w/index.php?title=PAGE-TITLE&action=parsermigratio…. For example, https://en.wikipedia.org/w/index.php?title=Typhoon_Parma&action=parsermigra… shows that the page renders differently with RemexHTML ( because of https://phabricator.wikimedia.org/T161341#3129283 ). We will send out a note on mailing lists (and possibly other forums like Tech News) next week about this and about how to leverage the Linter extension and Visual Diffing results for fixing wiki pages * Filed https://phabricator.wikimedia.org/T162275 to make visual diffing output more useful for editors for fixing up pages. This can help us track progress of wikitext and template fixup and tell us when it is safe to flip the switch on Tidy. * We are continuing to work on https://www.mediawiki.org/wiki/Parsoid/Language_conversion/Preprocessor_fix… to document impact of cleanup to the preprocessor to remove some edge cases ( https://gerrit.wikimedia.org/r/#/c/333997/ ). We'll use the results of this investigation to figure out followup work. * We released Parsoid debian 0.7.0 package y'day. This release drops support for node 0.10x and requires node v4x. However, we forgot to update the dependencies in the control file which still states a >= v0.8.0 requirement. Will release a 0.7.1 deb that fixes this. * In November, we announced a deprecation of node 0.10 for Parsoid ( https://lists.wikimedia.org/pipermail/wikitech-l/2016-November/087005.html ), Going forward, node 0.10 is no longer supported in Parsoid. * Bumping service-runner in Parsoid as requested by Services team for the upcoming DC switchover this month. ==== Collaboration ==== * RCFilters beta feature went live on plwiki, ptwiki last week; next release to trwiki, fawiki, ruwiki and frwiki next week (Apr 11); then enwiki + most non-ORES wikis on Apr 24; and all remaining wikis May 9 * Working with Aaron H on figuring out ORES behavior for RCFilters for the next releases ==== Language ==== * Work on OOjs UI migration continue. == Technology == === Analytics === * Reportcard migrated to new infra - Limn is dead * new AQS metrics (historical projectcounts) have a bug - still vetting before announcing * user agent map in EventLogging replaces user agent string (fully deployed) * All hadoop workers have been reimaged to jessie - masters left (next week) * Planning wikistats 2.0 prototype consultation ( https://analytics-prototype.wmflabs.org") * Eventlogging MariaDB custom replication procedure has been updated (should avoid long delays between master and slave) * db1047 is to be decommissioned - https://phabricator.wikimedia.org/T156844#3107357 === Security === * Reviews: ** iOS 2-factor wrapping up ** Ex:WikibaseMediaInfo ** Ex:CodeMirror === Services === * Blockers: none * Updates: ** New version of the PDF render service still awaits checking from WMDE *** https://en.wikipedia.beta.wmflabs.org/api/rest_v1/#!/Page_content/get_page_… *** https://phabricator.wikimedia.org/T160764 ** All SCB services have been redeployed in preparation to DC switchover to pick up short-term DNS caching === RelEng === *Blockers: ** May need Ops help deploying 3d2png via scap3 (worked on Beta Cluster), need some +2 in puppet === Discovery === * No blockers * Discussing strategy for enabling live updates for completion suggester - probably starting with new pages * New Polish analyzers deployed, Ukrainian is next, working on Chinese * Working on Wikidata search improvement * Working on adding non-exact search capabilities to Special:Undelete * Working on improving noop detection plugins for Elasticsearch * Preparing for active-active switch === Fundraising Tech === * Moved all our scheduled jobs off Jenkins with surprisingly little complication: https://phabricator.wikimedia.org/T161569 ** Anybody need a job scheduler / cron wrapper script? ** yaml job description files with command, timeout, environment vars ** Ensures jobs run as a specified user ** non-ops can be given the ability to run defined jobs on demand ** can generate cron.d entries automatically ** See more here: https://github.com/wikimedia/wikimedia-fundraising-process-control * More work on Central Notice banner sequence, and general admin UI refactor: https://phabricator.wikimedia.org/T144453

1 0

[Reminder] CREDIT showcase, Wednesday, 5-April-2017
by Lani Goto 05 Apr '17

05 Apr '17

Just a reminder, CREDIT is starting in 30 minutes! ---------- Forwarded message ---------- From: Lani Goto <lgoto(a)wikimedia.org> Date: Thu, Mar 30, 2017 at 5:24 PM Subject: CREDIT showcase, Wednesday, 5-April-2017 To: wikitech-l(a)lists.wikimedia.org Hi! I'd like to welcome you to join us at the CREDIT showcase next week, Wednesday, 5-April-2017 at 1800 UTC / 1100 Pacific Time. We'd like to see your demos, whether they're rough works in progress or polished production material, or even just a telling of something you've been studying recently. For more information on the upcoming event, as well as recordings of previous events, please visit the following page: https://www.mediawiki.org/wiki/CREDIT_showcase And if you'd like to share the news about the upcoming CREDIT showcase, here's some suggested verbiage. Thanks! *Hi <FNAME>* *I hope all is well with you! I wanted to let you know about CREDIT, a monthly demo series that we’re running to showcase open source tech projects from Wikimedia’s Community, Reading, Editing, Discovery, Infrastructure and Technology teams. * *CREDIT is open to the public, and we welcome questions and discussion. The next CREDIT will be held on April 5th at 11am PT / 2pm ET / 18:00 UTC. * *There’s more info on MediaWiki, and on Etherpad, which is where we take notes and ask questions. You can also ask questions on IRC in the Freenode chatroom #wikimedia-office (web-based access here). Links to video will become available at these locations shortly before the event.* *Please feel free to pass this information along to any interested folks. Our projects tend to focus on areas that might be of interest to folks working across the open source tech community: language detection, numerical sort, large data visualizations, maps, and all sorts of other things.* *If you have any questions, please let me know! Thanks, and I hope to see you at CREDIT.* *YOURNAME* -- Lani Goto Project Assistant, Engineering Admin -- Lani Goto Project Assistant, Engineering Admin

1 0

Re: [Wikitech-l] Fantastic MediaWikis - Track at Wikimedia Hackathon - CfP
by Markus Glaser 05 Apr '17

05 Apr '17

Hello all, just a reminder: the call for participation for "Fantastic MediaWikis and How to Maintain Them", a one-day track at the Wikimedia Hackathon in Vienna, ends today. So if you intend to submit a presentation, please add yourself to this list: https://www.mediawiki.org/wiki/MediaWiki_Stakeholders%27_Group/Fantastic_Me… All the best, Markus (User:Mglaser) MediaWiki Stakeholders' Group -----Ursprüngliche Nachricht----- Von: Wikitech-l [mailto:wikitech-l-bounces@lists.wikimedia.org] Im Auftrag von Markus Glaser Gesendet: Montag, 20. März 2017 15:30 An: Wikimedia developers <wikitech-l(a)lists.wikimedia.org> Betreff: [Wikitech-l] Fantastic MediaWikis - Track at Wikimedia Hackathon - CfP [This sender failed our fraud detection checks and may not be who they appear to be. Learn about spoofing at http://aka.ms/LearnAboutSpoofing] Hello everyone, "Fantastic MediaWikis and How to Maintain Them" is a one-day conference track designed for people who work with the open source software MediaWiki in their organisation, company or business [1]. The conference track is curated by the MediaWiki Stakeholders Group and hosted by Wikimedia Austria. The track is part of Wikimedia's biggest annual tech-event, the Wikimedia Hackathon [2]: For three days each year, about 200 developers come together to improve MediaWiki. Among the participants are coders from the Wikimedia Foundation as well as volunteers from all over the world. We're using this opportunity to connect the people who work with MediaWiki in their enterprise, company, or organisation to the people who actually develop the code. We invite all MediaWiki stakeholders - power-users, maintainers, and service providers, who have a professional or semi-professional interest in the software - to join us for a day full of MediaWiki knowledge and networking! This is a call for participation. We are specifically looking for contributions of your experience in running MediaWikis. These include but are not confined to: * Use Cases. Tell us how and why you use MediaWiki in a specific area or to solve a specific problem. * Best Practices. Talk about the most effective way you have found to use particular MediaWiki features. * Enhancements. Have you improved MediaWiki to fit your needs? Show us your solution. * Challenges. How can we all add to MediaWiki functionality? Do you have specific ideas you want to collaborate on? Share your experience and submit a presentation here: https://www.mediawiki.org/wiki/MediaWiki_Stakeholders%27_Group/Fantastic_Me… Important dates: * 20th March 2017: Call for Participation opens * 5th April 2017: Submission deadline * 10th April 2017: Notification of acceptance * 19th - 21st May 2017: Vienna Hackathon We are looking forward to your submissions! Best, Markus (User:Mglaser) MediaWiki Stakeholders' Group [1] https://www.wikimedia.at/hackathon/fantastic-mediawikis/ [2] https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2017 _______________________________________________ Wikitech-l mailing list Wikitech-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l

1 0

Introducing the MediaWiki Platform Team!
by Victoria Coleman 05 Apr '17

05 Apr '17

Hello everyone, I am pleased to share with you the news about the formation of the latest team in the Technology department, the MediaWiki Platform team![1] The MediaWiki Platform team will be tasked with leading maintenance and improvements related to the core MediaWiki platform codebase. That includes encouraging future development of the MediaWiki platform and addressing the technical debt that has accumulated during the 15-year history of MediaWiki. MediaWiki is an amazing, powerful, and complex open-source software platform. The number and variety of extensions, and the wide variety of communities who have adopted MediaWiki as their method for knowledge collection and dissemination, are a testament to its strength as a software platform. Like any significant codebase with a long development history, there are remnants of design choices and experiments that are no longer in use, and some areas of code are in need of modernization. However, at its core is a large amount of highly functional, secure, performant code, capable of supporting a robust platform through the use of extensions and hooks. There is also a great amount of flexibility to adapt to new requirements. This team will have a more focused purpose than the previous MediaWiki Core team.[2]. While the previous team was at times spread too thin, many areas are now covered by dedicated teams like Security and Performance. The new MediaWiki Platform team will center their efforts on the core codebase. The team will also have a dedicated Product Manager who will be creating the platform roadmap in collaboration with the team, the Architecture Committee and the MediaWiki user community. Specific goals for this team are to: * Assist and encourage development of features for MediaWiki by providing developers with a strong core. * Undertake feature development work which is primarily architectural in nature. * Facilitate the development and publication of MediaWiki's roadmap to assist coordination between internal and external users. * Maintain and promote guidelines and standards for the MediaWiki core. I am thrilled that Tim Starling has agreed to lead the team, reporting directly to me. He will be joined by Brion Vibber, Kunal Mehta and Brad Jorsch. The team officially launches on Monday April 3, and will complete the hiring and onboarding of additional team members in the coming months. Their initial workplan will include core support for multi content revisions for the Structured Data on Commons project and will be discussed in more detail during the upcoming consultation for the Wikimedia Foundation 2017-2018 annual plan. I am excited by this latest evolution in the structure of the Foundation's Engineering group. We will continue to learn from our collective knowledge and expertise, and make adjustments to our composition and plans. I appreciate the input provided by many in the community that helped inform this decision. I also want to thank the members of the Wikimedia Foundation's Product, Technology, and Community Engagement departments who were involved in this process. In particular, I would like to thank Toby Negrin, Adam Baso, and Trevor Parscal - whose support was critical in bringing this plan together. Join me in welcoming and celebrating our new team! Victoria [1] https://www.mediawiki.org/wiki/MediaWiki_Platform_team <https://www.mediawiki.org/wiki/MediaWiki_Platform_team> [2] https://www.mediawiki.org/wiki/Wikimedia_MediaWiki_Core_Team <https://www.mediawiki.org/wiki/Wikimedia_MediaWiki_Core_Team>

7 6

Questions over usage of ObjectCache
by Nischay Nahata 04 Apr '17

04 Apr '17

Hi all, I have been trying to add certain rate limiting actions for my extension's API and noticed that it doesn't work with $wgMainCacheType set to CACHE_NONE This is because User::pingLimiter() uses ObjectCache::getLocalClusterInstance() to store the current rate limit counts. Is this the expected behavior? Looks pretty deceitful to me as $wgMainCacheType is assumed to define the cache type but is actually disabling a core functionality like rate limiting and maybe few others? Regards, Nischay Nahata

2 3

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

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