Wikitech-l May 2016

wikitech-l@lists.wikimedia.org

113 participants
123 discussions

Reducing the environmental impact of the Wikimedia movement
by Lukas Mezger 24 May '16

24 May '16

Dear readers of the Wikitech mailing list, I am a member of the Wikipedia community and I have started a project to reduce the environmental impact of the Wikimedia movement <https://meta.wikimedia.org/wiki/Environmental_impact>. The main idea is to use renewable energy for running the Wikimedia servers and the main reason for this is that by doing so, Wikipedia can set a great example for environmental responsibility in the entire internet sector. My project was started after Greenpeace USA published a report <http://www.greenpeace.org/usa/global-warming/click-clean/> about the energy consumption of the biggest sites on the Internet in 2015 and in which Wikipedia, to my astonishment, performed poorly, receiving a "D" score and only passing because of the Wikimedia Foundation's openness about its energy consumption. I would very much like to change that and set up a page called "Environmental impact <https://meta.wikimedia.org/wiki/Environmental_impact>" on Meta. I have already discussed the issue with a few people both from the Wikimedia Foundation's management and from the Wikimedia community and have received positive responses. In order to further advance the project, I would like to learn more about how much energy Wikipedia's servers use. As far as I can tell, these figures are not public, but I believe they could very well be. Also, I am interested to learn how changing a server site's energy sources can be carried out on the operations side since the United States energy sector hasn't been completely deregulated yet. So, thank you very much for any comments! Maybe there also is an even better forum to discuss these questions? Finally, if you would like to support my project, please consider adding your name to this list <https://meta.wikimedia.org/wiki/Environmental_impact#Show_your_support>. Thank you. Kind regards, Lukas Mezger / User:Gnom <https://meta.wikimedia.org/wiki/User:Gnom>

14 18

The Revision scoring weekly update
by Amir Ladsgroup 23 May '16

23 May '16

Hey, This is the fifth weekly update for revision scoring team that we sent to this mailing list. *New developments:* - We got Swedish basic model ready to deloy, likely to happen in the next week [1] [2] - We generated list of bad words for every Wikipedia with more than 100K articles (with a few exceptions) [3] *Maintenance and robustness:* - We enabled CORS for Wikimedia wikis in wikilabels and now we won't let you do write actions via GET [4] - We are using systemd watchdogs in precaching to be sure it stays alive. [5] - We are changing some settings in nginx and uwsgi in order to finalize moving to prod [6] 1. https://phabricator.wikimedia.org/T131450 2. https://phabricator.wikimedia.org/T135604 3. https://phabricator.wikimedia.org/T134629 4. https://phabricator.wikimedia.org/T135377 5. https://phabricator.wikimedia.org/T135941 6. https://phabricator.wikimedia.org/T135655 Sincerely, The Revision scoring team

1 0

AuthManager is now in core and 1.27
by Brad Jorsch (Anomie) 23 May '16

23 May '16

TL;DR: AuthManager is now in core, although it's currently behind a feature flag that is disabled on Wikimedia wikis. We're hoping that feature flag can be removed from 1.27 before release. Help fix extensions! AuthManager is a new authentication system for MediaWiki that allows for easily plugging in multiple authentication methods, non-password-based authentication methods (such as authentication by redirecting to a third-party service), secondary authentication methods like two-factor auth, and so on. We've[1] been working on it for over a year now, and it's getting close to being done. Last week, we merged the core patches[2] and fixes for extensions bundled in the tarball. These were also backported to the REL1_27 branch. Documentation is now at https://www.mediawiki.org/wiki/Manual:SessionManager_and_AuthManager, please feel free to ask questions or to improve it. AuthManager is currently behind a feature flag, $wgDisableAuthManager, which can be set to use the old authentication system rather than AuthManager. For Wikimedia wikis, our next step is to fix the rest of the extensions we use,[3] then (gradually) enable AuthManager while making sure things don't break.[4] We plan to default the flag to enabling AuthManager in master soon,[5] and we hope to be able to remove it entirely from 1.27 before release.[6] If you maintain an extension in Gerrit and it needs updating for AuthManager, we've probably already filed a task in Phabricator for you! Look at the subtasks of T110282 for extensions deployed on Wikimedia wikis, or of T110291 for other extensions. Besides the information in the tasks, we've also compiled a list of common things needing updating and some solutions.[6] If you run a wiki, you might need to set $wgDisableAuthManager = true if you have extensions that break. Remember, though, this isn’t a permanent solution, and you’ll need to update your extensions reasonably soon. If you run a bot that still uses API action=login (and isn't using it for BotPasswords), it's time to update! If you have an interactive application that logs in with API action=login, you'll want to prepare to start using action=clientlogin. If you want some visibility, the tracking task for clients is T134945. If you find bugs in AuthManager, please report them in Phabricator and include the #Reading-Infrastructure-Team tag. See also previous AuthManager announcements: * https://lists.wikimedia.org/pipermail/wikitech-l/2016-January/084501.html * https://lists.wikimedia.org/pipermail/mediawiki-api/2016-January/003686.html * https://lists.wikimedia.org/pipermail/mediawiki-api/2016-January/003688.html [1]: Mainly Gergő Tisza and I, with help from Bryan Davis and Chris Steipp. [2]: https://gerrit.wikimedia.org/r/#/c/195297/, https://gerrit.wikimedia.org/r/#/c/240052/, https://gerrit.wikimedia.org/r/#/c/265201/, and https://gerrit.wikimedia.org/r/#/c/282202/ [3]: https://phabricator.wikimedia.org/T110282 [4]: https://phabricator.wikimedia.org/T135504 [5]: We tried to do it already, but it broke all the selenium tests due to changes to account creation. See https://phabricator.wikimedia.org/T135884 for progress on that. [6]: https://phabricator.wikimedia.org/T135498 [7]: https://www.mediawiki.org/wiki/Manual:SessionManager_and_AuthManager/Updati… -- Brad Jorsch (Anomie) Senior Software Engineer Wikimedia Foundation -- Brad Jorsch (Anomie) Senior Software Engineer Wikimedia Foundation

1 0

Wired article about machine learning
by Pine W 23 May '16

23 May '16

Seems like a good summary: http://www.wired.com/2016/05/the-end-of-code/ Comments welcome, especially from Wikimedia AI experts who are working on ORES. Pine

4 3

ArchCom-RFC status update: 2016-W20
by Rob Lanphier 23 May '16

23 May '16

Hi everyone, Here's the ArchCom RFC status update for 2016-W20 [1], which is also available via mw:Architecture_committee/Status [2] ===== Recent RFC meetings ===== * ArchCom Planning meeting 2016W20: 2016-05-18: [[Phab:E183]] (E156/7) ** Notes: [[Architecture committee/2016-05-18]] * ArchCom-RFC office hour 2016W20: 2016-05-18: [[Phab:E184]] (E66/35) ** [[Phab:T102476|T102476: RFC: Requirements for change propagation]] ===== Upcoming RFC meetings ===== * ArchCom Planning meeting 2016W21: 2016-05-25: [[Phab:E194]] (E156/8) ** Notes: [[Architecture committee/2016-05-25]] * ArchCom-RFC office hour 2016W21: 2016-05-25: [[Phab:E187]] (E66/36) ** RFC triage meeting using [[phab:tag/archcom-rfc/|ArchCom RFC board]] ** Goal: assign priorities for items marked "needs triage" and ensure that high priority items are clearly marked as such ===== Entering Final Comment Period ===== * None. ===== Recently Approved ===== * [[Phab:T120164|T120164 RFC: Institute "last call" period]] ==== RFC inbox ==== * [[phab:tag/archcom-rfc/|ArchCom RFC board]]: ** Inbox zero on 2016-06-11. ===== Shepherd status ===== * Brion ** (?) * Daniel ** Software Quality working group? ** Working on Multi Content Rev Spec with Brion ** T113034 [[phab:T113034|RFC: Overhaul Interwiki map, unify with Sites and WikiMap]]: (Update?) * Gabriel ** Working with [[User:BSitzmann (WMF)|BSitzmann]] on [[Phab:T132597|T132597]] (RFC: Agree on endpoints for feeds) * Roan ** T108655 [[phab:T108655|RFC: Standardise JavaScript interfaces]]: I need to start the second part, but the recent comments have me confused. I'll need to talk to Timo and figure out what the subject of part two should be. * RobLa ** Still need to schedule an RFC triage meeting outside of ArchCom-RFC time *** Filed [[phab:T135674|T135674]], and made it clear that I'm not going to be able to do this without some help. ** Created [[phab:project/manage/2002/|#ArchCom-Approved Phab tag]] ([[Phab:T133803|T133803]]) * Tim ** Not many updates with cscott out of office. T89331 (Replace Tidy in MW parser with HTML 5 parse/reserialize) ** T114444 [[phab:T114444|RFC: Introduce notion of DOM scopes in wikitext]]: (Update?) * Timo ** No update ===== No activity in the last two weeks ===== * T18691 [[phab:T18691|RFC: Section headings should have a clickable anchor]] (Timo) * T111588 [[phab:T111588|RFC: API-driven web front-end]] (Timo) * T123753 [[phab:T123753|Establish retrospective reports for Security and Performance incidents]] (RobLa) * T122825 [[phab:T122825|Service ownership and minimum maintenance requirements]] (Gabriel) * T105766 [[phab:T105766|RFC: Dependency graph storage]] (Gabriel) * T124504 [[phab:T124504|Transition WikiDev '16 working areas into working groups]] (RobLa) * T66214 [[phab:T66214|Use content hash based image / thumb URLs & define an official thumb API]] (Brion) * T91162 [[phab:T91162|RFC: Shadow namespaces]] (Brion) * T128351 [[phab:T128351|RFC: Notifications in core]] (Brion) * T122825 [[phab:T122825|Service ownership and minimum maintenance requirements]] (Gabriel) * T54807 [[phab:T54807|Identify and remove legacy preferences from MediaWiki core]] (no shepherd) * T88596 [[phab:T88596|Improving extension management]] (Daniel) Our meeting for 2016-W21 (this coming Wednesday) will be a triage of the ArchCom-RFC queue[3] Rob [1] ISO week 2016-W20: https://en.wikipedia.org/wiki/ISO_week_date [2] https://www.mediawiki.org/wiki/Architecture_committee/Status [3] https://phabricator.wikimedia.org/tag/archcom-rfc/

1 0

Discovery Weekly Update for the week starting 2016-05-16
by Chris Koerner 22 May '16

22 May '16

Hi, Here is this week's update from the Discovery department. * A Wikipedia.org survey was run from May 10 - 17, 2016 to determine how visitors arrived at the portal page. Survey results here. [1] * A Wikipedia.org production release was done on May 18, 2016 which added descriptive text to the sister wiki project links. [2] * WikiVoyage experimental map with custom layers. [3] * Analysis was done for the Portal A/B test for the addition of descriptive text to the sister wiki project links. [4] * Deb will be coordinating with User Research team to get interviews setup for survey responders that want to talk about how they use the wikipedia portal. [1] https://commons.wikimedia.org/wiki/File:Wikipedia_Portal_Survey_-_May_2016.… [2] https://www.mediawiki.org/wiki/Wikipedia.org_Portal_A/B_testing#A.2FB_test:… [3] https://en.wikivoyage.org/wiki/Wikivoyage:Travellers%27_pub#Maps_with_extra… [4] https://commons.wikimedia.org/wiki/File:Descriptive_Text_for_Sister_Project… ---- Feedback and suggestions on this weekly update are welcome! The full update, and archive of past updates, can be found on Mediawiki.org: https://www.mediawiki.org/wiki/Discovery/Status_updates -- Yours, Chris Koerner Community Liaison - Discovery Wikimedia Foundation

1 0

Community Tech survey on watchlist use
by Danny Horn 21 May '16

21 May '16

Hi everyone, WMF's Community Tech team is starting to work on a Cross-wiki watchlist, one of the top 10 wishes in the Community Wishlist Survey that we conducted at the end of last year. [1] We're running a survey on how people use their watchlists, to help inform our work. If you've got a minute and want to share your thoughts, here's the survey link: https://wikimedia.qualtrics.com/SE/?SID=SV_1BRVhdayaTyuGJ7 The survey's hosted on a third-party service. We'll be running the survey for about a week, and once it's closed, we'll publish aggregated results on Meta.[2] Feel free to pass the link on, if you'd like to. Let me know if you have any questions. Thanks! Danny Horn Product Manager, WMF Community Tech [1] Info on the Community Wishlist Survey: https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey Info on the Cross-wiki watchlist project: https://meta.wikimedia.org/wiki/Community_Tech/Cross-wiki_watchlist [2] Survey Privacy Statement: https://wikimediafoundation.org/wiki/Survey_Privacy_Statement_for_March_201…

2 1

[MediaWiki-announce] Security Release: 1.26.3, 1.25.6, and 1.23.14
by Chad 20 May '16

20 May '16

I would like to announce the release of MediaWiki 1.26.3, 1.25.6 and 1.23.14. These releases fix sixteen security issues in core, one issue in the bundled extension SyntaxHighlight_GeSHi and one issue in the non-bundled extension Scribunto. Download links are given at the end of this email. == Security fixes == * T122056: Old tokens are remaining valid within a new session * T127114: Login throttle can be tricked using non-canonicalized usernames * T123653: Cross-domain policy regexp is too narrow * T123071: Incorrectly identifying http link in a's href attributes, due to m modifier in regex * T129506: MediaWiki:Gadget-popups.js isn't renderable * T125283: Users occasionally logged in as different users after SessionManager deployment * T103239: Patrol allows click catching and patrolling of any page * T122807: [tracking] Check php crypto primatives * T98313: Graphs can leak tokens, leading to CSRF * T130947: Diff generation should use PoolCounter * T133507: Careless use of $wgExternalLinkTarget is insecure * T132874: API action=move is not rate limited This fix affects both core and SyntaxHighlight_GeSHi: * T110143: strip markers can be used to get around html attribute escaping in (many?) parser tags These two fixes are not applicable to 1.23.14 as the 1.23 branch does not contain pbkdf2 support. * T116030: Increase pbkdf2 parameter strengths * T127420: Pbkdf2Password does not check if hash_pbkdf2() succeeded This fix is already in master and the 1.27 release branch, and is just being backported to 1.23 and 1.25: * T126685: Globally throttle password attempts == Links to all mentioned tasks == https://phabricator.wikimedia.org/T122056 https://phabricator.wikimedia.org/T127114 https://phabricator.wikimedia.org/T123653 https://phabricator.wikimedia.org/T123071 https://phabricator.wikimedia.org/T129506 https://phabricator.wikimedia.org/T125283 https://phabricator.wikimedia.org/T103239 https://phabricator.wikimedia.org/T122807 https://phabricator.wikimedia.org/T98313 https://phabricator.wikimedia.org/T130947 https://phabricator.wikimedia.org/T133507 https://phabricator.wikimedia.org/T132874 https://phabricator.wikimedia.org/T110143 https://phabricator.wikimedia.org/T116030 https://phabricator.wikimedia.org/T127420 https://phabricator.wikimedia.org/T126685 == Release notes == Full release notes for 1.26.3: <https://www.mediawiki.org/wiki/Release_notes/1.26> Full release notes for 1.25.6: <https://www.mediawiki.org/wiki/Release_notes/1.25> Full release notes for 1.23.14: <https://www.mediawiki.org/wiki/Release_notes/1.23> For information about how to upgrade, see <https://www.mediawiki.org/wiki/Manual:Upgrading> ********************************************************************** 1.26.3 ********************************************************************** Download: https://releases.wikimedia.org/mediawiki/1.26/mediawiki-1.26.3.tar.gz https://releases.wikimedia.org/mediawiki/1.26/mediawiki-core-1.26.3.tar.gz Patch to previous version: https://releases.wikimedia.org/mediawiki/1.26/mediawiki-1.26.3.patch.gz GPG signatures: https://releases.wikimedia.org/mediawiki/1.26/mediawiki-1.26.3.tar.gz.sig https://releases.wikimedia.org/mediawiki/1.26/mediawiki-1.26.3.patch.gz.sig https://releases.wikimedia.org/mediawiki/1.26/mediawiki-core-1.26.3.tar.gz.… Public keys: https://www.mediawiki.org/keys/keys.html ********************************************************************** 1.25.6 ********************************************************************** Download: https://releases.wikimedia.org/mediawiki/1.25/mediawiki-1.25.6.tar.gz https://releases.wikimedia.org/mediawiki/1.25/mediawiki-core-1.25.6.tar.gz Patch to previous version: https://releases.wikimedia.org/mediawiki/1.25/mediawiki-1.25.6.patch.gz GPG signatures: https://releases.wikimedia.org/mediawiki/1.25/mediawiki-1.25.6.tar.gz.sig https://releases.wikimedia.org/mediawiki/1.25/mediawiki-1.25.6.patch.gz.sig https://releases.wikimedia.org/mediawiki/1.25/mediawiki-core-1.25.6.tar.gz.… Public keys: https://www.mediawiki.org/keys/keys.html ********************************************************************** 1.23.14 ********************************************************************** Download: https://releases.wikimedia.org/mediawiki/1.23/mediawiki-1.23.14.tar.gz https://releases.wikimedia.org/mediawiki/1.23/mediawiki-core-1.23.14.tar.gz Patch to previous version: https://releases.wikimedia.org/mediawiki/1.23/mediawiki-1.23.14.patch.gz GPG signatures: https://releases.wikimedia.org/mediawiki/1.23/mediawiki-1.23.14.tar.gz.sig https://releases.wikimedia.org/mediawiki/1.23/mediawiki-1.23.14.patch.gz.sig https://releases.wikimedia.org/mediawiki/1.23/mediawiki-core-1.23.14.tar.gz… Public keys: https://www.mediawiki.org/keys/keys.html -Chad H. & Chris S. _______________________________________________ MediaWiki announcements mailing list To unsubscribe, go to: https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce

3 3

Community Consultation on Labs Terms of Use: Round 1
by Zhou Zhou 20 May '16

20 May '16

Hi all, The Wikimedia Legal team is interested in revising, updating, and clarifying the existing Labs Terms of Use governing developers and their projects on labs. We have opened up Round 1 of our community consultation <https://meta.wikimedia.org/wiki/Labs_TOU_Consultation_Round_1_(2016)> to hear feedback on the Labs Terms of Use. We will try to respond the best we can, but the main purpose of this round is to hear all your thoughts. After the feedback round, we will prepare a draft revision of the Terms based on that feedback and other minor revisions to clarify statements in existing the Terms. We will then engage in a community discussion about the revised Terms. We plan to leave the discussion open until June 9, 2016. Thank you for all your help and feedback. Best, Zhou -- Zhou Zhou Legal Counsel Wikimedia Foundation 149 New Montgomery Street, 6th Floor San Francisco, CA 94105 zzhou(a)wikimedia.org NOTICE: This message might have confidential or legally privileged information in it. If you have received this message by accident, please delete it and let us know about the mistake. As an attorney for the Wikimedia Foundation, for legal/ethical reasons I cannot give legal advice to, or serve as a lawyer for, community members, volunteers, or staff members in their personal capacity. For more on what this means, please see our legal disclaimer <https://meta.wikimedia.org/wiki/Wikimedia_Legal_Disclaimer>.

1 0

Security release later today + 1.28 stuff
by Chad 20 May '16

20 May '16

Hi, I had originally planned to release 1.28.0-rc.0 today. Instead we'll be getting a security release! This release will cover all active branches. The new versions will be 1.23.14, 1.25.6 and 1.26.3. Master and the REL1_27 branches will also get the patches. There's quite a few fixes going into this release so all installs are strongly advised to upgrade. The RC for 1.28 will happen on Monday. The reasoning is half for the security release and the other is because I wanted a few more days for the AuthManager code to stew on beta before releasing it. Thanks! -Chad

2 4

← Newer
1
2
3
4
5
6
7
8
...
13
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 May 2016