From: Alec Warner <antarus@gentoo.org>
To: gentoo-nfp <gentoo-nfp@lists.gentoo.org>
Subject: [gentoo-nfp] Next meeting; a motion to have 1 type of Gentoo member.
Date: Sun, 6 Nov 2016 18:32:59 -0800 [thread overview]
Message-ID: <CAAr7Pr-ZeH5YOGyT2M-YVn6k7KMmcLPRjwRHzUH_+Kgw6c6e4A@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1118 bytes --]
The foundation currently has 1 member type (in the bylaws) but Gentoo
itself still seems to have 2 (Gentoo staff and Ebuild developer)
This motion represents an idea that the community itself would only have 1
contributor type.
1) Contributors must take the staff quiz (which we should rename to the
contributor quiz.)
2) Contributors are encouraged to be foundation members, but membership is
not required. We may amend the contributor onboarding process to offer
foundation membership at the time they join Gentoo as a contributor.
3) Contributors that want access to the gentoo ebuild repository still need
to follow the normal recruiting process (ebuild quiz, mentor, 30 day
period.)
4) Contributors that do not want access to the gentoo ebuild repository
(because they contribute in other ways) do not need to take the ebuild
quiz. Its unclear if a 30 day grace period is required for non-ebuild
groups.
5) Existing developers and staff are rebranded as contributors.
If approved, I expect a few months of working with comrel to adjust
existing policy documents and recruiting guidelines to implement.
-A
[-- Attachment #2: Type: text/html, Size: 1362 bytes --]
next reply other threads:[~2016-11-07 2:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 2:32 Alec Warner [this message]
2016-11-07 4:55 ` [gentoo-nfp] Next meeting; a motion to have 1 type of Gentoo member Dean Stephens
2016-11-07 5:03 ` M. J. Everitt
2016-11-07 5:12 ` Matthew Thode
2016-11-08 4:57 ` Dean Stephens
2016-11-07 5:19 ` Matthew Thode
2016-11-07 11:50 ` Rich Freeman
2016-11-07 11:54 ` Kristian Fiskerstrand
2016-11-07 12:26 ` Rich Freeman
2016-11-07 16:57 ` David Abbott
2016-11-07 18:44 ` Alec Warner
2016-11-08 4:57 ` Dean Stephens
2016-11-07 18:35 ` Alec Warner
2016-11-08 4:57 ` Dean Stephens
2016-11-07 8:23 ` Sven Vermeulen
2016-11-07 8:28 ` Matthew Thode
2016-11-07 18:46 ` Alec Warner
2016-11-08 4:58 ` Dean Stephens
2016-11-07 8:52 ` Kristian Fiskerstrand
2016-11-07 10:52 ` Ulrich Mueller
2016-11-07 18:47 ` Alec Warner
2016-11-07 10:44 ` Roy Bamford
2016-11-07 10:59 ` Luca Barbato
2016-11-07 18:52 ` Alec Warner
2016-11-08 4:58 ` Dean Stephens
2016-11-09 7:29 ` [gentoo-nfp] " Michael Palimaka
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=CAAr7Pr-ZeH5YOGyT2M-YVn6k7KMmcLPRjwRHzUH_+Kgw6c6e4A@mail.gmail.com \
--to=antarus@gentoo.org \
--cc=gentoo-nfp@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