From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Listing sub-system maintainers? Date: Tue, 16 Sep 2014 14:49:30 +0200 Message-ID: <87egvbk9wl.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:58418) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XTsCW-0005aV-Fx for guix-devel@gnu.org; Tue, 16 Sep 2014 08:49:49 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XTsCM-0004Ke-O3 for guix-devel@gnu.org; Tue, 16 Sep 2014 08:49:44 -0400 Received: from hera.aquilenet.fr ([2a01:474::1]:45058) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XTsCM-0004Jz-8b for guix-devel@gnu.org; Tue, 16 Sep 2014 08:49:34 -0400 Received: from localhost (localhost [127.0.0.1]) by hera.aquilenet.fr (Postfix) with ESMTP id 8A573FA0 for ; Tue, 16 Sep 2014 14:49:29 +0200 (CEST) Received: from hera.aquilenet.fr ([127.0.0.1]) by localhost (hera.aquilenet.fr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bpyQgHoGTktB for ; Tue, 16 Sep 2014 14:49:29 +0200 (CEST) Received: from pluto (pluto.bordeaux.inria.fr [193.50.110.57]) by hera.aquilenet.fr (Postfix) with ESMTPSA id 4A160F5A for ; Tue, 16 Sep 2014 14:49:29 +0200 (CEST) List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Guix-devel --==-=-= Content-Type: multipart/mixed; boundary="=-=-=" --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hello, Guix! While discussing with a Debian developer at the GHM, it seemed like a good idea to start developing more =E2=80=9Cformal=E2=80=9D rules now that = Guix is small, in order to scale better in the future. Sometimes, we=E2=80=99ve seen patches on the list waiting for review for so= me time, or people feeling they had not been =E2=80=9Cformally approved.=E2=80= =9D Recently, we=E2=80=99ve had a hard time making a decision and sticking to it wrt. glibc CVEs. This is the kind of practical issues that a process should intend to solve. I thought a starting point could be to have a list of maintainers, similar in spirit to the =E2=80=98MAINTAINERS=E2=80=99 file in GDB=C2=B9. = So I=E2=80=99ve come up with the attached file, to start the discussion: --=-=-= Content-Type: text/x-org; charset=utf-8 Content-Disposition: inline; filename=MAINTAINERS Content-Transfer-Encoding: quoted-printable This file describes different groups of people who are, together, the maintainers and developers of the GNU Guix project. * Overview [taken almost verbatim from GDB's =E2=80=98MAINTAINERS=E2=80=99 file, wit= h the last paragraphs from Guix=E2=80=99s =E2=80=98HACKING=E2=80=99 file] There are four groups of Guix developers, covering the patch development and review process: - The Global Maintainers. These are the developers in charge of most daily development. They have wide authority to apply and reject patches, but defer to the Responsible Maintainers (see below) within their spheres of responsibility. They have permission to check patches into the repository without obtaining approval first. - The Responsible Maintainers. These are developers who have expertise and interest in a particular area of Guix, who are generally available to review patches, and who prefer to enforce a single vision within their areas. - The Write After Approval Maintainers. These are developers who have write access to the Guix source tree. They can check in their own changes once a developer with the appropriate authority has approved the changes; they can also apply the Obvious Fix Rule (below). Maintainers should always post non-trivial patches to guix-devel@gnu.org. Trivial patches include fixing typos, fixing obvious mistakes, etc. Maintainers can commit patches that just add a new package, and a simple on= e, if they=E2=80=99re confident (which means they successfully built it in a c= hroot setup, and have done a reasonable copyright and license auditing.) Likewise for package upgrades, except for upgrades that trigger a lot of rebuilds (f= or example, upgrading GnuTLS or GLib.) There is a mailing list for commit notifications (guix-commits@gnu.org), so people can notice. The term =E2=80=9Creview=E2=80=9D is used in this file to describe several = kinds of feedback From=20a maintainer: approval, rejection, and requests for changes or clarification with the intention of approving a revised version. Review is= a privilege and/or responsibility of various positions among the Guix Maintainers. Of course, anyone=E2=80=94whether they hold a position but no= t the relevant one for a particular patch, or are just following along on the mailing lists for fun, or anything in between=E2=80=94may suggest changes o= r ask questions about a patch! * Global Maintainers Ludovic Court=C3=A8s (+ someone else...) * Responsible Maintainers This section lists parts of the Guix source tree their Responsible Maintainers. ** Core (store, derivations, packages, monads, gexp) Ludovic Court=C3=A8s ** Tools Eric Bavier guix refresh Ludovic Court=C3=A8s guix package, guix system, guix pull, etc. Cyril Roelandt guix lint Mark H. Weaver guix package ** Build Systems Ludovic Court=C3=A8s gnu, trivial, perl Andreas Enge gnu, cmake, python Cyril Roelandt python, perl Mark H. Weaver gnu, trivial ** Packages *** Bootstrap, base, cross-base, make-bootstrap Ludovic Court=C3=A8s Mark H. Weaver *** Specific cross tool chain Ludovic Court=C3=A8s i686-pc-gnu Andreas Enge mips64el-linux-gnu Manolis Ragkousis i686-pc-gnu Mark H. Weaver mips64el-linux-gnu *** Architecture-specific Ludovic Court=C3=A8s x86_64-linux Andreas Enge x86_64-linux, mips64el-linux Mark H. Weaver x86_64-linux, mips64el-linux John Darrington i686-linux *** Security Handling vulnerabilities in Guix and CVEs in packaged software. Ludovic Court=C3=A8s Mark H. Weaver *** GNU Linux-Libre Jason Self *** GNU Hurd Manolis Ragkousis *** Other packages Everyone! (Add per-package maintainers?) *** Packaging guidelines Andreas Enge ** User interfaces Ludovic Court=C3=A8s (guix scripts package), (guix profiles) Alex Kost Emacs, (guix profiles) ** Operating system Ludovic Court=C3=A8s gnu/system, gnu/services, gnu/build --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable I=E2=80=99ve put names under each item, to get an idea. We can discuss the details of who does what if/when we agree on the process; it will be a voluntary process, of course. The difficulty is to come up with something useful and not overkill. The list of =E2=80=9Csub-systems=E2=80=9D may be too fine-grain, actually. What do people think of the general idea? Any suggestions? Thoughts about simplifications or clarifications? Thanks, Ludo=E2=80=99. =C2=B9 https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;a=3Dblob_= plain;f=3Dgdb/MAINTAINERS;hb=3DHEAD --=-=-=-- --==-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBAgAGBQJUGDHaAAoJEAkLEZk9muu1ASYQAJvXVXwz7KgUVoYVsCAmgHuh sj2mPfWWnAQIQzJwSuYXw8pISJHBogbnWnADLmTAy1OZqkOKWfqNhpieL+7ASiZE kMmhY7Fhe3lHOz+g1rSHt5XHiIGBdRGuXqSYX+YHz04Vo7dypJ08Q6jJws+QWKVD J2boHgoYeCBfnrLSQ+F+MzHr7mA6tJgbFE2YKWFvfD7wTdhwzOii12oX0bpjh+TJ ZP6apEo8A3rzxsIq1vWzt3SwEI7VlTRqwXVsQK5O+5APxd84l19jmxJavNu8WshL VBltOummnAr6Pp6Y8Mzu2EIz+ur1ZMwSKWNWzHe4wDozaOQEn4PG5FJ/QDWD1yXr xF8YWj3JTSvxSnlwxeR72iXGAVbf/JnZNOzm6zsQkE5/x5gpGD+IyvhuJQ5wNPk2 b1cSCZnuKZm1KI47nNLNbHgSU6c1IcXkowIseBkTIDmfeCsyt0X5Yy7Xi+gs5XzE UuuLFjsUcL058q3oMve9THBjEgIHMXORBGLGPSNp6tZNNDPR2ydHv9xgqvKOExg3 ycIFDB+26xGEGFv89frUpu7ddObzM8PjBOKFRP3rqCPPMjd5iPERUl/2epXu9MvG nX4rFnVsGgk0rYQep4f6ov7g25dwWTAHR0Ia4+cFJPJJXkfXGqEyuU628qcIPkfO mRR2pxWVnEvEUVEz1F3/ =wjyl -----END PGP SIGNATURE----- --==-=-=--