Hello, Ricardo Indeed, I trust that over the years you and others must have tried their best.
> Or they *do* Cc the team, but the email drowns in all the other Guix emails > and I have no way of listing all patches affecting my field of > responsibility, etc. This I agree with, after being part of teams, I had been looking for such methods. One way is to get patches which mention the branch name (Rust Team, Emacs Team etc.) but maybe we should have also another tag in the subject every time it's directed to a team? Akin to labels in a web-based setup. Also, since you and others have had such experience with these tools, I'd like some suggestions from you and everyone else on what Savannah and FSF can do to have the workflow smoother. I believe the "learning curve" issue is irrelevant to this, but mostly infrastructure wise, what can be improved/repaired/maintained better? I ask this because I'm slowly taking responsibilities at FSFSysOps and Savannah. I communicated with the FSFSysOps team last night, and they're open to working on improvements. While of course, I'm not suggesting Guix to rely on this or wait for it, I'm simply asking what we can learn from this to go forward in having other GNU projects to be better. Thank you. Regards, Divya Ranjan Divya Ranjan, Mathematics, Philosophy and Libre Software
