Re: Translating the Emacs manuals (a summary)

[Eli Zaretskii <eliz@gnu.org>]

> Date: Sat, 20 Jan 2024 04:37:05 +0000
> From: Jean-Christophe Helary <jean.christophe.helary@traductaire-libre.org>
> Cc: emacs-devel@gnu.org
> 
> > On Jan 20, 2024, at 4:54, Eli Zaretskii <eliz@gnu.org> wrote:
> > 
> >> Date: Fri, 19 Jan 2024 18:00:34 +0000
> >> From: Jean-Christophe Helary <jean.christophe.helary@traductaire-libre.org>
> >> Cc: help-texinfo@gnu.org
> >> 
> >> I’m trying here to make a summary of the discussions that we’ve had so far, in the hope of being able to propose a proper readme file at some point in the close future.
> >> 
> >> I hope I've not forgotten anything.
> > 
> > Looks fine to me, thanks.
> 
> (I am making amendments at the moment and that triggers a few extra questions.)
> 
> What about people who do not have commit rights to the repository?
> Can they send a file to the list and ask for it to be committed to a review branch?

They can send a file or they can send a patch, yes.  Patches are
preferable, especially if they are in "git format-patch" form, because
they allow easier review and easier installation of the changes by
someone with write access.

Also, if we are talking about such fine details, let's not forget that
changes should be always posted for review, no matter if the author
does or doesn't have write access to the repository.  This is
especially important in this case, since many contributors are likely
to be unaware of our coding, documentation, and commenting
conventions, and so patch review is an important part of making sure
the results comply to our conventions.