public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Raymond Jennings <shentino@gmail.com>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Foundation membership and who can join
Date: Fri, 14 Oct 2016 08:03:24 -0700	[thread overview]
Message-ID: <CAGDaZ_r++wp724iGLkyOxwqSdUwqZq99tugW_xYf1JHW=nkNqw@mail.gmail.com> (raw)
In-Reply-To: <40838d7f-9c91-6074-4df8-5d053d6ace52@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 2211 bytes --]

This is why I oppose mooshing the roles together.

An ebuild maintaining nerd/codemonkey type may have little interest in
foundation politics, and vice versa.  We should not force them to shoulder
roles they don't want.

As long as they're willing to play nice with the community, they should be
allowed to offer their support in any way they see fit.  I don't think
putting vote quotas on anyone is going to help.

On Fri, Oct 14, 2016 at 7:45 AM, Ian Stakenvicius <axs@gentoo.org> wrote:

> On 14/10/16 10:35 AM, Rich Freeman wrote:
> > On Fri, Oct 14, 2016 at 10:17 AM, Ian Stakenvicius <axs@gentoo.org>
> wrote:
> >> On 14/10/16 08:43 AM, Rich Freeman wrote:
> >>>
> >>> [...] two different pools of voters (Foundation members and
> >>> "Developers" (which today includes anybody with an @g.o address even
> >>> if they don't have commit access - the proposal splits that into Staff
> >>> and Developers)
> >>
> >>
> >> By definition #1, if you're a dev then you're staff; staff is a
> >> superset of dev but there's no separation there based on the
> >> definitions listed.  There needs to be a classification for
> >> non-staff-dev if a dev loses foundation membership due to the
> >> staff<->foundation hard coupling and whatever rules there are that
> >> revokes foundation membership and therefore staff status, but can
> >> still remain a dev.
> >>
> >> OR, don't couple dev to staff so that devs have a different (sub)set
> >> of rules regarding foundation membership revocation.
> >
> > My intent is that anybody who ceases to be a Foundation member also
> > loses membership in staff, dev, and loses commit access.
> >
> > Again, the point is to keep Foundation membership strictly in-line
> > with what are currently today developers.  This means that the same
> > people who vote for Council also vote for the Trustees.  (Today staff
> > are also considered developers and do vote for the Council.)
>
>
> Excellent.  *THIS* makes things very clear.
>
> Now, I forsee there being some push-back from a dev losing their
> gentoo-repo commit rights if they abstain from voting in two
> (consecutive?) Foundation elections....but that's a separate issue
> that can be addressed on its own.
>
>
>
>
>

[-- Attachment #2: Type: text/html, Size: 2943 bytes --]

  reply	other threads:[~2016-10-14 15:04 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-13 16:35 [gentoo-project] Foundation membership and who can join Matthew Thode
2016-10-13 17:14 ` Matthew Thode
2016-10-13 17:29 ` William L. Thomson Jr.
2016-10-13 18:16   ` Matthew Thode
2016-10-13 19:16     ` Roy Bamford
2016-10-13 19:37       ` William L. Thomson Jr.
2016-10-13 17:39 ` [gentoo-project] Re: [gentoo-nfp] " Alec Warner
2016-10-13 17:59   ` William L. Thomson Jr.
2016-10-13 18:27 ` Roy Bamford
2016-10-13 18:56 ` [gentoo-project] " Rich Freeman
2016-10-14  4:31   ` Daniel Campbell
2016-10-14  4:33     ` M. J. Everitt
2016-10-13 19:25 ` Matthew Thode
2016-10-13 19:28   ` Raymond Jennings
2016-10-14  0:44     ` NP-Hardass
2016-10-14  0:53       ` Rich Freeman
2016-10-14  1:04         ` Matthew Thode
2016-10-14  7:59         ` Raymond Jennings
2016-10-14 15:49           ` Matthew Thode
2016-10-14  4:30     ` William L. Thomson Jr.
2016-10-14  1:06 ` Matthew Thode
2016-10-14  3:33   ` Ian Stakenvicius
2016-10-14  3:48     ` Matthew Thode
2016-10-14  8:47       ` Roy Bamford
2016-10-14  8:52         ` Raymond Jennings
2016-10-14 12:08         ` Ian Stakenvicius
2016-10-14 12:43           ` Rich Freeman
2016-10-14 13:07             ` Raymond Jennings
2016-10-14 13:46               ` Rich Freeman
2016-10-14 13:55                 ` Ian Stakenvicius
2016-10-14 14:04                   ` Raymond Jennings
2016-10-14 14:13                     ` Ian Stakenvicius
2016-10-14 14:16                       ` Raymond Jennings
2016-10-14 14:17             ` Ian Stakenvicius
2016-10-14 14:35               ` Rich Freeman
2016-10-14 14:45                 ` Ian Stakenvicius
2016-10-14 15:03                   ` Raymond Jennings [this message]
2016-10-14 15:15                     ` Rich Freeman
2016-10-14 15:43                       ` NP-Hardass
2016-10-14 16:20                         ` Matthew Thode
2016-10-14 16:33                           ` NP-Hardass
2016-10-14 16:42                             ` NP-Hardass
2016-10-15  9:51                         ` Roy Bamford
2016-10-23  8:08               ` Daniel Campbell
2016-10-14  4:37   ` Nick Vinson
2016-10-14  6:52     ` Michał Górny
2016-10-14  7:51       ` Raymond Jennings
2016-10-14 16:57         ` Robin H. Johnson
2016-10-14 17:03           ` William L. Thomson Jr.
2016-10-14 18:28             ` Raymond Jennings
2016-10-14 18:55               ` William L. Thomson Jr.
2016-10-14 18:57                 ` Raymond Jennings
2016-10-14 19:19                   ` William L. Thomson Jr.
2016-10-14 19:23                     ` Raymond Jennings
2016-10-14 19:34                       ` William L. Thomson Jr.
2016-10-14 19:36                         ` Raymond Jennings
2016-10-14 19:40                           ` William L. Thomson Jr.
2016-10-14 20:35                             ` Ian Stakenvicius
  -- strict thread matches above, loose matches on Subject: below --
2016-10-13 19:50 John R. Graham
2016-10-14  0:47 ` NP-Hardass

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='CAGDaZ_r++wp724iGLkyOxwqSdUwqZq99tugW_xYf1JHW=nkNqw@mail.gmail.com' \
    --to=shentino@gmail.com \
    --cc=gentoo-project@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