public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Bryan Ãstergaard" <kloeri@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev]  [GLEP] Bugzilla access for contributors
Date: Mon, 4 Sep 2006 15:25:38 +0000	[thread overview]
Message-ID: <20060904152538.GC8959@woodpecker.gentoo.org> (raw)
In-Reply-To: <44FB757B.2040309@gentoo.org>

On Sun, Sep 03, 2006 at 08:38:19PM -0400, Alec Warner wrote:
> Stefan Schweizer wrote:
> > Hi,
> > 
> > as requested by multiple devrel members I have written a GLEP to standardize
> > bugzilla access for contributors. It has already been discussed on the
> > devrel mailing list before but I am looking for a wider opinion now.
> > 
> > This is also a submission for the new council when it meets.
> > 
> > Best regards,
> > Stefan
> 
> Errr. on -devrel you noted you would just make people take the ebuild
> quiz and now devrel wants a GLEP again?
> 
> I'll state the same thing I stated on that list.
> 
> A.  This already happens.  I had bugs access for MONTHS before becoming
> a dev; I got assigned to the portage buggroup and I could edit portage
> bugs.  Anyone already on the portage team could add me, so no nastiness
> for recruiters (or anyone else).
If people are randomly given bugzie privs (or any other privs) this is
something we need to fix. And just to make this clear to all - handing
out privs is only half the equation and it's already hard enough for
recruiters to keep track of devs even though we have well defined
procedures etc. for that.
> 
> B.  Double bonus is that I don't even see why a GLEP is required?  This
> is a small subset of users using one resource (bugzilla) so perhaps
> Infra and devrel and you can work out the requisite groups?  Why is
> there all this red tape?
Because it's going to affect all devs if people don't need to pass
quizzes (or we lower the threshhold substantially) before they can
reassign, close, reopen etc. the maintainers bugs.
> 
> Create a group; come up with a subset of bugs that they can access, add
> user to group -> done.  As long as they can't access my bugs; I really
> shouldn't (and trust me I don't) care.
Who's going to admin that? We already have the Arch Tester / Herd Tester
projects that defines a proper way of achieving the goal as I see it.

Only problem with Herd Testers / Arch Testers compared to genstefs goal
is that HTs/ATs deal with packages in the tree while sunrise
contributors deal with packages outside the tree.

And personally I'd very much like to draw the line somewhere. Genstef
made the GLEP extremely vague regarding contributors (on purpose) but
guess what?  Everybody who files a new bug, submits a fixed ebuild etc.
are contributors. So should we just remove all the restrictions now?
This is definitely something we need to define before moving on, no
matter if the GLEP is eventually denied or accepted.
> 
> C.  No real standard on any other fora.  I don't need a GLEP to add
> someone to my project overlay, or grant them voice or ops in my
> project's IRC channel.  I don't need a GLEP to get them subscribed to my
> mailing list and I don't need a GLEP to add them to (most) project
> aliases.  Why does this require one?
Because this is about the entire Gentoo project and affects us all in a
very direct way as opposed to random projects.

Regards,
Bryan Østergaard
-- 
gentoo-dev@gentoo.org mailing list



  parent reply	other threads:[~2006-09-04 15:30 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-03 22:59 [gentoo-dev] [GLEP] Bugzilla access for contributors Stefan Schweizer
2006-09-04  0:38 ` Alec Warner
2006-09-04  6:35   ` [gentoo-dev] " Stefan Schweizer
2006-09-04 15:26     ` Bryan Ãstergaard
2006-09-04 15:25   ` Bryan Ãstergaard [this message]
2006-09-04 18:59     ` [gentoo-dev] " Alec Warner
2006-09-04 20:01       ` Bryan Østergaard
2006-09-04  3:08 ` Elfyn McBratney
2006-09-04  3:16   ` Elfyn McBratney
2006-09-04  6:40   ` [gentoo-dev] " Stefan Schweizer
2006-09-04  7:27     ` Donnie Berkholz
2006-09-04  3:25 ` [gentoo-dev] " Josh Saddler
2006-09-04  6:45   ` [gentoo-dev] " Stefan Schweizer
2006-09-04  7:05     ` Mike Frysinger
2006-09-04  8:32       ` [gentoo-dev] " Stefan Schweizer
2006-09-04  9:16         ` Mike Frysinger
2006-09-04  9:20         ` Josh Saddler
2006-09-04 11:54           ` [gentoo-dev] " Stefan Schweizer
2006-09-04 14:38             ` Simon Stelling
2006-09-04 15:32             ` Bryan Ãstergaard
2006-09-04 14:43           ` [gentoo-dev] " Alec Warner
2006-09-04  7:05     ` [gentoo-dev] " Josh Saddler
2006-09-04  7:25       ` [gentoo-dev] " Stefan Schweizer
2006-09-04 15:33 ` [gentoo-dev] " Kevin F. Quinn
     [not found] ` <44FDB142.4060302@gentoo.org>
2006-09-05 17:45   ` Jakub Moc
2006-09-05 18:21     ` Bryan Østergaard
2006-09-05 17:57   ` Bryan Østergaard
2006-09-09 19:50     ` [gentoo-dev] " Stefan Schweizer

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=20060904152538.GC8959@woodpecker.gentoo.org \
    --to=kloeri@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