From: Simon Tournier <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 72891@debbugs.gnu.org, Florian Pelz <pelzflorian@pelzflorian.de>,
Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: [bug#72891] [PATCH RFC] doc: Define the purpose, membership, and creation of teams.
Date: Wed, 04 Sep 2024 19:26:53 +0200 [thread overview]
Message-ID: <87plpjwcrm.fsf@gmail.com> (raw)
In-Reply-To: <fb9721adfc71b841dcb6a2575539449ce756e401.1725012038.git.ludo@gnu.org> ("Ludovic Courtès"'s message of "Fri, 30 Aug 2024 12:12:04 +0200")
Hi,
On Fri, 30 Aug 2024 at 12:12, Ludovic Courtès <ludo@gnu.org> wrote:
> * doc/contributing.texi (Teams): Define the purpose of teams; provide
> example; clarify membership and team creation.
> (Reviewing the Work of Others): Link to “Teams”.
>
> Change-Id: I5d75f69bc4653eb9da9c1d1f920718238ea83b9d
> ---
> doc/contributing.texi | 63 ++++++++++++++++++++++++++++++++++++-------
> 1 file changed, 53 insertions(+), 10 deletions(-)
This patch LGTM modulo minor comments.
( Aside, I am less and less comfortable to have a manual that collects
our practises instead of separated documents. Anyway. :-) )
> +To organize work on Guix, including but not just development efforts,
> +the project has a set of @dfn{teams}. Each team has its own focus and
> +interests and is the primary contact point for questions and
> +contributions in those areas. A team's primary mission is to coordinate
> +and review the work of individuals in its scope (@pxref{Reviewing the
> +Work of Others}); it can make decisions within its scope, in agreement
> +with other teams whenever there is overlap or a close connection, and in
> +accordance with other project rules such as seeking consensus.
> +@c TODO: Currently ``consensus-based decision making'' is discussed
> +@c under ``Commit Access''. Move that elsewhere and refer to it from
> +@c here.
If we are at it. I think this “section Teams” should be moved to its
own section and not a subsection of “Submitting Patches”.
The “consensus” should also move to its own section.
See v2 for a proposal.
> +As an example, the Python team is responsible for core Python packaging
[...]
> +To list existing teams, run the following command from a Guix checkout:
What is missing between the brackets [...] is a link to “Reviewing the
work of others”. Somehow, I would add a sentence clarifying “its work”.
For instance, I propose a last sentence in the paragraph:
--8<---------------cut here---------------start------------->8---
As an example, the Python team is responsible for core Python packaging
[...]
the entire community. Other said, teams provide feedback on patches
touching its scope (@pxref{Reviewing the Work of Others}).
--8<---------------cut here---------------end--------------->8---
Cheers,
simon
next prev parent reply other threads:[~2024-09-04 17:58 UTC|newest]
Thread overview: 13+ 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:25 ` bug#72891: " Simon Tournier
2024-09-04 17:26 ` Simon Tournier [this message]
2024-09-09 8:58 ` [bug#72891] " 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
2024-09-10 0:21 ` [bug#72891] [PATCH RFC] " Maxim Cournoyer
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87plpjwcrm.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=72891@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=maxim.cournoyer@gmail.com \
--cc=pelzflorian@pelzflorian.de \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.