From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: On maintaining GNU Guix Date: Thu, 11 Jul 2019 11:01:11 +0200 Message-ID: <877e8pj67c.fsf@elephly.net> References: <87ftnfk7a0.fsf@elephly.net> <87sgrdrxvw.fsf@dustycloud.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:36446) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hlUxK-0007sr-AZ for guix-devel@gnu.org; Thu, 11 Jul 2019 05:01:35 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hlUxF-0004Sm-AW for guix-devel@gnu.org; Thu, 11 Jul 2019 05:01:34 -0400 Received: from sender4-of-o53.zoho.com ([136.143.188.53]:21398) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hlUxE-0004BZ-TD for guix-devel@gnu.org; Thu, 11 Jul 2019 05:01:29 -0400 In-reply-to: <87sgrdrxvw.fsf@dustycloud.org> 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" To: guix-devel@gnu.org Christopher Lemmer Webber writes: > Ricardo Wurmus writes: > >> This would allow each of the maintainers to better concentrate on >> selected sub-projects, and to increase the likelihood of having an >> active co-maintainer around when other co-maintainers are unavailable. >> We also hope that this change will decrease the importance of any >> individual maintainer=E2=80=99s presence and attention, and eventually l= ead to a >> more collective and perhaps representative way of arriving at decisions >> and breaking ties when necessary. > > +1! > > In addition... I think we aren't at the point where it's applicable, but > in considering the point where Guix's community grows big enough where > many people contributing to the main repository is untenable, I think a > move to something like what the Linux kernel does (different people > responsible for certain trees) might make sense. We already have many largely independent modules that people work on in an independent fashion. There are champions for packages written in certain languages (Java, Rust, Go, R, Haskell, etc) and in some tangible sense the quality of packages in those modules is ensured by those people. If it would help we could make this sort of module maintainership a official (an idea brought forward by janneke some months ago) by recording it somewhere or by automating requests for review when patches come in (an idea fielded by Andy Wingo). I don=E2=80=99t think we need separate repositories for Guix packages just = yet, but even for the separate repositories that we do have (website, videos, maintenance, etc) we also generally have =E2=80=9Cproject managers=E2=80=9D= or =E2=80=9CMeister=E2=80=9D who are more familiar with them and can be considered authorities in those areas. -- Ricardo