public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Vlastimil Babka <caster@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Non-Dev Contributors and the Tree
Date: Thu, 07 Jun 2007 20:34:37 +0200	[thread overview]
Message-ID: <46684FBD.7010105@gentoo.org> (raw)
In-Reply-To: <1181239361.15396.63.camel@workbox.quova.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Chris Gianelloni wrote:
> On Thu, 2007-06-07 at 07:43 -0400, Michael Cummings wrote:
>> What I would like to propose is that we have an official (yes, official)
>> cvs overlay that is used by developers *and* contributors to commit new
>> ebuilds and changes to. Mirrors would still pull, as they always have,
>> from the gentoo-x86 cvs repo. "Official" Gentoo developers would then be
>> able to take from the overlay and commit to the main tree at will, but
>> have a common stomping ground for contributors and developers to work in
>> without fear of breaking the rest of the tree. We reward those users
>> (pardon the terms if you find that condescending, its not intended as
>> such) with the drive and passion, but not the means, resources, or time,
>> by making them contributors to this overlay, where they can make cvs
>> commits.
>>
>> This overlay wouldn't necessarily need to be the whole of the tree,
>> either. Some areas, such as profiles, could be absent, as well as select
>> projects (perhaps the kernel and toolchain portions?). These
>> contributors wouldn't need to have a flood of @gentoo.org email
>> addresses - they are only contributors who, for whatever reason, are not
>> actually full scale developers.
> 
> I'm just asking, but isn't this exactly what Sunrise is supposed to be?
> 
> Isn't this the reason it was approved by the previous Council?

Well the difference is that AFAIK Sunrise is just for maintainer-wanted
stuff that's not in the tree yet, but Michael talks about (rev)bumps of
stuff that's already in tree.

Personally I think that project/herd overlays with non-dev contributors
already work well (at least for Java team) and don't see much benefit in
some overlay for everything.
- --
Vlastimil Babka (Caster)
Gentoo/Java
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGaE+8tbrAj05h3oQRAqtqAKCeMu7nTKYosVtvMhQZxQXdz0wHhQCglNqa
uBMP6ZZCoidKPlgruJWt6gE=
=wsIC
-----END PGP SIGNATURE-----
-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2007-06-07 18:38 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 [this message]
2007-06-07 18:51     ` Wulf C. Krueger
2007-06-08  7:01 ` Kent Fredric
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=46684FBD.7010105@gentoo.org \
    --to=caster@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