From: David Abbott <dabbott@gentoo.org>
To: gentoo-project <gentoo-project@lists.gentoo.org>
Cc: mentors@gentoo.org
Subject: Re: [gentoo-project] Merging Trustees and Council / Developers and Foundation
Date: Thu, 5 Jan 2017 18:20:01 -0500 [thread overview]
Message-ID: <CACs9S6aTJjU9MGZznXWRDtq62AXuo9O7dSBaFbFTiyyq3+xOWg@mail.gmail.com> (raw)
In-Reply-To: <CAGDaZ_pDtS6=b2gn3pxPHjqSk9XcT57E4Ori7wNm2hxhSjx6yA@mail.gmail.com>
On Thu, Jan 5, 2017 at 6:03 PM, Raymond Jennings <shentino@gmail.com> wrote:
> So, just to double check, and for the purpose of verification, what is the
> exact step by step method for becoming a "developer" of the kind that has a
> @g.o, and not necessarily a developer with full commit access?
>
> And more to the point, is current documentation on the subject accurate and
> up to date?
[see below]
>
>
> On Thu, Jan 5, 2017 at 2:54 PM, Rich Freeman <rich0@gentoo.org> wrote:
>>
>> On Thu, Jan 5, 2017 at 5:20 PM, Raymond Jennings <shentino@gmail.com>
>> wrote:
>> > I personally oppose merging the foundation and dev community.
>> >
>> > As someone else pointed out, there are ways to contribute to gentoo that
>> > do
>> > not involve developing.
>>
>> Developer = having an @gentoo.org email address. People who are
>> significant contributors in any way should be able to apply to get
>> these, and the process already exists for this.
>>
>> We used to make a distinction between "developers" and "staff." Now
>> it seems the preferred terms are developers with and without commit
>> access.
>>
>> --
>> Rich
>>
>
Raymond,
Try not to top post.
First you need a mentor to become a developer, with or without commit access.
This seems pretty up to date;
https://wiki.gentoo.org/wiki/Project:Recruiters/Quiz#Quiz_selection_2
--
David Abbott (dabbott)
Gentoo Foundation Secretary
http://dev.gentoo.org/~dabbott/
next prev parent reply other threads:[~2017-01-05 23:20 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 21:36 [gentoo-project] Merging Trustees and Council / Developers and Foundation Matthew Thode
2017-01-05 21:56 ` Michał Górny
2017-01-05 22:02 ` Matthew Thode
2017-01-05 22:14 ` Michał Górny
2017-01-05 22:17 ` William L. Thomson Jr.
2017-01-10 5:32 ` Daniel Campbell
2017-01-06 10:43 ` Andreas K. Huettel
2017-01-06 15:28 ` William L. Thomson Jr.
2017-01-10 5:35 ` Daniel Campbell
2017-01-05 22:03 ` M. J. Everitt
2017-01-05 22:14 ` William L. Thomson Jr.
2017-01-06 10:48 ` Andreas K. Huettel
2017-01-06 15:15 ` [gentoo-project] OT " William L. Thomson Jr.
[not found] ` <8835202.ILOODCAab9@wlt>
2017-01-06 15:31 ` William L. Thomson Jr.
2017-01-10 5:39 ` [gentoo-project] " Daniel Campbell
2017-01-10 6:21 ` Matthew Thode
2017-01-06 0:41 ` Alec Warner
2017-01-06 1:15 ` Rich Freeman
2017-01-06 10:40 ` Andreas K. Huettel
2017-01-06 15:37 ` William L. Thomson Jr.
2017-01-05 21:57 ` Kristian Fiskerstrand
2017-01-05 22:10 ` [gentoo-nfp] " Matthew Thode
2017-01-05 22:17 ` Kristian Fiskerstrand
2017-01-05 22:20 ` Raymond Jennings
2017-01-05 22:54 ` Rich Freeman
2017-01-05 23:03 ` Raymond Jennings
2017-01-05 23:20 ` David Abbott [this message]
2017-01-06 12:10 ` Andreas K. Huettel
2017-01-06 14:47 ` Rich Freeman
2017-01-06 16:22 ` William L. Thomson Jr.
2017-01-10 5:55 ` Daniel Campbell
2017-01-06 15:57 ` William L. Thomson Jr.
2017-01-06 16:24 ` Rich Freeman
2017-01-06 16:41 ` William L. Thomson Jr.
2017-01-06 16:51 ` Rich Freeman
2017-01-06 17:09 ` William L. Thomson Jr.
2017-01-06 17:13 ` Andreas K. Huettel
2017-01-06 17:19 ` Matthew Thode
2017-01-06 17:37 ` Raymond Jennings
2017-01-06 18:15 ` Rich Freeman
2017-01-06 18:31 ` Raymond Jennings
2017-01-06 17:26 ` Alec Warner
2017-01-06 17:37 ` William L. Thomson Jr.
2017-01-06 18:43 ` Alec Warner
2017-01-06 20:22 ` William L. Thomson Jr.
2017-01-10 6:19 ` Daniel Campbell
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=CACs9S6aTJjU9MGZznXWRDtq62AXuo9O7dSBaFbFTiyyq3+xOWg@mail.gmail.com \
--to=dabbott@gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
--cc=mentors@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