From: Stefan Schweizer <genstef@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Re: [GLEP] Bugzilla access for contributors
Date: Mon, 04 Sep 2006 09:25:01 +0200 [thread overview]
Message-ID: <edgkds$esf$1@sea.gmane.org> (raw)
In-Reply-To: 44FBD042.3070104@gentoo.org
Josh Saddler wrote:
> Stefan Schweizer wrote:
>> Josh Saddler wrote:
>>
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> Stefan Schweizer wrote:
>>> [. . .]
>>>
>>> Define "contributors" -- is this a special status? If it is, how does
>>> one *become* a "contributor" to get these rights?
>>>
>>> This is potentially a big problem, the way I see it.
>>
>> As the word might tell a contributor is someone who is contributing. No
>> special status involved.
>>
>> - Stefan
>
> Contributing what? Contributing how much? Contributing how long? How is
> quality measured? Is there a minimum level somewhere? X amount of ebuilds?
> X amount of patches for docs/packages, or donating hardware, or adminning
> a webnode somewhere?
It does not matter. The real requirement is not to be defined as
a "contributor" but to take the ebuild quiz:
"To ensure that not everyone who asks for it can get access to edit bugs it
is required to complete the ebuild quiz prior to requesting access"
-Stefan
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2006-09-04 7:31 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
2006-09-04 14:43 ` [gentoo-dev] " Alec Warner
2006-09-04 7:05 ` [gentoo-dev] " Josh Saddler
2006-09-04 7:25 ` Stefan Schweizer [this message]
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='edgkds$esf$1@sea.gmane.org' \
--to=genstef@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