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 1NwMo3-0005GT-An for garchives@archives.gentoo.org; Mon, 29 Mar 2010 21:47:35 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C908DE0B9E; Mon, 29 Mar 2010 21:47:29 +0000 (UTC) Received: from mail.necoro.eu (zakarum.de [84.19.167.72]) by pigeon.gentoo.org (Postfix) with ESMTP id 436DFE0AF2 for ; Mon, 29 Mar 2010 21:47:09 +0000 (UTC) Received: from [192.168.0.5] (dslb-094-216-074-015.pools.arcor-ip.net [94.216.74.15]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.necoro.eu (Postfix) with ESMTPSA id 4175210009E for ; Mon, 29 Mar 2010 23:47:08 +0200 (CEST) Message-ID: <4BB11FDB.90506@necoro.eu> Date: Mon, 29 Mar 2010 23:47:07 +0200 From: =?UTF-8?B?UmVuw6kgJ05lY29ybycgTmV1bWFubg==?= User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8) Gecko/20100305 Lightning/1.0b2pre Thunderbird/3.0.3 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 To: gentoo-dev@lists.gentoo.org Subject: [gentoo-dev] Proxying and bugzilla X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 46baa3ea-63b3-4952-81d4-1be3baa5fd6e X-Archives-Hash: f1875928311ae1a54bda27993a65b53b -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, currently I am a maintainer for two packages -- and as a non-gentoo-dev being proxied by guys who are. Now a disadvantage of this position are the restricted rights in bugzilla. In case a bug is filed for one of my maintained packages I have to ask one of my proxies for each step ("could you mark this as a dupe?", "could you mark this as fixed?", etc.). This is quite cumbersome and puts just some load on the devs (which should have been avoided by the proxy-solution in the first place). So I am asking whether there would be a solution to allow people like me to have full bugzilla rights on packages they are in charge for. Two possibilities come to my mind: 1) Have an implicit restriction, i.e. give them full rights (where "full" just means: everything they need for handling their bugs), but make a policy, that they are only allowed to use this for their packages. In other words: Enforce the correct usage by "legal" ways instead of teachnically. This approach is probably easier in terms of bureaucracy but might be seen as dangerous. 2) Enforce the restriction technically. I do not know how this could be done in bugzilla - perhaps by having "proxy-herds", i.e. one herd for each proxied package and only give the user the full rights, if a bug is assigned to a herd he is a member of. The disadvantage is here, that there is quite some overhead of managing a bunch of "proxy-herds". Some sort of "bugzilla quiz" which needs to be taken by the maintainer might be useful in both cases. I'd be glad to hear some other opinions. - - Ren=C3=A9 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkuxH9sACgkQ4UOg/zhYFuAvogCfflrqjFg6iMq6OGEfp7Z4NHXS ERUAnAonFFHRlGRYuKVSL12Vb2WinSAr =3D1DOx -----END PGP SIGNATURE-----