public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "René 'Necoro' Neumann" <lists@necoro.eu>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Proxying and bugzilla
Date: Mon, 29 Mar 2010 23:47:07 +0200	[thread overview]
Message-ID: <4BB11FDB.90506@necoro.eu> (raw)

-----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é
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkuxH9sACgkQ4UOg/zhYFuAvogCfflrqjFg6iMq6OGEfp7Z4NHXS
ERUAnAonFFHRlGRYuKVSL12Vb2WinSAr
=1DOx
-----END PGP SIGNATURE-----



             reply	other threads:[~2010-03-29 21:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-29 21:47 René 'Necoro' Neumann [this message]
2010-03-29 21:55 ` [gentoo-dev] Proxying and bugzilla Robin H. Johnson
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=4BB11FDB.90506@necoro.eu \
    --to=lists@necoro.eu \
    --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