From: "Kent Fredric" <kentfredric@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Non-Dev Contributors and the Tree
Date: Fri, 8 Jun 2007 19:01:54 +1200 [thread overview]
Message-ID: <8cd1ed20706080001g3a58b15ej3ef9fe67d143d80d@mail.gmail.com> (raw)
In-Reply-To: <4667EF71.9010103@gentoo.org>
On 6/7/07, Michael Cummings <mcummings@gentoo.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> ...or, Trees and Tree Climbers: Shaking up the tree
>
>
> Comments?
>
> ~mcummings
>
As a non-dev with not a lot of free time, I applaud this suggestion.
However, my core fear is the potential for it becoming subject to
abuse, and people insisting on repeatedly uploading patches that are
not actually wanted / necessary for the project, despite the package
maintainer saying 'dude , stop'
Basically, if a non-maintainer wants maintenance rights, how do they
go about attaining them? , an automated service, or some vetting
process?
How do we go about handling the problem with the predicted increase in
collisions?
Is CVS fast enough / flexible enough for such a massive change in users?
(forgive me if I've made a misunderstanding, but im a SVN man, not a CVS'er )
--
Kent
ruby -e '[1, 2, 4, 7, 0, 9, 5, 8, 3, 10, 11, 6, 12, 13].each{|x|
print "enNOSPicAMreil kdrtf@gma.com"[(2*x)..(2*x+1)]}'
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-06-08 7:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-07 11:43 [gentoo-dev] [RFC] Non-Dev Contributors and the Tree Michael Cummings
2007-06-07 14:50 ` Wulf C. Krueger
2007-06-07 22:38 ` [gentoo-dev] " Duncan
2007-06-08 1:50 ` Steve Long
2007-06-07 18:02 ` [gentoo-dev] " Chris Gianelloni
2007-06-07 18:34 ` Vlastimil Babka
2007-06-07 18:51 ` Wulf C. Krueger
2007-06-08 7:01 ` Kent Fredric [this message]
2007-06-08 14:39 ` [gentoo-dev] " Steve Long
2007-06-08 17:46 ` Stefan Schweizer
2007-06-10 19:16 ` Steve Long
2007-06-08 18:17 ` [gentoo-dev] " Elias Probst
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=8cd1ed20706080001g3a58b15ej3ef9fe67d143d80d@mail.gmail.com \
--to=kentfredric@gmail.com \
--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