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]  Re: Re: Re: [GLEP] Bugzilla access for contributors
Date: Mon, 4 Sep 2006 15:32:13 +0000	[thread overview]
Message-ID: <20060904153213.GE8959@woodpecker.gentoo.org> (raw)
In-Reply-To: <edh469$2ut$1@sea.gmane.org>

On Mon, Sep 04, 2006 at 01:54:02PM +0200, Stefan Schweizer wrote:
> Josh Saddler wrote:
> > Because as much as possible, we need to see something concrete, not "maybe
> > an arch tester." We need to have a better definition of what "when needed
> > is" and who these "some people" are -- think about it. Do we want a system
> > that works like devship, but only halfway -- like you suggested, just
> > passing the ebuild quiz -- or is something more needed?
> 
> If it needs to be extended a new GLEP like this one can be written or this
> one extended. This is only about bugzilla access, nothing more. So no, it
> is meant to be as non-concrete as possible to allow usage in as many cases
> as possible.
> 
This practically means opening up bugzie to world + dog. Maybe not right
now but being so non-concrete as you call it means we can never tell
anybody no. All they have to do is calling themselves a contributor.
Personally I think this is only going to lead to chaos and I'm not at
all frilled by the idea.

If this is to go forward it needs to be well-defined - handwaving simply
isn't cutting it imo.

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



  parent reply	other threads:[~2006-09-04 16:12 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   ` [gentoo-dev] " Bryan Ãstergaard
2006-09-04 18:59     ` 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 [this message]
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=20060904153213.GE8959@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