From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0 Subject: Re: Adopt a patch! Date: Thu, 14 Sep 2017 04:26:25 +0000 Message-ID: <20170914042625.kgiv2g2iqgmuqhiq@abyayala> References: <877ex5d555.fsf@gnu.org> <980b12b7.AEQAQDR72NgAAAAAAAAAAAOtZhgAAAACwQwAAAAAAAW9WABZudnG@mailjet.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="bchpbemhr4gyzddd" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49561) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dsLju-0005HF-Tk for guix-devel@gnu.org; Thu, 14 Sep 2017 00:27:00 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dsLjt-0002UK-Ns for guix-devel@gnu.org; Thu, 14 Sep 2017 00:26:58 -0400 Content-Disposition: inline In-Reply-To: <980b12b7.AEQAQDR72NgAAAAAAAAAAAOtZhgAAAACwQwAAAAAAAW9WABZudnG@mailjet.com> 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: Arun Isaac Cc: guix-devel --bchpbemhr4gyzddd Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Arun Isaac transcribed 0.9K bytes: >=20 > Would it help to have teams of maintainers for specific packages or a > specific category of packages? Perhaps something like Debian has? Right > now, anyone can review any package. But, no one is "responsible" for any > package, and this feels a little chaotic. As far as I see it we already have teams, just sometimes they change or work together / blend together. For example I do mostly mail, crypto, IM and WM related stuff but I also have other things on my list which is due to another project and should hopefully get taken over as more people join there. A group of the same people does R. We have one person doing Icecat and linu= x-libre. etc. Of course some packages are left behind at the moment, but you can step on no ones toes by updating them (which happens more often in maintainer-per-package OS'). > Also, should we accept any package into Guix (provided it is free > software, of course)? Or, should we pick and choose, packaging only > sufficiently mature software? What about unmaintained packages? Debian's > policy is to remove unmaintained packages. What is ours? Perhaps we need > some kind of package popularity contest like Debian has. No. I think as long as the source exists it can find its way into Guix. As soon as security issues start to show up or other problems, we are dealing with it. There's a policy already we follow (it might not be written down of course). I also think that people will take on packages they need as soon as they realize that no one will be the person they think that could update the package they are looking at. It's very hands on and if when the documentation can express this in an empowering way, it's good. To just expect that "this group will handle it" doesn't help in the long run. For example getmail is considered to be "finished" many years ago by the author, it simply gets tiny fixes and occasionally features added when people ask for them. It's mostly in maintenance mode. We look at python packages and don't package unmaintained ones if they are absolutely not needed. For example I approach upstream if I see outdated pythong packages and ask for a resolution. Maybe we should write our current approach to this down. I don't think a polpularity contest would do any good. > These questions are bothering me, because I feel we don't have > sufficient labour power to handle the enormous number of packages out > there. I've been meaning to raise these questions at some point. Though > these questions are somewhat tangential to this thread, I thought it > might be ok to raise them here. >=20 >=20 --=20 ng0 GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588 GnuPG: https://krosos.org/dist/keys/ https://www.infotropique.org https://www.krosos.org --bchpbemhr4gyzddd Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEqIyK3RKYKNfqwC5S4i+bv+40hYgFAlm6BPAACgkQ4i+bv+40 hYjXkBAAmqDM5ONRe3Xb+Kqf2G1ZE5ffiB0IzMNewJlzA21xDHSgoB9Pp3G5B58l cX6wCr6+q54w3AjS2M/d+MHGO1z5vCDgI1yzqX/WlOJtwpfadanx47RMhrK2ME18 jhXM44sknBieziQbsdNBpDl90NJz2CT7nWZj0gj6pksCEnJHMVQAmXAxBjgA7RaR X0nshtBL1h4gkyUPtPYRkW/2DmhMx13KAdG06etvB7HWgyuhWNQ2EYC8Mkpi2WSQ G92tPzr/22mcA9XUma0u3KS+ZSLim7ttzeSS/NoHb+18wv4RKhT4Xxokn07HkXzs aU2WgDQ7XeYWypGqTiuv3787BTYMBrH2LrTSafu1ZzQJ44oZA/b1EVun513zYthd uGNkwZ5NXxudPAXrXW5Xu3JOySVFDlAzSNFZwoUJHogrUiO7A+SpzpzFAZDO6o6y abhsT0q76/vVGY7SMiKxip0VCvoGNmBMeui+4kzf+lLTlXLLhXYqPaoxeeKaxaw/ AV88nwP128WfI8lUKe9ImASG2WXCz6K3wH1QCk3m4n5DDA9Bu2kInP4Yd5QxJCYx fMksvp0Kgf0E7qoXqhze/LB8faVfV3ce2PSUtGD5ZHy8umHlYnK19Do4KORuO7eJ 9TNF7tYgSG/sWnQvdxjJB5ANQjDNbD2iH4U6UOxLQNvyVzOkwro= =c35c -----END PGP SIGNATURE----- --bchpbemhr4gyzddd--