Page MenuHomePhabricator

Wikimedia Technical Conference 2019 Session: Mediawiki Code Ownership
Open, Needs TriagePublic

"Love" token, awarded by Addshore."Love" token, awarded by bd808."Meh!" token, awarded by zeljkofilipin."Pterodactyl" token, awarded by brennen."Like" token, awarded by MusikAnimal."Love" token, awarded by Jrbranaa."Love" token, awarded by hashar."Like" token, awarded by Aklapper."Love" token, awarded by TK-999.
Assigned To
Authored By
debt, Fri, Oct 4



  • Track: Standardization Decisions
  • Topic: Mediawiki Code Ownership


In this session we will be looking for solutions to our code stewardship problems.

Questions to answer and discuss

Question: Should we divide MediaWiki into sections and assign maintainers?

Question: What incentives can we provide for owning code long-term?

Related Issues

  • ...
  • ...

Pre-reading for all Participants

  • [add links here]

Notes document(s)

[link to notes document (gdoc and / or etherpad)]

Notes and Facilitation guidance

Session Leader(s)

Session Scribes

  • [name]
  • [name]

Session Facilitator

  • [name]

Session Style / Format

  • [what type of format will this session be?]

Session Leaders please:

  • Add more details to this task description.
  • Coordinate any pre-event discussions (here on Phab, IRC, email, hangout, etc).
  • Outline the plan for discussing this topic at the event.
  • Optionally, include what this session will not try to solve.
  • Update this task with summaries of any pre-event discussions.
  • Include ways for people not attending to be involved in discussions before the event and afterwards.

Post-event summary:

  • ...

Post-event action items:

  • ...

Event Timeline

debt created this task.Fri, Oct 4, 3:43 PM
TK-999 awarded a token.Sat, Oct 5, 3:01 PM
hashar awarded a token.Mon, Oct 7, 2:51 PM
hashar added a subscriber: hashar.Mon, Oct 7, 2:54 PM

This is especially important when deploying code to production, it might be difficult to find the proper code maintainer. I am worrying this session might be to short to address the problem and find a clear solution.

Happy to help with this session.

@Jrbranaa @D3r1ck01 - Would either or both of you be interested in leading this session?

kaldari updated the task description. (Show Details)Wed, Oct 9, 3:51 AM

Sure. Happy to do either.

kaldari removed kaldari as the assignee of this task.Thu, Oct 10, 10:44 PM

@Jrbranaa - Great! Please add yourself as the session leader above and flesh out the description as needed.

kaldari assigned this task to Jrbranaa.Thu, Oct 10, 10:45 PM
kaldari updated the task description. (Show Details)Fri, Oct 11, 2:29 PM
Tgr added a subscriber: Tgr.Sun, Oct 13, 9:59 PM

Personally I am not a fan of the focus on team ownership. It is entirely possible for a developer community to have shared ownership of code, and IMO it's a better fit culturally. The problem is indeed the lack of incentives (fixing a problem in some random area of code means you are taking away time from the work you are going to be evaluated on, and the push for OKRs makes that even worse).

bd808 awarded a token.Tue, Oct 15, 2:47 PM