From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 42CC01381F3 for ; Sat, 22 Jun 2013 01:42:27 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 29570E0ABE; Sat, 22 Jun 2013 01:42:16 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 2E59FE0ABA for ; Sat, 22 Jun 2013 01:42:15 +0000 (UTC) Received: from grubbs.orbis-terrarum.net (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPS id 34CC533E5E8 for ; Sat, 22 Jun 2013 01:42:14 +0000 (UTC) Received: (qmail 7725 invoked by uid 10000); 22 Jun 2013 01:42:13 -0000 Date: Sat, 22 Jun 2013 01:42:13 +0000 From: "Robin H. Johnson" To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Soliciting input for a non-maintainer update (NMU) GLEP Message-ID: References: <201306212017.38571.vapier@gentoo.org> <201306212106.31519.vapier@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201306212106.31519.vapier@gentoo.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-Archives-Salt: aed5ac2c-1d29-4e6f-b1ae-7a483e18864b X-Archives-Hash: 09a4778b50517e9a2d317c0d054ff508 On Fri, Jun 21, 2013 at 09:06:30PM -0400, Mike Frysinger wrote: > On Friday 21 June 2013 20:26:03 Robin H. Johnson wrote: > > On Fri, Jun 21, 2013 at 08:17:38PM -0400, Mike Frysinger wrote: > > > > I'm not going into review systems here at all, I'm simply trying to > > > > have a policy of what changes are welcomed/blocked WITHOUT interaction > > > > from the listed maintainer(s) of a given package/herd. > > > > > > add a new field to metadata.xml that declares the state. make it an enum: > > > ANYTHING_GOES (the default) > > > REQUIRES_HERD > > > REQUIRES_MAINTAINER > > > > I wish it was that easy. > > > > Despite being ANYTHING_GOES on most of my packages, I don't want people > > to add giant features like qmail patchbombs; so we need to figure out > > something like the Debian NMU listing of what's acceptable. > the maintainers intent has to be machine codable So we have the following facets of NMU permissions: Who What > > Does a version bump count as an acceptable trivial change? > that's up to the maintainer This needs to be in the above data: So we have: Who = {ANYTHING_GOES, REQUIRES_DEV, REQUIRES_HERD, REQUIRES_MAINTAINER} What = {NONE, TRIVIAL, MINOR_FEATURES, VERSION_BUMP, MAJOR_FEATURES} So most of my packages might be coded with: - If you're a developer, you can do trivial fixes, add minor features, bump the version. - If you're in the herd, you can add major features. -- Robin Hugh Johnson Gentoo Linux: Developer, Trustee & Infrastructure Lead E-Mail : robbat2@gentoo.org GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85