Hello! Andy Wingo <wi...@igalia.com> skribis:
> A fully distributed system sounds nice but it has costs too. In my mind > for a project of Guix's target size the best situation would be having > around 100 committers or so who have internalized the coding style and > patterns of Guix so that they can work more or less directly on the > parts they feel comfortable with, posting patches to the list as > necessary for feedback. Agreed. That’s the spirit of the text in ‘HACKING’. > An incoming patch would be assigned to one of those people based on > automatic tooling. In that way Guix can scale to the next step while > remaining a consistent, hackable project. That sounds like a good approach to me. With the upcoming libgit2 bindings, we could cook up a tool that gives people a list of likely reviewers that submitters could Cc, and suggest it in <https://www.gnu.org/software/guix/manual/html_node/Submitting-Patches.html>. Thanks, Ludo’.
