From: "Robin H. Johnson" <robbat2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Proxying and bugzilla
Date: Mon, 29 Mar 2010 21:55:05 +0000 [thread overview]
Message-ID: <robbat2-20100329T215114-663708430Z@orbis-terrarum.net> (raw)
In-Reply-To: <4BB11FDB.90506@necoro.eu>
On Mon, Mar 29, 2010 at 11:47:07PM +0200, René 'Necoro' Neumann wrote:
> 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.
We've got this available already.
The bug to track permissions is here:
http://bugs.gentoo.org/show_bug.cgi?id=236218
Ask the developer who is proxying for you to please file a bug to
devrel, and they will update that tracking page when they grant you
editbugs privileges.
> 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.
I've wondered before about giving privileges based on the summary line,
but I haven't given it much thought beyond that. I think that would
probably be more useful than proxy herds, because 'herds' are just
actually mail aliases with user accounts in Bugzilla.
> Some sort of "bugzilla quiz" which needs to be taken by the maintainer
> might be useful in both cases.
+1 on that idea too.
--
Robin Hugh Johnson
Gentoo Linux: Developer, Trustee & Infrastructure Lead
E-Mail : robbat2@gentoo.org
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85
next prev parent reply other threads:[~2010-03-29 21:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 21:47 [gentoo-dev] Proxying and bugzilla René 'Necoro' Neumann
2010-03-29 21:55 ` Robin H. Johnson [this message]
2010-03-29 23:31 ` Christian Ruppert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=robbat2-20100329T215114-663708430Z@orbis-terrarum.net \
--to=robbat2@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox