From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1NNs9o-0006ck-91 for garchives@archives.gentoo.org; Thu, 24 Dec 2009 18:11:28 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D674FE06DF for ; Thu, 24 Dec 2009 18:11:27 +0000 (UTC) Received: from smtp-vbr19.xs4all.nl (smtp-vbr19.xs4all.nl [194.109.24.39]) by pigeon.gentoo.org (Postfix) with ESMTP id 64A27E09A8 for ; Thu, 24 Dec 2009 16:12:24 +0000 (UTC) Received: from epia.jer-c2.orkz.net (atwork-106.r-212.178.112.atwork.nl [212.178.112.106]) (authenticated bits=0) by smtp-vbr19.xs4all.nl (8.13.8/8.13.8) with ESMTP id nBOGCNHv039906 for ; Thu, 24 Dec 2009 17:12:23 +0100 (CET) (envelope-from jer@gentoo.org) Date: Thu, 24 Dec 2009 17:12:22 +0100 From: Jeroen Roovers To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] metdata.dtd should require Message-ID: <20091224171222.3f4c5dc7@epia.jer-c2.orkz.net> In-Reply-To: <4B336086.2000108@gentoo.org> References: <200912071256.50485.bangert@gentoo.org> <1260205453.12837.21.camel@localhost> <200912072120.44046.bangert@gentoo.org> <1260890340.29419.142.camel@tablet> <4B288301.5030808@gentoo.org> <55e0be1b0912231036q533f43ccx2425383804da561@mail.gmail.com> <4B336086.2000108@gentoo.org> X-Mailer: Claws Mail 3.7.3 (GTK+ 2.16.6; i686-pc-linux-gnu) 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-Transfer-Encoding: 7bit X-Virus-Scanned: by XS4ALL Virus Scanner X-Archives-Salt: 6a53cda8-36ab-4c9b-a92f-ed9e2976ef19 X-Archives-Hash: a812ecd8a1dd2a8aaa86c69fdcf34e1e On Thu, 24 Dec 2009 07:37:26 -0500 Richard Freeman wrote: > I think we should definitely have some way of designating which > should be the contact for bugs. I've had some bugs sit around for a > while without being noticed because they were assigned to the herd > the package is in, and not to me personally, and I don't generally > work with that herd, and the project associated with the herd doesn't > generally maintain the package. That means the bug wasn't properly assigned... I've set up some rules [1] that might help there. It comes down to this: 1) If one or more tags are listed, assign to the first one mentioned. 2) If no tag is listed, assign to the first mentioned. 3) CC everyone else listed (s and s). The rationale is that if one or more s are listed as well as one or more s, a bug wrangler shouldn't need to go find out if that maintainer happens to be on the 's alias as well (otherwise, why would it mention those maintainers separately?). The order in which and tags are listed isn't special, because goes before for the reason set out above. The order of multiple tags (or multiple tags) does matter: the first one you find is the Assignee, the others are CC'd. Regards, jer [1] http://www.gentoo.org/proj/en/qa/bug-wranglers/index.xml#doc_chap4