From: Stefan Schweizer <genstef@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: [RFC] Non-Dev Contributors and the Tree
Date: Fri, 08 Jun 2007 19:46:39 +0200 [thread overview]
Message-ID: <f4c4mb$8s1$1@sea.gmane.org> (raw)
In-Reply-To: f4bpqb$v14$1@sea.gmane.org
Steve Long wrote:
> Dunno what the procedure might end up becoming, but my understanding is
> commit right to the sunrise overlay, from where a dev has to commit it to
> the main tree. It seems like a logical extension of sunrise, and i am sure
> there are stats on who has submitted what to sunrise in the past. So there
> is a baseline for whom to invite to become <insertNameOfNewPost>s.
Snrise already has such an "extension". A portage-review/ subdirectory,
where ebuilds from the gentoo-x86 + changes can be posted. A dev then takes
those and reviews them to the main tree and removes them again from the dir
The process has worked really good so far. I suggest you to read up on how
this is currently being done on overlays.gentoo.org/proj/sunrise and if you
are interested I invite you to join #gentoo-sunrise to see how it is done.
The current log:
http://overlays.gentoo.org/proj/sunrise/log/portage-review
You will notice the regular "in portage", "now reviewed", "in cvs" messages
Best regards,
Stefan
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-06-08 17:50 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
2007-06-08 14:39 ` [gentoo-dev] " Steve Long
2007-06-08 17:46 ` Stefan Schweizer [this message]
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='f4c4mb$8s1$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