From: Fabian Groffen <grobian@gentoo.org>
To: gentoo-alt@lists.gentoo.org
Subject: Re: [gentoo-alt] Best Practice in Adopting New Ebuilds in Prefix
Date: Sat, 6 Aug 2011 09:37:37 +0200 [thread overview]
Message-ID: <20110806073737.GZ20656@gentoo.org> (raw)
In-Reply-To: <86aabnwdqz.fsf@gmail.com>
Hi Benda,
On 06-08-2011 10:05:40 +0900, heroxbd@gmail.com wrote:
> I guess becoming a developer particular for Gentoo Prefix is somewhat
> different than that of gx86, in that I don't need to do those practice
> in the overlays?
>
> Where should I start from now? Maybe this quiz[1]?
There is no difference in the recruitment (and status) between
Prefix-enabled developers and normal Gentoo developers.
(I made that Prefix-enabled up, right here ... :) )
You'll have to go through the normal Gentoo recruitment process [2], and
before I grant you access to the prefix overlay [3], I ask you to fill
in my Prefix quiz [1], so you learn about certain things that are often
go wrong.
We'll find someone to mentor you, you don't have to do that yourself.
> [1] http://dev.gentoo.org/~grobian/prefix-quiz
[2] http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=1&chap=2
[3] http://overlays.gentoo.org/proj/alt/browser/trunk/prefix-overlay
--
Fabian Groffen
Gentoo on a different level
next prev parent reply other threads:[~2011-08-06 8:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-03 1:36 [gentoo-alt] Best Practice in Adopting New Ebuilds in Prefix heroxbd
2011-08-03 5:49 ` Zac Medico
2011-08-06 0:13 ` heroxbd
2011-08-06 0:42 ` Zac Medico
2011-08-06 1:24 ` heroxbd
2011-08-03 8:07 ` Fabian Groffen
2011-08-06 1:05 ` heroxbd
2011-08-06 7:37 ` Fabian Groffen [this message]
2011-08-10 1:17 ` heroxbd
2011-08-10 6:44 ` Fabian Groffen
2011-08-05 20:00 ` Jeremy Olexa
2011-08-10 1:31 ` heroxbd
2011-08-10 4:42 ` Jeremy Olexa
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=20110806073737.GZ20656@gentoo.org \
--to=grobian@gentoo.org \
--cc=gentoo-alt@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