Wikitech-l September 2016

wikitech-l@lists.wikimedia.org

105 participants
111 discussions

[Discussion needed] Process for taking over abandoned tools
by Bryan Davis 21 Sep '16

21 Sep '16

In 2015, a phabricator task [0] and RfC discussion on meta [1] were started to create a process for determining when a tool has been abandoned by it's original maintainer(s) and how to hand control of the tool over to interested volunteers. The process stalled out without resolution. Our on-wiki communities are still highly dependent on volunteer developed tools and vulnerable to disruption when the original developers move on. I have drafted two straw dog [2] policies that attempt to define fair and workable solutions to the general problem. The proposals take two different but compatible approaches to solving the problem of abandonment. The Tool Labs developer community could choose to adopt either or both policies as protection for the communities that they serve. The first policy describes a *right to fork* for all Tool Labs hosted software. This policy clarifies the existing Tool Labs Open Source and Open Data requirements and defines a process for requesting access to code and data that are not already published publicly. The second policy is a more aggressive *abandoned tool policy* that describes a process for adding new maintainers to a tool account (adoption) with a future possibility of removing the original maintainers (usurpation). This policy is based primarily on the discussions that happened on Meta in 2015. Both policies propose creating a new committee of volunteers to evaluate requests and perform cleanup of sensitive data in the tool before providing the source code or direct access to the tool account. This provision is key actually implementing both proposals. Paid administration and management does not scale any better than paid editing. To continue to grow and thrive, the Tool Labs developer community needs to become more active in enforcing and expanding their own policies. Membership in the committees would require signing the Wikimedia Foundation's Volunteer NDA [3] to ensure that sensitive data is handled appropriately. If both polices are adopted the two committees should be collapsed into a single group with authority to handle both types of requests. The straw dog policies are posted on Wikitech: * https://wikitech.wikimedia.org/wiki/Help:Tool_Labs/Right_to_fork_policy * https://wikitech.wikimedia.org/wiki/Help:Tool_Labs/Abandoned_tool_policy Discussion of the particulars of each proposal should happen on their associated talk pages. As an example it would be appropriate to debate whether the 14 day non-functional waiting period is too short or too long on the Abandoned tool policy talk page. Discussion of the process in general can happen on Meta [1]. I would like discussion to remain open through *2016-10-12* (3 weeks from date of posting). Following the discussion period I hope to call for an approval vote of some sort to make the policies official. Wikitech and Tool Labs do not currently have well defined policies for establishing consensus, but I'm sure we can collectively come up with something reasonable. [0]: https://phabricator.wikimedia.org/T87730 [1]: https://meta.wikimedia.org/wiki/Requests_for_comment/Abandoned_Labs_tools [2]: https://en.wikipedia.org/wiki/Straw_man_proposal [3]: https://wikitech.wikimedia.org/wiki/Volunteer_NDA Bryan -- Bryan Davis Wikimedia Foundation <bd808(a)wikimedia.org> [[m:User:BDavis_(WMF)]] Sr Software Engineer Boise, ID USA irc: bd808 v:415.839.6885 x6855

1 0

WikiDev17 Collaboration topic (Re: Opening up MediaWiki dev summit in January?)
by Rob Lanphier 21 Sep '16

21 Sep '16

Scott suggested the following as one of three suggested topic ideas for WikiDev17. The three ideas: 1) Collaboration 2) Wikitext Maintenance 3) Machine Translation More inline about "1) Collaboration" below: On Tue, Sep 20, 2016 at 10:05 AM, C. Scott Ananian <cananian(a)wikimedia.org> wrote: > *1. *(A unified vision for) *Collaboration* > > - Real-time collaboration (not just editing, but chatting, curation, > patrolling) > - WikiProject enhancements: User groups, finding people to work with, > making these first class DB concepts > - Civility/diversity/inclusiveness, mechanisms to handle/prevent > harassment, vandalism, trolling while working together > - Real-time reading -- watching edits occur in real time > - Integration with WikiEdu > - Broadening notion of "an edit" in DB -- multiple contributors, > possibly multiple levels of granularity > - Tip-toeing toward "draft"/"merge" models of editing > - Better diff tools: refreshed non-wikitext UX, timelines, authorship > maps, etc. I've copied this wholesale into the "Collaboration" area on [[WikiDev17/Topic ideas]], and quoted it directly here: <https://www.mediawiki.org/wiki/Topic:Tbypptt9myumu7q7> Let's use this thread to focus on this part of Scott's proposal. A lot of these seems in scope for the Wikimedia Collaboration team. Does the scope that you're thinking of align with what the team has published on their page: <https://www.mediawiki.org/wiki/Collaboration> Rob (p.s. please feel free to start separate threads with the other parts of Scott's proposal)

2 1

2016-09-21 Scrum of Scrums meeting notes
by Grace Gellerman 21 Sep '16

21 Sep '16

https://www.mediawiki.org/wiki/Scrum_of_scrums/2016-09-21 = 2016-09-21 = == Product == === Editing === ==== Collaboration ==== * Blocking * Blocked ** Services is working with us on the ReviewStream feed we're developing. * Updates ** Continued work on MessagePoster. PageTriage change to use it up, but not merged yet ** Fixed moderation (e.g. when a page or topic is deleted) of Echo notifications ** Some other Echo changes, such as to how seen time works, GENDER i18n, and to the page-linked notification ==== Language ==== * Blocked: none * Blocking: none * Updates: ** Content Translation work continue; templates and other fixes. ** Jessie migration for Apertium is scheduled on October first week. ==== Parsing (Subbu not attending because of a conflict) ==== * Blocked: Parsoid's native <gallery> implementation is blocked on getting feedback from the VE team. * Patches in gerrit to parse language variant markup in Parsoid -- need to resolve a few questions before we can deploy this * Magic-word based optout of global user pages merged (__NOGLOBAL__) * Kunal has filed an RFC to remove magic link functionality in the parser: https://www.mediawiki.org/wiki/Requests_for_comment/Future_of_magic_links * Evaluation ongoing of a (already merged in core) PHP version of a HTML5 parser (as a potential replacement for Tidy). === Community Tech === * No blockers * Copyvio tools for French Wikipedia https://phabricator.wikimedia.org/T145431 * More performance testing in hopes to get PageAssessments deployed to English Wikipedia * Education Programs Dashboard https://phabricator.wikimedia.org/T125546 * Changes to CentralAuth for cross-wiki watchlists * Investigating work on improving blocking and harassment prevention tools === Reading === ==== Reading Web ==== * Current sprint: https://phabricator.wikimedia.org/project/view/2186/ * Preparing to enable hovercards ab test in italian and russian * Preparing to enable related articles in mobile in more wikis * Lazy images blog post * Next sprint: https://phabricator.wikimedia.org/project/view/2221/ * Enable related articles in mobile in more wikis ==== Mobile Content Service (MCS) ==== * Getting the aggregated feed endpoint working on Beta Cluster since feed aggragation happens in RB now. ==== Android native app ==== * Current sprint: https://phabricator.wikimedia.org/project/view/2216/ * Next sprint: https://phabricator.wikimedia.org/project/view/2238/ * Released to beta Monday 9/19. Plan is to get feedback, fix bugs, and release nav overhaul to the stable app by EOM. ==== iOS native app ==== * Current release board: https://phabricator.wikimedia.org/project/view/2188/ ** In regression ** Expected to be released Sept 21 * Next release board: https://phabricator.wikimedia.org/project/board/2220/ ** In progress ** MIgrating iOS Feed over to the MCS ** Adding In the news and a local notification ** Expected Delivery ~3 weeks ==== Reading Infrastructure ===== * no === Fundraising Tech === * Almost done getting rid of ActiveMQ! * Fixing CentralNotice db calls for strict mode * More refinements to CiviCRM contact de-duplication === RelEng === * Blocking ** no * Blocked ** wmf.18 load-time regression https://phabricator.wikimedia.org/T146099 * Updates ** Skipping wmf.19 entirely due to undiagnosed load-time regression https://wikitech.wikimedia.org/wiki/Incident_documentation/20160915-MediaWi… *** Tentative plan is to cut wmf.20 and deploy to group0 today and, if all goes well, adjust the remainder of this week's schedule accordingly *** https://phabricator.wikimedia.org/T144644#2654240 ** Completed Beta Cluster database migration to jessie/MariaDB 10 yesterday ** Reminder: no deploys week of Sept 26th ** Reminder: no train week of Oct 17th (but SWATs OK) === Analytics === * Blocking: None * Blocked: None * Updates: ** New AQS cluster is up! Massive reduction of latency. We'll increase the throttling threshold. ** Public Event Streams: Finalized Kasocki prototype. Considering using server side events / streaming instead of web-sockets. ** Edit history reconstruction: Some improvements on the quality of data, still a couple issues to fix. ** Pivot (druid based UI): More work on productionizing it using servicerunner ** A/B testing design - Evaluating feasibility of design ideas. ** Nuria participated in the Technology off-site, very productive. === Technical Operations === * '''Blocking''' ** None * '''Blocked''' ** None * Updates ** TechOps offsite happening week of Sept 25 (last week of quarter), please work around this for deployments ** Will not be able to attend SoS for the same reason ** Puppet migration complete ** Varnish upload cluster upgraded to version 4. There are some caveats, but looking good https://phabricator.wikimedia.org/T145661 ** Apertium migration to Jessie scheduled for Oct 3 ** OpenStackManager in wikitech is being deprecated. There will be information coming your way in the next weeks. === Security === * Patch deployed for CentralAuth on monday; let us know if you experience weirdness * Will follow-up on Youdao review ( https://phabricator.wikimedia.org/T143185) * Catching up on e-mail, Gerrit, and Phab traffic from last week === Services === * Blocking: none * Blocked: none * Updates: ** Huge RESTBase deployment, VE now usable on undeleted articles ** Change-Prop: separated transclusions topics - decrease user visibility of lagging ** Trending service planning with reading ** Bad articles stream planning === Discovery === * No blockers * Analyzing BM25 A/B test, if results are positive deployment will be somewhere early October * Working on multiwiki indexes, public comments sought at: ** https://www.mediawiki.org/wiki/Cross-wiki_Search_Result_Improvements ** https://www.mediawiki.org/wiki/Cross-wiki_Search_Result_Improvements/Design * Working on file properties indexing (size, type, dimensions, etc.) * WDQS servers on codfw deployed, looking into how to add them to production setup * Portal: updated portal strings to "Read Wikipedia in your language" and language wiki descriptions. == Wikidata == * Blocker: Can not connect to the Hangout on https://hangouts.google.com/hangouts/_/wikimedia.org/scrum-of-scrums. Get error "HJR: 2-RNF". * No other ;-) blockers at the moment. * Making usage information (which page on which wiki uses which Wikidata entity) visible to users: https://phabricator.wikimedia.org/T103091 * Introduced batching in the job that notifies wikis about changes on wikidata.org: https://gerrit.wikimedia.org/r/309972, https://phabricator.wikimedia.org/T107722 * Working on cleaning up several dependencies on legacy stuff in core, e.g. https://phabricator.wikimedia.org/T144977 * Pushing multi content revisions forward.

1 0

Re: [Wikitech-l] Opening up MediaWiki dev summit in January?
by Rob Lanphier 21 Sep '16

21 Sep '16

On Tue, Sep 20, 2016 at 10:05 AM, C. Scott Ananian <cananian(a)wikimedia.org> wrote: > Here are three topic suggestions, cc'ed here in case folks aren't following > the Flow, with an illustrative (but not exhaustive) list of sessions that > could fit under each Thanks for doing that breakdown! I incorporated your suggestions into this page: <https://www.mediawiki.org/wiki/WikiDev17/Topic_ideas> I suspect each of the three ideas you presented here are worthy of separate threads (and perhaps separate on-wiki conversations), so I'll reply to at least the first part under separate cover. Rob

1 0

Re: [Wikitech-l] [Engineering] Long running tasks/scripts now included on [[wikitech:Deployments]]
by Greg Grossmeier 20 Sep '16

20 Sep '16

<quote name="Aaron Schulz" date="2016-09-20" time="15:31:44 -0700"> > How far ahead of time must entries be added? I trust most people's best judgement here :) But, as soon as you have an idea of when you'll do it is the best time to do it. Obviously if the task will impact others and/or require no other deploys at the same time that should be scheduled further in advance (~1 week) than something that is low-risk and will be completed in 2-3 hours. -- | Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E | | Release Team Manager A18D 1138 8E47 FAC8 1C7D |

1 0

Opening up MediaWiki dev summit in January?
by Brion Vibber 20 Sep '16

20 Sep '16

The last couple years we've done a big MediaWiki Dev Summit in January, around the time of the Wikimedia Foundation all-hands meeting. Invitations have been fairly broad to known developers, but there's a very strong feeling that newbies, non-technical people, and in general *the people MediaWiki is created and maintained for* are not welcome. I think we should change this. I would really like a broader MediaWiki Dev Summit that asks our users to participate, and asks "developers" to interact with them to prioritize and work on things that really matter to them. I want template authors, Lua module authors, template users, power editors, folks working on the lines of defense for vandalism patrol and copyvio checking. I want people with opinions on discussion systems. I want people who have been editing for years and have experience with what works and what doesn't. I want people who wish they could edit but have a bad experience when they try, and want to share that with us so we can help make it better. Thoughts? -- brion

21 37

ArchCom IRC office hour: Content Meta-Data Storage for MCR
by Daniel Kinzler 19 Sep '16

19 Sep '16

Hi all! This Wednesday the ArchCom office hour will be about discussing the next steps towards support for Multi-Content Revisions (MCR). The focus will be on the heart of the proposal, the database schema for associating multiple content objects with a single revision[1]. The basic schema was discussed recently in the context of improving content model storage[2]. This session will be about resolving some remaining questions about the schema, and about discussing the deployment and migration strategy. Detail questions: - Do we want a single names table, or separate tables for content_model, content_format, etc? - Do we need cont_hash (or cont_sha1) and cont_logical_size? - De we re-use or copy content rows? - If we re-use, does the role live in the content or in the slot label? Broader questions: - Are the scaling and Efficiency estimates correct? - What options do we have for optimization? - Would the proposed migration plan work? The discussion is scheduled for 2016-09-21 UTC: Time: Wednesday 21 UTC (2pm PDT, 23 CEST) Place: #wikimedia-office Phab event: [E273][3] [ArchCom/Status][4] Daniel [1]: <https://www.mediawiki.org/wiki/Multi-Content_Revisions/Content_Meta-Data> [2]: <https://phabricator.wikimedia.org/E261> [3]: <https://phabricator.wikimedia.org/E273> Upcoming meeting [4]: <https://www.mediawiki.org/wiki/Architecture_committee/Status> -- Daniel Kinzler Senior Software Developer Wikimedia Deutschland Gesellschaft zur Förderung Freien Wissens e.V.

1 0

Beta Cluster maintenance window tomorrow 9/19 1400-1700 UTC
by Dan Duvall 19 Sep '16

19 Sep '16

Due to an unexpected production database outage during last week's maintenance window, we were unable to complete the Beta Cluster database migration to the new Debian jessie instances. We'll be performing this migration during a three-hour read-only maintenance window tomorrow from 1400-1700 UTC. Please contact Release Engineering (#wikimedia-releng) if you have concerns/questions regarding this process, or refer to the Phabricator task (T138778). https://phabricator.wikimedia.org/T138778 Thanks, Dan -- Dan Duvall Software Engineer, Release Engineering Wikimedia Foundation <http://wikimediafoundation.org>

1 0

Outreachy-13 "almost there" projects
by Sumit Asthana 19 Sep '16

19 Sep '16

Hi all, I've tried to sort out some "probable" and interesting internship projects which have a well-defined scope and/or *one* mentor willing to support it. Please go through them, and let us know if you'd like to mentor, so that we can feature it for Outreachy-13 [0]( Dec 6 to March 6 ). *Needing Primary mentors:* 1. Fork NYPL emoji bot for Commons images (to give back 'similar' Commons images) - T143593 [1] - Interesting project on emojis, @*Melody* has agreed to provide design help, just needs technical help from someone. 2. Document process for creating new Zotero translator and getting it live in production - T115158 [2] - *@Mvolz* has agreed to be co-mentor. We need a primary mentor. 3. Editor-focused dashboard gadget - T91655 [3] - An interesting idea of a gadget for personalized user pages for editors - *@Mvolz* has agreed for co-mentor. We need a primary mentor. 4. Remind me of this article in X days - T2582 [4] - Interesting idea to create reminders for editors. *@Mattflaschen and @Mooeypoo* have agreed to be co-mentor, we need a primary mentor. *Needing co-mentors*: 1. Improvements to ProofreadPage Extension and Wikisource - T128840 [5] - *@Yann* has agreed to help with fixes fro ProofreadPage Extension, needs a co-mentor. 2. Pywikibot to detect and correctly handle edits that trigger abusefilter rules - T85656 [6] - *@jayvdb* is mentoring, we need a co-mentor With some help we can feature these projects for Outreachy-13 and have some more cool ideas for students to work on. For signing up as a mentor, just add yourself on the task, or ping and we'll do the rest. Please do consider giving a shot :) [0] - https://www.mediawiki.org/wiki/Outreachy/Round_13 [1] - https://phabricator.wikimedia.org/T143593 [2] - https://phabricator.wikimedia.org/T115158 [3] - https://phabricator.wikimedia.org/T91655 [4] - https://phabricator.wikimedia.org/T2582 [5] - https://phabricator.wikimedia.org/T128840 [6] - https://phabricator.wikimedia.org/T85656 -- -Thanks and Regards, Sumit Outreachy-13 Org Admin

1 0

Phab blogs
by Amir E. Aharoni 19 Sep '16

19 Sep '16

Hi, I only now noticed that Phabricator has blogs: https://phabricator.wikimedia.org/phame/blog/ I couldn't find a way to subscribe to them in RSS. Is it possible? -- Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי http://aharoni.wordpress.com ‪“We're living in pieces, I want to live in peace.” – T. Moore‬

6 6

← Newer
1
2
3
4
5
6
7
8
9
...
12
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 September 2016