public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Matthew Thode <prometheanfire@gentoo.org>
To: gentoo-project@lists.gentoo.org
Cc: gentoo-nfp <gentoo-nfp@lists.gentoo.org>
Subject: Re: [gentoo-project] Foundation membership and who can join
Date: Fri, 14 Oct 2016 11:20:24 -0500	[thread overview]
Message-ID: <316f6264-5304-47a7-4ba7-f943fe6ce952@gentoo.org> (raw)
In-Reply-To: <ccd61ffb-de97-bca5-e475-23cfe09cb187@gentoo.org>


[-- Attachment #1.1: Type: text/plain, Size: 4168 bytes --]

On 10/14/2016 10:43 AM, NP-Hardass wrote:
> On 10/14/2016 11:15 AM, Rich Freeman wrote:
>> On Fri, Oct 14, 2016 at 11:03 AM, Raymond Jennings <shentino@gmail.com> wrote:
>>> 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.
>>>
>>
>> It is a valid argument, but it does then lead to the situation where
>> we have diverging foundation and dev membership, which means that if
>> you post the same question to both groups, you could get different
>> answers, and thus conflict.
>>
>> However, this could be mitigated a great deal if we still purged
>> foundation members who are no longer active staff/devs, while keeping
>> foundation membership optional for those who are, and if somebody
>> loses foundation membership due to not voting they could ask to be
>> allowed back in.  Then while somebody might not be voting for who the
>> Trustees are, they can't really complain because they need only ask
>> for the ability to vote for them, and crisis could be averted.
>>
> 
> What exactly are the requirements for quorum as necessitated by NM law?
> How do explicit abstains from a vote affect that if they do?   If
> explicit abstention is allowed, then make voting completely compulsory,
> and those that do not feel that they have a desire to put a filled
> ballot forward are required to submit a ballot of abstention.   This
> might alleviate some of the concerns of developers being forced to vote
> for trustees, while still putting developers in a position where they
> have to weigh what degree they wish to weigh in on such a matter.
> IANAL, but my suspicion is that the law only mandates that a quorum be
> present, not that a quorum vote one way or another.  According to this
> document [1], abstentions only affect votes where the
> quorum/majority/unanimity is required of *present* voters, thus votes
> where only quorum/majority/unanimity of total votes is required,
> abstention is removed entirely from the assessment of quorum for the
> decision itself.
> 
I think I found it.

http://www.sos.state.nm.us/uploads/files/Corporations/ch53Art11.pdf
page 93 - 53-11-32

I wasn't able to find any info on abstaining.  As far as I could tell a
'rolling quorum' (just those present) can't make decisions.

http://www.nmag.gov/uploads/files/Publications/ComplianceGuides/Open%20Meetings%20Act%20Compliance%20Guide%202015.pdf

> Note, in the document from NM [2], I couldn't find specific reference to
> this (and we should speak to a lawyer), but there are some points where
> quorum is discussed of present members and some where it is discussed in
> relation to the entirety of the body.
> 
> TL;DR: It might be possible to force all to vote, and but permit
> abstentions in the case of the trustees election.  This might allow an
> easier time aligning the bodies while not forcing developers to forcibly
> vote where they might not have an opinion.
> 
> Please note, the above might be worth looking into regardless of whether
> we align the voting bodies as it might make achieving a quorum in future
> votes more attainable.
> 
> 
> 
> Regardless of quorum requirements, if we align the Foundation and Staff
> memberships, and make voting compulsory (within a 2 year period), it
> might be wise to loosen the voting periods to make it easier for members
> to vote, i.e. if voting is open for 2 weeks currently, make it open for
> 4 weeks as a month should be ample time to cast a vote, whether it be
> abstention (if allowed) or a filled ballot.
> 
> 
> 
Altering what constitutes a quorum can only be done by altering the
articles of incorporation (as far as I can tell).  We might be able to
extend the voting period though.

-- 
-- Matthew Thode (prometheanfire)


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  reply	other threads:[~2016-10-14 16:20 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
2016-10-14 15:15                     ` Rich Freeman
2016-10-14 15:43                       ` NP-Hardass
2016-10-14 16:20                         ` Matthew Thode [this message]
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=316f6264-5304-47a7-4ba7-f943fe6ce952@gentoo.org \
    --to=prometheanfire@gentoo.org \
    --cc=gentoo-nfp@lists.gentoo.org \
    --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