Hi Distopico,
You raise several valid points.
I think there have been improvements with the move to Codeberg, notably:
• People from the right team are notified on each contribution and
there’s a team label set on issues/pull requests that makes it
easier to see items in one’s scope.
• One can subscribe/unsubscribe to issues and pull requests with very
fine grain, which helps keep track of things that matter.
• Milestones do help coordinate on higher-level goals:
https://codeberg.org/guix/guix/milestones
• CI is not new (qa.guix.gnu.org was doing a good job before the move
to Codeberg) and it’s not perfect either, but having feedback
straight in pull requests probably helps reviewers and contributors
get a clearer view of the situation.
But you’re right that tooling is not everything and the problem of
overwhelmed reviewers largely remains.
I think, as Tomas suggested before, that organizing team meetings (IRC
or video) like the release team has been doing can help focus and find
the energy to do things. And of course, recruiting more people to join
teams and ensuring rotation of active members would help.
Thanks,
Ludo’.
