From: Rich Freeman <rich0@gentoo.org>
To: gentoo-project <gentoo-project@lists.gentoo.org>
Subject: Re: [gentoo-project] RFC: Expanding Foundation Bylaws, section 4.9 Termination from Membership
Date: Thu, 8 Feb 2018 17:03:07 -0500 [thread overview]
Message-ID: <CAGfcS_kHaCQDBX31KuRkO6Yhj2WVhPnLfHPGe5sbwb8bbOgqpg@mail.gmail.com> (raw)
In-Reply-To: <CAPDOV49Xy+izCTxRUGXm405UzBcY3GJj1-Xwwi2JX5jBm0DgoQ@mail.gmail.com>
On Thu, Feb 8, 2018 at 4:34 PM, Daniel Robbins <drobbins@funtoo.org> wrote:
> I think the "rules" as it stands give the trustees the ability to remove any
> member that they feel is disruptive or not good for the project. They don't
> need to provide a reason or justification. It is at their discretion. So
> disruptive people can be removed. If I am misunderstanding this, let me
> know.
Indeed, I'd even go further and simplify the bylaw to say:
Section 4.9. Termination from Membership.
Membership may be terminated by a majority vote of the board of trustees.
And just leave it at that.
If you're concerned about somebody threatening to sue, then it is
probably better to NOT give them a reason for dismissal, unless
specifically required to do so by law.
If the law doesn't require a reason, and you don't give a reason, then
they don't really have much ground for argument. If you do give a
reason, you've now given them something to argue with when there was
no need to do so.
IMO a better defense against Gentoo volunteers being sued is to join
an umbrella that is actually equipped to handle these situations, and
which will probably be less likely to give people grounds to sue,
especially since they would no longer have standing as members to do
so.
And keep in mind that kicking somebody out doesn't really diminish
their standing to sue, since they can potentially sue based on actions
taken while they were a member, and the loss of membership becomes one
more cause for action.
--
Rich
next prev parent reply other threads:[~2018-02-08 22:03 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 4:50 [gentoo-project] RFC: Expanding Foundation Bylaws, section 4.9 Termination from Membership zlg
2018-02-08 5:41 ` Daniel Robbins
2018-02-08 21:18 ` zlg
2018-02-08 21:34 ` Daniel Robbins
2018-02-08 22:03 ` Rich Freeman [this message]
2018-02-08 22:17 ` Matthew Thode
2018-02-08 22:33 ` Daniel Robbins
2018-02-08 22:39 ` Matthew Thode
2018-02-09 7:32 ` Ulrich Mueller
2018-02-09 7:48 ` Daniel Robbins
2018-02-09 8:04 ` Ulrich Mueller
2018-02-09 8:20 ` Daniel Robbins
2018-02-09 9:00 ` zlg
2018-02-10 17:29 ` Andreas K. Huettel
2018-02-09 14:23 ` Matthew Thode
2018-02-09 8:24 ` Michał Górny
2018-02-09 8:32 ` Daniel Robbins
2018-02-10 17:17 ` Andreas K. Huettel
2018-02-08 22:29 ` Daniel Robbins
2018-02-08 22:43 ` zlg
2018-02-08 23:04 ` Daniel Robbins
2018-02-08 23:12 ` M. J. Everitt
2018-02-10 17:39 ` Andreas K. Huettel
2018-02-10 22:31 ` Daniel Robbins
2018-02-10 22:36 ` Daniel Robbins
2018-02-10 22:46 ` Andreas K. Huettel
2018-02-10 22:57 ` Michał Górny
2018-02-10 23:16 ` Matthew Thode
2018-02-11 5:03 ` Daniel Robbins
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=CAGfcS_kHaCQDBX31KuRkO6Yhj2WVhPnLfHPGe5sbwb8bbOgqpg@mail.gmail.com \
--to=rich0@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