[Wikitech-l] Weigh in on whether to finalize "Diversity" and “Conflict of interest” sections of Code of Conduct
Please comment on whether to approve the "Diversity" and "Conflict of interest" section of the draft Code of conduct for technical spaces: * Diversity - https://www.mediawiki.org/wiki/Code_of_Conduct/Draft#Diversity * Conflict of interest - https://www.mediawiki.org/wiki/Code_of_Conduct/Draft#Conflict_of_interest You can comment at https://www.mediawiki.org/wiki/Talk:Code_of_Conduct/Draft#Finalize_.22Diversity.22_and_.22Conflict_of_interest.22_sections.3F . A position and brief comment is fine. You can also send private feedback to conduct-discuss...@wikimedia.org . Thanks again, Matt Flaschen ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] [MediaWiki-announce] Security Release - 1.27.1, 1.26.4, 1.23.15
I would like to announce the release of MediaWiki 1.27.1, 1.26.4, 1.23.15! These releases fix five security issues in core and one for the extension PdfHandler. Download links are given at the end of this email. == Security fixes == * (T139565) API: Generate head items in the context of the given title (CVE-2016-6335) * (T137264) XSS in unclosed internal links (CVE-2016-6334) * (T133147) Escape '<' and ']]>' in inline
[Wikitech-l] The Revision Scoring weekly update
Hey, This is the 18th weekly update from revision scoring team that we have sent to this mailing list. *Communications:* - Aaron presented on how user-feedback has been helping us address some sneaky biases in ORES' models. [1, 2, 3] *New development:* - We included 'autoreview' and 'patroller' groups in Turkish wiki models to get a fitness boost. [4] - We added some basic uwsgi metrics to grafana[5] and added a response timing metric from Change Propagation so that we can track any performance issues. [6] *Maintenance and robustness:* - We increased the number of workers per node in production for a 66% increase in total capacity for ORES[7] - We updated all of our edit quality models with the new version of revscoring [8] and sent an email out to wikitech-l and ai-l about the implications for tool developers. [9] - We decided not to make specialized models for ORES in beta labs. [10] Instead, we'll use the production models so that issues with them will be caught in beta. 1. https://phabricator.wikimedia.org/T143275 -- Present on user-feedback stories at Research Showcase 2. https://www.youtube.com/watch?v=rsFmqYxtt9w#t=29m00s -- Video of ORES user-feedback talk 3. https://www.mediawiki.org/wiki/File:Deploying_and_maintaining_AI_in_a_socio-technical_system_--_Research_Showcase_(August_2016).pdf 4. https://phabricator.wikimedia.org/T140474 -- Include specific user groups in the trwiki edit quality model 5. https://phabricator.wikimedia.org/T143081 -- Add uwsgi-related metrics to grafana 6. https://phabricator.wikimedia.org/T143568 -- Add median, 75% and 95% response time to ORES dashboard 7. https://phabricator.wikimedia.org/T143105 -- Increase celery workers to 40 per scb node 8. https://phabricator.wikimedia.org/T143125 -- Update editquality models with new version of revscoring 9. https://lists.wikimedia.org/pipermail/ai/2016-August/68.html -- "[AI] New models coming to ORES & notes" 10. https://phabricator.wikimedia.org/T141980 -- Should we make a model for ores in beta? Sincerely, Aaron from the Revision Scoring team ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] SWAT deploy slot time changes (and adding European mid-day slot)
Le 09/08/2016 à 20:00, Greg Grossmeier a écrit : > I'm pleased to announce that after being heavily SF-focused for a long > time we're adding a Europe-focused (and slightly better for Asia/India) > SWAT window[0] starting on August 22nd[1]. > > This new SWAT window follows a couple changes to the SWAT process[2] and > scap tooling[3] which make SWAT deploys less risky and stressful for all > involved. Hello, It went all fine. The canary check and mw1099/X-Wikimedia-Debug make it a breeze to do the deployments. We had 8 patches which kept us busy, I am hoping to do actual training / levelling up when there are less patches to push. cheers, -- Antoine "hashar" Musso ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l