From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0.migadu.com ([2001:41d0:403:58f0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms13.migadu.com with LMTPS id YCCqDEub0WY8TQAAqHPOHw:P1 (envelope-from ) for ; Fri, 30 Aug 2024 10:13:31 +0000 Received: from aspmx1.migadu.com ([2001:41d0:403:58f0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0.migadu.com with LMTPS id YCCqDEub0WY8TQAAqHPOHw (envelope-from ) for ; Fri, 30 Aug 2024 12:13:31 +0200 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=debbugs.gnu.org header.s=debbugs-gnu-org header.b=kHJ0o55c; dkim=fail ("headers rsa verify failed") header.d=gnu.org header.s=fencepost-gnu-org header.b=EdvL3MNu; dmarc=pass (policy=none) header.from=gnu.org; spf=pass (aspmx1.migadu.com: domain of "guix-patches-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-patches-bounces+larch=yhetil.org@gnu.org" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1725012811; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding:resent-cc: resent-from:resent-sender:resent-message-id:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=6KMi5M2HsbVaDc7Y9cZyuBUkS3zFYbrlVfwJXLVRGzI=; b=QNDv+FpseN59UFv6lxQCMlhXLOTY0dI3lKeBWwYsHP31rxWWxJIoQYUK2/JWYbT8J6sd2V WVWi3VlBMAJdK38z+xFiuus4ZZUps+DgyFokaOw/OefJdSj62uUjekw557s6ZOMa8u25FS vFb/16rzl0TO0Fzaaqm4AkSpN0rLfI4gAEJ8PcC1f7Ur97ECgYgxHKsoWAbn31d8dOQj5p 0CGf6ISbH+2qGklZFPSM+K/Ag+fxu/lTFPVJyiQ/qMC8ct2eQ97EUCDSl1n8U6P7cNNCmU kxcG3SVMk5y0GsZbz/RqGKsHhXYoHmeK3ezmDUzmzWdfhe5B23ARS0P1ehsmbA== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1725012811; a=rsa-sha256; cv=none; b=fr5UnjhTlmUdkt9XFQp3ZyANIxlwfGz9EuSOldRMkUijSvJ511E82wVMwPA+sH+SBj+Q+4 p+52fk3l/o8xcSXLwnDCEuCHHZxpm7yXLli2znGiNfgIADi5HniUQgZQKIUZp3yL5edxCQ J0+V4vNvlA0LCv0eEajZ0HRAgOdUrur9d1TtAxKmUROo3pG2F450dCj/6BWW1P1OOnKlGq xbAKdwELasl3Ok2JVSV2RIAIaa91mecp/tjN+bAnwuwCCMMY3x1TXKa8RSc9vLrhimiSDP F4zmQpCg1k89G/B3xRxxMbmgjsTubpgCP3FGqMJJVB+WHYFBuZT2M0YkmfUUEA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=debbugs.gnu.org header.s=debbugs-gnu-org header.b=kHJ0o55c; dkim=fail ("headers rsa verify failed") header.d=gnu.org header.s=fencepost-gnu-org header.b=EdvL3MNu; dmarc=pass (policy=none) header.from=gnu.org; spf=pass (aspmx1.migadu.com: domain of "guix-patches-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-patches-bounces+larch=yhetil.org@gnu.org" Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 826827127F for ; Fri, 30 Aug 2024 12:13:30 +0200 (CEST) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sjycx-0003ud-IQ; Fri, 30 Aug 2024 06:13:11 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sjycv-0003uO-Cb for guix-patches@gnu.org; Fri, 30 Aug 2024 06:13:09 -0400 Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1sjycu-00085Z-Op; Fri, 30 Aug 2024 06:13:08 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debbugs.gnu.org; s=debbugs-gnu-org; h=MIME-Version:Date:From:To:Subject; bh=6KMi5M2HsbVaDc7Y9cZyuBUkS3zFYbrlVfwJXLVRGzI=; b=kHJ0o55c8cpM2QjI1A4EQjuteLxUdHrJ5C5F+Mbf0ZmI+mqs6WGZDhooBLzuPgeeAcmCOHaZb62ZmctBgAs9g2ktrpzFP5NFL15kZq1nkhjI3+5T3KyytHwcCyFZaAZR5tg58n5L0oLkgggF8XzdCm9zZi/awrZ7vg7J4cOr6C+AaHqxhL52kZkci1NHLtOGn+WFPGyhcgHG5hTKSggZ7mzy6HPy2en5Sc+2ZoIV+j53iWVjOejp2DY8z+3hdhpiQuXvrKatbCE5t/qOsAUMV2Z0/k4kgSKuQ5MtPhKPG02ZecG3+4yDNT1lPAGNwzRXg5snEJXtpOsRm731TpHCQg==; Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1sjydm-0007wl-KN; Fri, 30 Aug 2024 06:14:02 -0400 X-Loop: help-debbugs@gnu.org Subject: [bug#72891] [PATCH RFC] doc: Define the purpose, membership, and creation of teams. Resent-From: Ludovic =?UTF-8?Q?Court=C3=A8s?= Original-Sender: "Debbugs-submit" Resent-CC: pelzflorian@pelzflorian.de, ludo@gnu.org, maxim.cournoyer@gmail.com, guix-patches@gnu.org Resent-Date: Fri, 30 Aug 2024 10:14:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: report 72891 X-GNU-PR-Package: guix-patches X-GNU-PR-Keywords: patch To: 72891@debbugs.gnu.org Cc: Ludovic =?UTF-8?Q?Court=C3=A8s?= , Florian Pelz , Ludovic =?UTF-8?Q?Court=C3=A8s?= , Maxim Cournoyer X-Debbugs-Original-To: guix-patches@gnu.org X-Debbugs-Original-Xcc: Florian Pelz , Ludovic =?UTF-8?Q?Court=C3=A8s?= , Maxim Cournoyer Received: via spool by submit@debbugs.gnu.org id=B.172501281730491 (code B ref -1); Fri, 30 Aug 2024 10:14:02 +0000 Received: (at submit) by debbugs.gnu.org; 30 Aug 2024 10:13:37 +0000 Received: from localhost ([127.0.0.1]:52544 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1sjydN-0007vj-0L for submit@debbugs.gnu.org; Fri, 30 Aug 2024 06:13:37 -0400 Received: from lists.gnu.org ([209.51.188.17]:58954) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1sjycw-0007p3-8I for submit@debbugs.gnu.org; Fri, 30 Aug 2024 06:13:35 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sjyc0-0003rU-SH for guix-patches@gnu.org; Fri, 30 Aug 2024 06:12:13 -0400 Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sjybz-0007zl-NB; Fri, 30 Aug 2024 06:12:11 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-Version:Date:Subject:To:From:in-reply-to: references; bh=6KMi5M2HsbVaDc7Y9cZyuBUkS3zFYbrlVfwJXLVRGzI=; b=EdvL3MNuTVtYW2 lX9U9FLGKRdxTYvhSkMRowkxeMyy4WuzOtMAcytJWGhHhJlw93BQjgooxsb4FNP8sokaB7uJ7lMxp B8s66aZVKAgE3jcpf4uW9UJ06e2lDSUvQwibnDELZ9gUmcsRxIZKNnsmiFHAQ6kMmEnQdqKDwOTca sCTi6mSuhiJpFOMUsB4ugySJZV+mrrszuNCG4ZGe0wvmXuK4zxeUfLAUy4pbLLbmaUnJpQ6yBj+H2 c7CTQT1TlNsQSXYEGc9/U4B7ZkSSIxMet2rEyH8RBS2XUx0uy6lJAcnqd4P1wiUMfPGJNKmh5YDfH 7+A3c7ZFscAJsF7AWrDA==; From: Ludovic =?UTF-8?Q?Court=C3=A8s?= Date: Fri, 30 Aug 2024 12:12:04 +0200 Message-ID: X-Mailer: git-send-email 2.45.2 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: guix-patches@gnu.org List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+larch=yhetil.org@gnu.org Sender: guix-patches-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US X-Migadu-Spam-Score: -0.78 X-Spam-Score: -0.78 X-Migadu-Queue-Id: 826827127F X-Migadu-Scanner: mx11.migadu.com X-TUID: i/MhYYZRiy5b * 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(-) Hello Guix! The recent discussion about creating a browser team¹ made it clear that teams are not defined anywhere: the manual doesn’t say what their mission is, how to become a member, how to revoke members, nor how to create new teams. This patch is an attempt to formalize that. I believe there’s nothing really new for someone who’s been following closely in recent times, but it should definitely improve legibility for newcomers. Thoughts? I suggest that we iterate on this for at most one month so we have a first version checked in by September 30th. Ludo’. ¹ https://lists.gnu.org/archive/html/guix-devel/2024-08/msg00168.html diff --git a/doc/contributing.texi b/doc/contributing.texi index 73f7addbef..7705367bce 100644 --- a/doc/contributing.texi +++ b/doc/contributing.texi @@ -2225,8 +2225,52 @@ Teams @subsection Teams @cindex teams -There are several teams mentoring different parts of the Guix source -code. To list all those teams, you can run from a Guix checkout: +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. + +As an example, the Python team is responsible for core Python packaging +matters; it can decide to upgrade core Python packages in a dedicated +@code{python-team} branch, in collaboration with any team whose scope is +directly dependent on Python---e.g., the Science team---and following +branching rules (@pxref{Managing Patches and Branches}). The +Documentation team helps review changes to the documentation and can +initiate overarching documentation changes. The Translations team +organizes translation of Guix and its manual and coordinates efforts in +that area. The Core team is responsible for the development of core +functionality and interfaces of Guix; because of its central nature, +some of its work may require soliciting input from the community at +large and seeking consensus before enacting decisions that would affect +the entire community. + +Teams are defined in the @file{etc/teams.scm} file in the Guix +repository. The scope of each team is defined, when applicable, as a +set of files or as a regular expression matching file names. + +@cindex team membership +Anyone with interest in a team's domain and willing to contribute to its +work can apply to become a member by contacting current members by +email; commit access is not a precondition. Membership is formalized by +adding the person's name and email address to @file{etc/teams.scm}. +Members who have not been participating in the team's work for one year +or more may be removed; they are free to reapply for membership later. + +@cindex team creation +One or more people may propose the creation of a new team by reaching +out to the community by email at @email{guix-devel@@gnu.org}, clarifying +the intended scope and purpose. When consensus is reached on the +creation of this team, someone with commit access formalizes its +creation by adding it and its initial members to @file{etc/teams.scm}. + +To list existing teams, run the following command from a Guix checkout: @example $ ./etc/teams.scm list-teams @@ -2234,15 +2278,12 @@ Teams name: Mentors description: A group of mentors who chaperone contributions by newcomers. members: -+ Christopher Baines -+ Ricardo Wurmus -+ Mathieu Othacehe -+ jgart -+ Ludovic Courtès ++ Charlie Smith @dots{} @end example -You can run the following command to have the @code{Mentors} team put in +@cindex mentoring +You can run the following command to have the Mentors team put in CC of a patch series: @example @@ -2905,12 +2946,14 @@ Reviewing the Work of Others is to review the work contributed by others. You do not need to be a committer to do so; applying, reading the source, building, linting and running other people's series and sharing your comments about your -experience will give some confidence to committers. Basically, you must +experience will give some confidence to committers. You must ensure the check list found in the @ref{Submitting Patches} section has been correctly followed. A reviewed patch series should give the best chances for the proposed change to be merged faster, so if a change you would like to see merged hasn't yet been reviewed, this is the most -appropriate thing to do! +appropriate thing to do! If you would like to review changes in a +specific area and to receive notifications for incoming patches relevant +to that domain, consider joining the relevant team(s) (@pxref{Teams}). @cindex reviewing, guidelines Review comments should be unambiguous; be as clear and explicit as you base-commit: d5312370b46ace47e138d84e1bb28e5651cee94b -- 2.45.2