There is a proposed WikiDev16 session about improving code review, especially for volunteers: T114419: Event on "Make code review not suck". You are welcome to comment there if interested.

I've changed the task summary by prefixing "Agree on and implement actions to..." and removed DevRel-December-2015 here as this task is blocked by T101686: Goal: Define potential actions to reduce code review queues and waiting times (to be finished in December) and hence will not get fixed in December 2015.

T123753: Establish retrospective reports for #security and #performance incidents may be a useful prerequisite for this goal.

This task was one of the T119387: Community Liaison and Developer Relation quarterly goals for January - March 2016. We have missed it as it was formulated. @Aklapper could you formulate the current status and the progress during the past quarter, please?

Meh. Not sure why I renamed this task on Dec 29. Reverting back to old title.

Potential actions (a blocker for this task) were successfully identified in T101686 - I added them as blockers to this task, regarding their implementation.

Defining and proposing potential actions

• The tasks under "Blocked By" are action items that were successfully identified in T101686: Goal: Define potential actions to reduce code review queues and waiting times:
  • T129842: Launch the Wikimedia Code Review Working Group
  • T129067: Document a structured, standardized approach for reviewing code contributions
  • T129068: Improve code contribution guidelines for patch authors
  • T115852: Fix unclear maintenance responsibilities for some parts of MediaWiki core repository
  • T128370: Update ownership list on [[mw:Developers/Maintainers]]
  • T128371: Set up Code Review office hours
  • T128372: Document use of Owners in Phabricator and advertise it

Agreeing on actions

Regarding the "agree on" part of this very task, this was done by the following steps:

• The technical community was asked on wikitech-l@ for input on the tasks listed under "Blocked By".
• A heads-up about the wikitech-l@ thread was sent to engineering@.
• Team-Practices was also asked for input but it is out of scope for them.
• These action items were also brought up in the Wikimedia Developer Summit session in January 2016 (T114419) which could be considered agreement (at least for those physically attending that session)

Implement actions

The "implement" part was clearly not done in Jan-Mar 2016, though some work has been started in specific tasks with defined owners. Some tasks still miss owners and miss a clear way forward, e.g. T115852.

Obviously we have identified actions to improve the code review situation in general, so everybody should benefit from future improvements regardless of their affiliation, not only volunteers contributing patches (though they are still our main focus).

Regarding involvement of Developer-Advocacy specifically, T129068: Improve code contribution guidelines for patch authors and T129067: Document a structured, standardized approach for reviewing code contributions are @Aklapper's personal goals for the April - June 2016 quarter.
Until T129842 is resolved it's not entirely clear how much the Developer-Advocacy team will be involved in actually driving all (emphasis by me) these action items.

[Task is blocked by numerous tasks hence not convinced whether punting this to yet another quarter helps anybody. And this is marked as Tracking-Neverending. Hence setting generic team project instead of milestone.]

Removing Team Practices because we're not sure how we could help with this in the near term. If you have a specific request for us, please see: https://www.mediawiki.org/wiki/Team_Practices_Group/How_To_Engage_With_TPG

From T156120: Update gerrit to 2.14.6:

You can now set an assignee for changes.

From one of the sub tasks I have published a blog explaining the Gerrit review by blame plugin as well as other manual way to find reviewers: J139: Blog Post: Gerrit now automatically adds reviewers. That would help to at least get some reviewers on changes since they are now added automatically by Gerrit.

Our speed reviewing patches is not impressive, and this is a problem difficult to solve.

Is this data available in another tool (bitergia perhaps)? The one linked in the task description (http://korma.wmflabs.org/browser/gerrit_review_queue.html) is no longer available. I'm particularly interested to see this data for specific repositories, if possible.

@kostajh: It depends on which exact data you're looking for. :) https://www.mediawiki.org/wiki/Community_metrics#Time_to_first_review_for_Gerrit_patches_per_repository and the following section might provide some insights.
The "Organizations" widget lets you filter for author_org_name:"Independent"; the "Repositories" widget allows filtering for repository:"mediawiki/extensions/Examples".

In T78768#7489406, @Aklapper wrote:

@kostajh: It depends on which exact data you're looking for. :) https://www.mediawiki.org/wiki/Community_metrics#Time_to_first_review_for_Gerrit_patches_per_repository and the following section might provide some insights.
The "Organizations" widget lets you filter for author_org_name:"Independent"; the "Repositories" widget allows filtering for repository:"mediawiki/extensions/Examples".

That's useful, thanks!