Hi Leo,
On Thu, 06 Feb 2025 at 14:39, Leo Famulari <l...@famulari.name> wrote:
> On Thu, Feb 06, 2025 at 04:40:03PM +0100, Simon Tournier wrote:
>> Sorry if my understanding is incorrect, but if we do not increase the
>> number of people with specific/dedicated/controlled write access, the
>> move to Codeberg is useless. Provocative on purpose. ;-)
>
> There are other problems with our email workflow besides "not enough
> people are committers". Although I agree we should be creative about
> empowering more people, like with branch-based permissions.
I agree. I was reacting on Ludo’s answer [1]:
I believe we want to keep the number of committers relatively small, for
security reasons.
At Guix Days, we had a session about Reviewing and in a summary, the
pitch introducing the session and the closing words seems very similar.
Something we already know and already discussed at length. :-)
1. Tooling
2. Expectations (from Submitter and from Reviewer)
3. Incentives
One alone is not enough.
My point is that we need to take the opportunity to also re-think what
means Committer, Team member, etc. and the implications about write
access and “duties”.
> For me, the big problem with email is that resolved tickets don't get
> removed from my inbox. Currently, my guix-patches inbox has 7000
> messages. And 520 for bug-guix. Since April 2024.
Bah that’s the same with Codeberg notifications. :-) And if not
notified, using my web-browser, I will never go further than page 1 or 2
of the still open Pull Requests. Just for the record, nixpkgs has more
than 5k+ open PRs.
https://github.com/NixOS/nixpkgs/pulls
> improving our workflow with helper scripts and services, and that still
> haven't satisfied the Guix contributors... or we could try something
> new.
Do not take me wrong: I agree that the “emails workflow“ has drawback
and limitations.
I think that whatever the tool, the issue isn’t the tool itself but the
volume and the scale. Not so far from now, I was able to give a look to
(almost) all emails (patches included) sent to any Guix mailing lists;
Today, I mark full threads as read and when I miss a couple of days, I’m
dead! :-)
And the volume will be probably even higher when running Codeberg.
All in all, the two important questions, IMHO:
1. When collaborating via a forge as Codeberg, is it aligned with all
the principles and values we advocates as a project? What is the
trade-off?
2. Does it the fit the workflow of people who concretely review and
push code from other? And if I read correctly your messages,
yes. :-)
Cheers,
simon
1: Re: [GCD] Migrating repositories, issues, and patches to Codeberg
Ludovic Courtès <l...@gnu.org>
Tue, 04 Feb 2025 11:11:35 +0100
id:87o6ziyq7c....@gnu.org
https://lists.gnu.org/archive/html/guix-devel/2025-02
https://yhetil.org/guix/87o6ziyq7c....@gnu.org
