From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
72891@debbugs.gnu.org,
"Simon Tournier" <zimon.toutoune@gmail.com>
Subject: [bug#72891] [PATCH v2 3/3] doc: Define the purpose, membership, and creation of teams.
Date: Tue, 10 Sep 2024 09:20:21 +0900 [thread overview]
Message-ID: <87y140741m.fsf@gmail.com> (raw)
In-Reply-To: <87seueh350.fsf@pelzflorian.de> (pelzflorian@pelzflorian.de's message of "Thu, 05 Sep 2024 11:16:11 +0200")
Hi,
"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> writes:
> Hi! I agree with such additions; just some comments:
>
> Patch v2 1/3:
>
> Simon Tournier <zimon.toutoune@gmail.com> writes:
>> * doc/contributing.texi (Consensus Decision): New section.
>> Ccommit Access): Move consensus decision to its section.
>
> “Consensus Decision” is a single act of deciding.
> I guess lengthy “Consensus Decision Making” is the best
> section title.
>
> In the commit message, you wrote C instead of an opening parenthesis.
>
>
> Patch v2 3/3:
>
> Simon Tournier <zimon.toutoune@gmail.com> writes:
>> +large and seeking consensus before enacting decisions that would affect
>> +the entire community. Other said, teams provide feedback on patches
>> +touching its scope (@pxref{Reviewing the Work of Others}).
>
> “Other said” is close to a term we use in German, but in English better
> say something
> from <https://en.wiktionary.org/wiki/Thesaurus:in_other_words>.
I agree that "Other said" doesn't sound too natural in English (in the
sense that I've never heard it from native speakers -- disclaimer: I'm
not one). I believe Simon borrowed it from "autrement dit", which is
good French :-).
--
Thanks,
Maxim
next prev parent reply other threads:[~2024-09-10 0:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 10:12 [bug#72891] [PATCH RFC] doc: Define the purpose, membership, and creation of teams Ludovic Courtès
2024-08-31 6:26 ` Noé Lopez
2024-08-31 19:44 ` Ludovic Courtès
2024-09-04 17:26 ` Simon Tournier
2024-09-09 8:58 ` Ludovic Courtès
2024-09-09 17:48 ` Simon Tournier
2024-09-04 18:05 ` [bug#72891] [PATCH v2 1/3] doc: contributing: Move consensus Simon Tournier
2024-09-04 18:05 ` [bug#72891] [PATCH v2 2/3] doc: contributing: Move up section Teams Simon Tournier
2024-09-04 18:05 ` [bug#72891] [PATCH v2 3/3] doc: Define the purpose, membership, and creation of teams Simon Tournier
2024-09-05 9:16 ` pelzflorian (Florian Pelz)
2024-09-10 0:20 ` Maxim Cournoyer [this message]
2024-09-10 0:21 ` [bug#72891] [PATCH RFC] " Maxim Cournoyer
2024-10-14 12:14 ` bug#72891: " Ludovic Courtès
2024-10-14 17:37 ` [bug#72891] " Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y140741m.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=72891@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=pelzflorian@pelzflorian.de \
--cc=zimon.toutoune@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).