This is a potential area for work at Wikimedia-Developer-Summit-2016. "Collaboration" is about how we work together.
How do we scale editing our code up to populations similar to editing our projects, proportionally increasing our positive impact and productivity?
Main session in Robertson 1: Make code review not suck
Currently scheduled for Tuesday, January 5 at 2pm PST. Check the official schedule to confirm.
T114419: Event on "Make code review not suck": a very important discussion combined with @Aklapper's T101686: Goal: Define potential actions to reduce code review queues and waiting times & T78768: Agree on and implement actions to prioritize code review of patches submitted by volunteers
Goals for the session (copied from T114419)
- We have a number of ideas on how to fix the problem
- While we may not have decided which idea to implement, people come away from the meeting feeling that at least one of the ideas would fix things, and that there is hope for a brighter tomorrow.
- A summary of the ideas is presented to wikitech-l for further evaluation, in the hopes that the wikitech-l discussion will narrow down the choices to the best ones.
Plenary wrapup session: Tuesday, 3:40pm
- Results from the 2015 Community Wishlist Survey
- Summit retrospective
Recommended for breakout scheduling
- T114320: Code-review migration to Differential status/discussion: this is ongoing work, there is an RfC developing, and will have a big impact in our community.
Recommended for unconference
- T90908: Goal: Binding code of conduct for all Wikimedia technical spaces with consequences for breaches: even if it is a general topic, the unconference context might be more appropriate for a focused dicussion at this stage.
- T113490: 10 tips for communicating with communities when developing software: there hasn't been much discussion before the Summit, and people expressing their interest seem to want to "listen" more that be part of the effort for defining these tips. People motivated by this session could participate in the Unconference context, and then a Tech Talk could be produced with the final presentation.
- T114400: WikiBadge: very narrowed focus; people intersted can meet any time in the unconference setup.
In a limbo
- T89907: Discuss and approve a MediaWiki developer community governance model: very important topic, but the discussion hasn't moved much. If @RobLa-WMF wants to push for it, we will support him
- T115762: Shadow namespaces at the 2016 Wikimedia Developer Summit: for the reasons exposed at T119030#1851922, if @Legoktm wants to push for this, we will support him.
Other working areas (and the meta conversations about the idea of working areas) can/should be found here: T119018: Working groups/areas for macro-organization of RfCs for the summit