From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.105.134.102] (helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.43) id 1DiiM7-0002y5-5K for garchives@archives.gentoo.org; Thu, 16 Jun 2005 00:35:39 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j5G0XXu1024533; Thu, 16 Jun 2005 00:33:33 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [134.68.220.30]) by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j5G0U4c3015368 for ; Thu, 16 Jun 2005 00:30:04 GMT Received: from p5086dfd6.dip.t-dialin.net ([80.134.223.214] helo=[192.168.0.9]) by smtp.gentoo.org with esmtpa (Exim 4.43) id 1DiiHa-0000yS-J5 for gentoo-dev@lists.gentoo.org; Thu, 16 Jun 2005 00:30:58 +0000 From: Markus Nigbur To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Final proposal: New alias maintainer-needed@g.o or some such (speak now or forever hold your peace ;) ) Date: Thu, 16 Jun 2005 02:30:44 +0200 User-Agent: KMail/1.8.1 References: <1118630128.32687.14.camel@powerix.local.c0ffeine.de> <200506140038.21821.pYrania@gentoo.org> <20050615184950.GO5946@kfk4ever.com> In-Reply-To: <20050615184950.GO5946@kfk4ever.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1534489.C35dYByx5d"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200506160230.48340.pYrania@gentoo.org> X-Archives-Salt: b5fd7824-72c0-4b16-ac67-bcad4cb88be6 X-Archives-Hash: 5a43497b4fa8e5c67e91453a44318c32 --nextPart1534489.C35dYByx5d Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 15 June 2005 20:49, Maurice van der Pot wrote: > So I take it everybody who replied on this thread is in agreement that > the creation of an alias (e.g. maintainer-needed@gentoo.org) would be > the best solution and that it is upto the herd to choose between > assigning the bug to the new alias and putting the herd on the cc and > the other way around? Assigning to m-n@g.o and adding the actual fitting herd to CC is the most=20 elegant option, IMHO. However we do it, we should really agree on one solution, to get more=20 structure into the chaos. > If this is introduced we need to record it somewhere. I'm not sure what > would be the best place though. =2D Topic of #gentoo-dev =2D -core mail =2D Developer Handbook (which really needs a section about how bugs are tre= ated.=20 I always wanted to write up a draft when I find the time...) =2D Announce the existence and purpose of the alias in the GWN =2D-=20 (o_ Markus Nigbur //\ Gentoo GNU/Linux Developer [ ]/_ http://www.gentoo.org GPG Fingerprint: 9E31 187A 6C78 210C F248 EDBB F2FB A77F 707D F8C1 --nextPart1534489.C35dYByx5d Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQBCsMg4I7fK2cqeyXkRAuK0AKCbLE1WKXgVFBbfumlnTBh02Rb64wCg3wGK WBQHoZPqIL9xlz50XDBLreE= =Dx+S -----END PGP SIGNATURE----- --nextPart1534489.C35dYByx5d-- -- gentoo-dev@gentoo.org mailing list