Currently, there is no streamlined process for watching new developer patches that land in Gerrit. And, this is why it is cumbersome to offer help to new authors or reviewers who might need it in this area.
Developer Relations relies on [[ https://wikimedia.biterg.io/ | wikimedia.biterg.io ]] for obtaining names and dates of new authors who submitted their very first changeset into Gerrit. But, this as of now is blocked by a technical upstream constraint: T151161. Until late 2016, attempts have been made to send requests for code review to Wikitech-I, but then migrating from korma.wmflabs.org to wikimedia.biterg.io (both provided by Bitergia) affected this process.
We also have an [[ https://www.mediawiki.org/wiki/Gerrit/Reports/Open_changesets_by_newbie_owner | Open changesets by newbie owner ]] script, that provides direct links to Gerrit. But, the way it is right now, it is of little use to us. It is not regularly updated, does not provide an option to view patches within a specific date range, also lists those authors whose changesets were taken care by others later, or were submitted about years ago.
# An easy and quick solution would be to improve the script or wait for the following issue to get resolved: T151161.
# A refined workflow could consist of two parts (which makes the job of DevRel's and others easier):
- A tool (possibly leveraging [[ https://github.com/mzmcbride/gerrit-reports/tree/master/reports | mzmcbride/gerrit-reports ]]) that would help:
- view/monitor new volunteer patches (e.g. view patches within a specific date range)
- maintain workflow for reviewing patches (e.g. able to mark patches considered as done)
- Facilitation around the tool that could consist of:
- Connecting code review seekers with reviewers
- Directing new authors to follow [[ https://www.mediawiki.org/wiki/Gerrit/Code_review/Getting_reviews | Getting reviews ]] guidelines
- Directing reviewers to best [[ https://www.mediawiki.org/wiki/Gerrit/Code_review | code reviewing practices ]]
- Helping teams use the workflow to monitor patches submitted in their own area
- Making more teams aware that Gerrit (cross-repository) dashboards exist and [[ https://www.mediawiki.org/wiki/Gerrit/Advanced_usage#Gerrit_project_dashboard | how to set up Gerrit dashboards ]]
- Understand how other teams have monitored patches in the past or what practices they have adapted to get better at code review so that we can share them with others more widely.
# <add your idea here>
* Source for the script "Open Changesets by newbie owners": https://github.com/mzmcbride/gerrit-reports/tree/master/reports