Ekaitz Zarraga <eka...@elenq.tech> writes: > On 2025-03-04 18:19, Ricardo Wurmus wrote: >> >> The AGit flow: >> >> - clone the upstream repository >> - checkout a new branch >> - make a commit >> - push the commit as a PR to the forge. > > Yes but no. > It's easy, but if we are going to make any contributor do that, we are > still going to need documentation and people will come and complain. > > Isn't the email based workflow as simple as: > > - clone the upstream repository > - make commits > - send email
Here’s my point of view: - clone the upstream repository - make commits - format patches - configure git send-mail - …or find out which addresses to send the mail and who to cc with etc/teams.scm - send email Which is more complicated than the AGit flow IMO. And we will need documentation on how to contribute no matter which way we choose. What I especially like about the AGit flow is that it just uses git, which is a common factor. No need for an alternate patch format, or email. Cheers, Noé
signature.asc
Description: PGP signature
