From: Markos Chandras <hwoarang@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] More bugzilla restrictions should be applied to normal users
Date: Fri, 13 May 2011 11:10:10 +0100 [thread overview]
Message-ID: <20110513101010.GA11219@Eternity.halls.manchester.ac.uk> (raw)
In-Reply-To: <4DCC73E6.2040903@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1970 bytes --]
On Thu, May 12, 2011 at 11:57:26PM +0000, Jorge Manuel B. S. Vicetto wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi Markos.
>
> On 12-05-2011 20:19, Markos Chandras wrote:
> > Hi,
> >
> > Quite a lot of users tend to change bugzilla fields without even
> > understand why they are doing it. Would it be possible to restrict users
> > from touching the following fields?
> >
> > - Importance
> > - Severity
> > - CCing arches on their own (!)
> > - Blocks
> > - Keywords
> > - <...>
> >
> > How do you feel about that? Does bugzilla allow such restrictions?
>
> I think we should trust our users. Some might feel tempted to "test all
> the buttons", but I'm sure the majority will just try to fill a bug
> report the best way they know how.
It is not a matter of trust. If you trust them, then blocking access to
these fields shouldn't be a problem anyway.
> This topic has been raised a few times in the past and as far as I can
> recall there never was a consensus about it. In any case, as pointed out
> before, some developers want users to be able to CC them on bugs, at
> least on some bugs, informed users can have a good idea about the
> importance and or severity of a bug and in general being more open can
> provide a more inviting environment for users to look at and or
> contribute to Gentoo.
First of all, I said "Ccing Arches". Of course they should be allowed to
CC anyone, but ccing arches creates too much noise for us and quite a
lot of them do not understand the purpose of arch alias.
> Finally, whenever a user abuses bugzilla, you can poke bugzilla admins,
> userrel and a few others to look at and take care of it. Some of us can
> go as far as locking users accounts - feel free to poke me if that need
> ever arises.
>
> > Regards,
>
How is this solution more elegant than the one I proposed? :)
Regards,
--
Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-05-13 10:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 20:19 [gentoo-dev] More bugzilla restrictions should be applied to normal users Markos Chandras
2011-05-12 23:57 ` Jorge Manuel B. S. Vicetto
2011-05-13 0:39 ` Francisco Blas Izquierdo Riera (klondike)
2011-05-13 10:10 ` Markos Chandras [this message]
2011-05-13 11:59 ` Jorge Manuel B. S. Vicetto
2011-05-20 8:40 ` Thomas Kahle
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=20110513101010.GA11219@Eternity.halls.manchester.ac.uk \
--to=hwoarang@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