public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Non-Dev Contributors and the Tree
Date: Thu, 07 Jun 2007 11:02:41 -0700	[thread overview]
Message-ID: <1181239361.15396.63.camel@workbox.quova.com> (raw)
In-Reply-To: <4667EF71.9010103@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1517 bytes --]

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?

-- 
Chris Gianelloni
Release Engineering Strategic Lead
Alpha/AMD64/x86 Architecture Teams
Games Developer/Council Member/Foundation Trustee
Gentoo Foundation

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2007-06-07 18:09 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 ` Chris Gianelloni [this message]
2007-06-07 18:34   ` [gentoo-dev] " Vlastimil Babka
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=1181239361.15396.63.camel@workbox.quova.com \
    --to=wolf31o2@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