Ensure that Community Contributions are picked up by the team promptly
Problem statement
Even with the current #mr-coach, Community contribution and #mr-coach slack channel, We are still not responding to our community's contribution in a timely manner.
This issue was recently raised by our contributor and was captured in twitter.
- Slack https://gitlab.slack.com/archives/C3JJET4Q6/p1536999453000100
- Twitter https://twitter.com/msdundar/status/1040669415816265729
The Quality team plans to address the triage portion with automated tooling. gitlab-org/quality/triage-ops#3 (closed)
- Distributing MRs triaging to multiple team's in engineering.
- The triage package issue would contain issues/MRs to be triaged.
- The triage package issue would be created weekly and assign to each engineering team.
- Each engineering team is responsible to triage the given list. (Limited to just 10-5 per team per week)
However this only solves the triage portion. We also need to ensure that the relevant engieers are looking at the MR after the label has been applied.
From https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/20941#note_91794091 we still do not have any activity in the MR after applying Community contribution and team label for a month.
Proposal
Given that we have a steady influx of community contributions we want to process this as soon as we can to encourage more contributions.
How can we speed up the time to merge for Community contribution ?
Ideas to help speed this up include. Moved to track in epic gitlab-org/quality&6 (closed)
- Tighten the feedback loop for stale MRs notification.
- Reduce this to 1 month https://gitlab.com/gitlab-org/quality/triage-ops/blob/master/.triage-policies.yml#L387
- Ensure that each team is watching MRs tagged by Community contribution
- Define a dedicated mr coach from each team
- Implement average time to merge for Community contribution and have this tracked per team.
/cc @gl-quality