From: Matthew Thode <prometheanfire@gentoo.org>
To: gentoo-nfp@lists.gentoo.org
Subject: Re: [gentoo-nfp] Next meeting; a motion to have 1 type of Gentoo member.
Date: Sun, 6 Nov 2016 23:12:59 -0600 [thread overview]
Message-ID: <a22565d5-bd34-4d7c-8886-1114ab3e5f67@gentoo.org> (raw)
In-Reply-To: <58200B2A.2080304@iee.org>
[-- Attachment #1.1: Type: text/plain, Size: 3040 bytes --]
On 11/06/2016 11:03 PM, M. J. Everitt wrote:
> On 07/11/16 04:55, Dean Stephens wrote:
>> On 11/06/16 21:32, Alec Warner wrote:
>>> The foundation currently has 1 member type (in the bylaws) but Gentoo
>>> itself still seems to have 2 (Gentoo staff and Ebuild developer)
>>>
>> Which is a problem in exactly what way? What actual practical benefit is
>> being sought by means of this proposal?
>>
>>> 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.)
>>>
>> Which is already a a subset of the developer quiz, with the exception of
>> two questions that are unique to the staff quiz. If you want devs to be
>> required to describe what ~ARCH is and whether users need to know what
>> EAPI is, there are less labor intensive ways of achieving that goal.
>> Also, are you seriously proposing that anyone who submits a patch or
>> files a bug or helps other users in any of the various support channels
>> must take a quiz first, or do they not "contribute"?
>>
>>> 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.
>>>
>> Which is the status quo, just with the proposed renaming.
>>
>>> 3) Contributors that want access to the gentoo ebuild repository still need
>>> to follow the normal recruiting process (ebuild quiz, mentor, 30 day
>>> period.)
>>>
>> So, again, effectively the status quo.
>>> 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.
>>>
>> And, yet again, the status quo.
>>
>>> 5) Existing developers and staff are rebranded as contributors.
>>>
>> Why "rebrand" anyone?
>>
>>> If approved, I expect a few months of working with comrel to adjust
>>> existing policy documents and recruiting guidelines to implement.
>>>
>> Does comrel really need more to do? Even merely dropping the staff quiz
>> questions from the developer quiz and changing all documentation to
>> describe everyone as a "contributor" takes time, and you introduce
>> another round of quiz taking for new ebuild developers when taking too
>> much time to get through the quizzes is already probably the most
>> commonly complained about part of recruiting new ebuild developers.
>>> -A
>>>
>>
> With respect, I believe you're missing the point of what Alec and Matt
> are trying to do. Which is predominately formalise and Document the
> status quo, so there is less misunderstanding from the inside and out.
>
I can't speak for Alec, but it's my opinion that this is a change, but a
needed one, I'll reply to the other email on it's own.
--
-- Matthew Thode (prometheanfire)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2016-11-07 5:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 2:32 [gentoo-nfp] Next meeting; a motion to have 1 type of Gentoo member Alec Warner
2016-11-07 4:55 ` Dean Stephens
2016-11-07 5:03 ` M. J. Everitt
2016-11-07 5:12 ` Matthew Thode [this message]
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=a22565d5-bd34-4d7c-8886-1114ab3e5f67@gentoo.org \
--to=prometheanfire@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