Alice Kober-Sotzek, Ben Rohlfs, Luca Milanesio, Patrick Hiesel
Online, August 4, 12:30 - 13:00 CEST
The next meeting will be held on September 1, 12:30 CEST.
Luca has been working in updating the Gerrit screenshots on the homepage. Further work will also include the updates on the Gerrit documentation, so that the Gerrit project would not look outdated anymore.
As a follow-up, the screenshots layout in the homepage should be redesigned as they are today too small and difficult to read.
Luca presented the proposal of adding the ability to flag comments in a code-review, coming from a discussion with the CMs. The new feature would allow to filter out comments that are out of scope or inappropriate.
The Go project is big enough to have similar needs and it seems they do not need the flagging feature.
The general consensus is to NOT have the flagging feature in Gerrit, as it won't be practical because of:
Currently, all issues reported on GerritHub.io are ending up to Ben's backlog, which causes some overload and incorrect assignment to the PolyGerrit Team.
Luca proposed to create a proper template that would assign the issues to the GerritForge Team and will have the host label set to gerrithub.io, similarly to what happens today with Googlesource.com. The proposal is accepted.
The Google team proposed to help David Pursehouse in brainstorming items for the Gerrit Projects News page. Patrick checked internally and Youssef has agreed to take this on from now.
The Google team has presented the results of the discussions with Qualcomm on the proposal of having a new “robot” flag in the account settings, with the counter-proposal of defining a global capability that could be assigned to groups.
Gerrit already has the Non-Interactive Users group that could be potentially reused for this purpose, but there are performance implications because the group resolution could be potentially slow.
Patrick will think this through once more and follow up via email.
No new issues.