From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-dev+bounces-61041-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
	by finch.gentoo.org (Postfix) with ESMTP id E68191381F3
	for <garchives@archives.gentoo.org>; Sat, 22 Jun 2013 09:46:07 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 53FD3E0A6C;
	Sat, 22 Jun 2013 09:46:05 +0000 (UTC)
Received: from a1www.kph.uni-mainz.de (a1www.kph.uni-mainz.de [134.93.134.1])
	(using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by pigeon.gentoo.org (Postfix) with ESMTPS id 3A8C9E09B6
	for <gentoo-dev@lists.gentoo.org>; Sat, 22 Jun 2013 09:46:03 +0000 (UTC)
Received: from a1i15.kph.uni-mainz.de (a1i15.kph.uni-mainz.de [134.93.134.92])
	by a1www.kph.uni-mainz.de (8.14.4/8.13.4) with ESMTP id r5M9k2uV009736
	for <gentoo-dev@lists.gentoo.org>; Sat, 22 Jun 2013 11:46:02 +0200
Received: from a1i15.kph.uni-mainz.de (localhost [127.0.0.1])
	by a1i15.kph.uni-mainz.de (8.14.6/8.14.2) with ESMTP id r5M9k2Lc032220;
	Sat, 22 Jun 2013 11:46:02 +0200
Received: (from ulm@localhost)
	by a1i15.kph.uni-mainz.de (8.14.6/8.14.6/Submit) id r5M9k2l1032218;
	Sat, 22 Jun 2013 11:46:02 +0200
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
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-Transfer-Encoding: 7bit
Message-ID: <20933.29274.438907.585923@a1i15.kph.uni-mainz.de>
Date: Sat, 22 Jun 2013 11:46:02 +0200
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Soliciting input for a non-maintainer update (NMU)
 GLEP
In-Reply-To: <20933.26517.731140.317442@a1i15.kph.uni-mainz.de>
References: <robbat2-20130621T182855-619828737Z@orbis-terrarum.net>
	<201306212017.38571.vapier@gentoo.org>
	<robbat2-20130622T002113-633072609Z@orbis-terrarum.net>
	<201306212106.31519.vapier@gentoo.org>
	<robbat2-20130622T013220-253902125Z@orbis-terrarum.net>
	<20933.26517.731140.317442@a1i15.kph.uni-mainz.de>
X-Mailer: VM 8.2.0b under 24.3.1 (x86_64-pc-linux-gnu)
From: Ulrich Mueller <ulm@gentoo.org>
X-Archives-Salt: 9cd7b8e9-6ff6-4a3d-9c62-24a7920ebd45
X-Archives-Hash: bbb756d9f42721f8cf749bd72cb92035

>>>>> I wrote:

>>>>> On Sat, 22 Jun 2013, Robin H Johnson wrote:
>> 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:
>> <nmu-policy who="REQUIRES_DEV" what="VERSION_BUMP" />
>> <nmu-policy who="REQUIRES_HERD" what="MAJOR_FEATURES" />

>> - 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.

> Shouldn't this be REQUIRES_TEAM instead? A "herd" used to be a
> collection of packages, whereas the devs maintaining them were
> called a team. Or don't we care about this distinction any more?

Getting back on topic: Apart from this minor issue, I think that your
proposal is quite reasonable.

Ulrich