From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2.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 6FWGGC5bDWdSTgEAe85BDQ:P1 (envelope-from ) for ; Mon, 14 Oct 2024 17:55:58 +0000 Received: from aspmx1.migadu.com ([2001:41d0:403:58f0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2.migadu.com with LMTPS id 6FWGGC5bDWdSTgEAe85BDQ (envelope-from ) for ; Mon, 14 Oct 2024 19:55:58 +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=pUhmjejZ; dkim=fail ("headers rsa verify failed") header.d=gnu.org header.s=fencepost-gnu-org header.b=RXY2eLGw; 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"; dmarc=pass (policy=none) header.from=gnu.org ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1728928558; 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:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=kjAP/5XlmvB1Dp2SaQOa0spYa6ltXgStEdblPyiWDsM=; b=lFYHeiNfE8xaiKKuHoED6QohBhe67MK/2lGY6HXardIm0yuw6o5B0Dq5h+sSJAzxJJIZ/v q5TKF4LQxbNZ2dTpxyyo/apRrKHwYgHzcjIs0Y9yEuVIDc/1p9lP710uH4H8dGGpUh6lsE rPEc1N6hLw2l9Scv3EbOg9wQJHSLbQ1auIb/L9ZI8MVGsIVVm4wjV8TluVaXFGM2aCtPWK K/nd8kDk49W4Hn5OcGRREc3sp5IeP/lUo5fYQXbbcGT+cboBqp2luf9uJD0pZIlDLnd8Ph kcLoFZa90ZiHjxX/kYfuXtxqYOb1ruNsJRNE9e6YopsQbVwR1GaPLXEXXzU+WA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=debbugs.gnu.org header.s=debbugs-gnu-org header.b=pUhmjejZ; dkim=fail ("headers rsa verify failed") header.d=gnu.org header.s=fencepost-gnu-org header.b=RXY2eLGw; 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"; dmarc=pass (policy=none) header.from=gnu.org ARC-Seal: i=1; s=key1; d=yhetil.org; t=1728928558; a=rsa-sha256; cv=none; b=sBuAwVRKs3LHJ6gwzWt+1skl6ayTrBY548bZaS/lOm8txLoZYs9WGWHtWAvP2PiM6wpGZL R7Abwos2p3xdJNHQhU1PgdpihjRS+aglhmnKLAZF2h+PCT2m5w2DZnP92SRuA8/9s/BkLv 7Ei4MY8EZS5fkwXWzvpCyMXZLHzfN4ewecWoB4BtRRz3Ooy/spbJgcyMEaPCgCmtCn0Jbw UuSsRZjMD685j7rLalZSaripp6+NRnaCBEolca7NrcsM4Z3Rd1Z6FLHFRambQVDS8+BBtf JFjPqqQ3m1vSCkwYpdtD+kmBVnV6swmdMv/+44Z2NrJFSD0LazM7uQQm+paCfg== 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 E6EAE4054C for ; Mon, 14 Oct 2024 19:55:57 +0200 (CEST) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1t0PIJ-0007DZ-8Z; Mon, 14 Oct 2024 13:55:47 -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 1t0PII-0007DQ-5T for guix-patches@gnu.org; Mon, 14 Oct 2024 13:55:46 -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 1t0PIH-0002nL-5n; Mon, 14 Oct 2024 13:55:45 -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:References:In-Reply-To:Date:From:To:Subject; bh=kjAP/5XlmvB1Dp2SaQOa0spYa6ltXgStEdblPyiWDsM=; b=pUhmjejZ7kWrEXo7ycspY6ahZ69/LPY7dIFAr5TMHz/to7Rqz64wWTs2Y1YanN956RtmDraPVfEPhE6MBzQqAN+d8UvO/65Ktw2w6WJ72pN/+Em503dwCsMSrTrvpr/xlslBt+UgZ+uKgkuoDgz0zhCAelK7Eics00sA80fqTnz3sCG1J6MG3IaNSl4v0YNGmxOeD/mv05gEN+Kt0SWHoW5jFUMiipvdVe0AjJR6f0K0A6dGv3nklHb3KlZM1JbqG8pt13/QP19Yw84fVYyLSPCkYs3vcEMtzCTmvfV22PhYMSOgXdPBPDlZAsWYbQoYVWe/MgRC/OH6eloYM1STNw==; Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1t0PIY-0005IW-6I; Mon, 14 Oct 2024 13:56:02 -0400 X-Loop: help-debbugs@gnu.org Subject: [bug#73803] [PATCH 2/2] doc: Promote =?UTF-8?Q?=E2=80=9CTeams=E2=80=9D?= section. Resent-From: Ludovic =?UTF-8?Q?Court=C3=A8s?= Original-Sender: "Debbugs-submit" Resent-CC: ludo@gnu.org, maxim.cournoyer@gmail.com, guix-patches@gnu.org Resent-Date: Mon, 14 Oct 2024 17:56:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 73803 X-GNU-PR-Package: guix-patches X-GNU-PR-Keywords: patch To: 73803@debbugs.gnu.org Cc: Ludovic =?UTF-8?Q?Court=C3=A8s?= , Ludovic =?UTF-8?Q?Court=C3=A8s?= , Maxim Cournoyer X-Debbugs-Original-Xcc: Ludovic =?UTF-8?Q?Court=C3=A8s?= , Maxim Cournoyer Received: via spool by 73803-submit@debbugs.gnu.org id=B73803.172892851419863 (code B ref 73803); Mon, 14 Oct 2024 17:56:02 +0000 Received: (at 73803) by debbugs.gnu.org; 14 Oct 2024 17:55:14 +0000 Received: from localhost ([127.0.0.1]:44122 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1t0PHl-0005AI-7I for submit@debbugs.gnu.org; Mon, 14 Oct 2024 13:55:13 -0400 Received: from eggs.gnu.org ([209.51.188.92]:44630) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1t0Owf-0003fK-F6 for 73803@debbugs.gnu.org; Mon, 14 Oct 2024 13:33:26 -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 1t0Ou6-0008AF-6u; Mon, 14 Oct 2024 13:30:52 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-Version:References:In-Reply-To:Date:Subject:To: From; bh=kjAP/5XlmvB1Dp2SaQOa0spYa6ltXgStEdblPyiWDsM=; b=RXY2eLGwsHqe0qvlSiob oBLNzW4R2o2i0tXPOryasO8LDCaJTmzifs8PBrudzroYTKiRjGJ9RILpWRuIww5b1P9CI8Ma2hUZm QPleEHhU4FeeGFerHW7x1RZpgIL5jvlmqUXUeF/f5kP1EdgkR+kgnqMoSw5pMEczs+/dKwRl8/jBz PvJNLU3ZwerM2L7YcQZtKKjvwC1uCiOYtajyJpAHOjs08yMgdifNYexkItcAb4xmwcheUZKZ7B6sb O/9PNvVUcLEx2DNPf0HX5V/58iZCC7JuoVkr0ePhMCq8kVf4lJHvKby5E70167i9KxcVgsNOHZqCO YS5xZBRsRBiNyQ==; From: Ludovic =?UTF-8?Q?Court=C3=A8s?= Date: Mon, 14 Oct 2024 19:30:37 +0200 Message-ID: X-Mailer: git-send-email 2.46.0 In-Reply-To: References: 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-Country: US X-Migadu-Flow: FLOW_IN X-Migadu-Scanner: mx11.migadu.com X-Migadu-Spam-Score: 2.27 X-Spam-Score: 2.27 X-Migadu-Queue-Id: E6EAE4054C X-TUID: whfjWIYeYYPe Suggested by Simon Tournier . * doc/contributing.texi (Teams): Move from subsection of “Submitting Patches” to section of “Contributing”. Change-Id: Id21be29380fc981e74a5025b1467eebde8566726 --- doc/contributing.texi | 156 +++++++++++++++++++++--------------------- 1 file changed, 78 insertions(+), 78 deletions(-) diff --git a/doc/contributing.texi b/doc/contributing.texi index cc6e84013a..0385cedfb1 100644 --- a/doc/contributing.texi +++ b/doc/contributing.texi @@ -31,6 +31,7 @@ Contributing * Coding Style:: Hygiene of the contributor. * Submitting Patches:: Share your work. * Tracking Bugs and Changes:: Keeping it all organized. +* Teams:: Coordinating efforts. * Making Decisions:: Collectively choosing the way forward. * Commit Access:: Pushing to the official repository. * Reviewing the Work of Others:: Some guidelines for sharing reviews. @@ -2055,7 +2056,6 @@ Submitting Patches @menu * Configuring Git:: * Sending a Patch Series:: -* Teams:: @end menu @node Configuring Git @@ -2223,83 +2223,6 @@ Sending a Patch Series another cover letter, e.g. for explaining what's changed since the last revision, and these changes are necessary. -@node Teams -@subsection Teams -@cindex teams - -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 -(@pxref{Making Decisions}). - -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 -id: mentors -name: Mentors -description: A group of mentors who chaperone contributions by newcomers. -members: -+ Charlie Smith -@dots{} -@end example - -@cindex mentoring -You can run the following command to have the Mentors team put in -CC of a patch series: - -@example -$ git send-email --to=@var{ISSUE_NUMBER}@@debbugs.gnu.org \ - --header-cmd='etc/teams.scm cc-mentors-header-cmd' *.patch -@end example - -The appropriate team or teams can also be inferred from the modified -files. For instance, if you want to send the two latest commits of the -current Git repository to review, you can run: - -@example -$ guix shell -D guix -[env]$ git send-email --to=@var{ISSUE_NUMBER}@@debbugs.gnu.org -2 -@end example - @node Tracking Bugs and Changes @section Tracking Bugs and Changes @@ -2705,6 +2628,83 @@ Cuirass Build Notifications where each RSS entry contains a link to the Cuirass build details page of the associated build. +@node Teams +@section Teams +@cindex teams + +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 +(@pxref{Making Decisions}). + +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 +id: mentors +name: Mentors +description: A group of mentors who chaperone contributions by newcomers. +members: ++ Charlie Smith +@dots{} +@end example + +@cindex mentoring +You can run the following command to have the Mentors team put in +CC of a patch series: + +@example +$ git send-email --to=@var{ISSUE_NUMBER}@@debbugs.gnu.org \ + --header-cmd='etc/teams.scm cc-mentors-header-cmd' *.patch +@end example + +The appropriate team or teams can also be inferred from the modified +files. For instance, if you want to send the two latest commits of the +current Git repository to review, you can run: + +@example +$ guix shell -D guix +[env]$ git send-email --to=@var{ISSUE_NUMBER}@@debbugs.gnu.org -2 +@end example + @node Making Decisions @section Making Decisions -- 2.46.0