From: Daniel Robbins <drobbins@funtoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] RFC: Expanding Foundation Bylaws, section 4.9 Termination from Membership
Date: Thu, 8 Feb 2018 14:34:33 -0700 [thread overview]
Message-ID: <CAPDOV49Xy+izCTxRUGXm405UzBcY3GJj1-Xwwi2JX5jBm0DgoQ@mail.gmail.com> (raw)
In-Reply-To: <20180208211814.GA19121@clocktown>
[-- Attachment #1: Type: text/plain, Size: 3743 bytes --]
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.
I understand what you are getting at though, but to make it sound better I
would take a positive stance, and list expectations in the Code of Conduct.
I'll will give you an example:
"Foundation members are expected to act in good faith to cooperate with
others and resolve problems constructively, including the use of our
official channels for dispute resolution. The Foundation reserves the right
to remove anyone's membership who they feel is being disruptive to the
project or not acting in the spirit of cooperation, and depending on the
severity of the behavior, this may not even include a warning. Therefore,
it is important that as a Foundation member that you are aware of this. We
expect that you will not only cooperate but act in a way that models
professionalism and respect -- that is our standard."
That's a friendly warning, and if people read it, I think they will feel
"Cool - the Foundation is trying to maintain a professional environment. I
can get behind that. And I know that they expect that from me and if I
deviate from that, I know what the consequences might be." Then I really
don't feel like the Trustees have any hoops they need to jump through to
remove people -- they can exercise their rights as described in the bylaws.
-Daniel
On Thu, Feb 8, 2018 at 2:18 PM, zlg <zlg@gentoo.org> wrote:
> On Wed, Feb 07, 2018 at 10:41:11PM -0700, Daniel Robbins wrote:
> > The current bylaws are sufficient.
> >
> > Threats should not be tolerated. It seems like right now, all it takes
> are
> > the trustees to vote on it to remove that member. Your addition leaves it
> > up to interpretation whether specified events fit the criteria you
> define,
> > which just make it more confusing than a simple vote of trustees in the
> > first place.
>
> All of our policies are written in a natural language, which leaves them
> open to interpretation by a human. How would you improve the wording of
> the criteria?
>
> >
> > So I don't think any of this helps; and with the videos at the end, it
> just
> > kind of seems paranoid.
>
> The intent was to show that the phenomenon is real and poses a threat to
> us. The all-caps warning was being respectful of the circumstances that
> people may be reading the list under. I thought I put enough thought and
> effort into my recommendation to not be written off and disregarded as
> paranoid. In an age where information is gathered en masse and
> often misused against people, I hardly consider it paranoid to be
> concerned about the safety of our members.
>
> Which bylaw(s) already cover legal threats? 4.9 is a bylaw with broad,
> general language that is also subject to interpretation. Our Code of
> Conduct does not cover this behavior, either. The closest thing is
> "mean-spirited", which is actually *less* specific than what I outlined.
>
> It comes down to this: these events *can* and *do* happen, and some of
> our members *have* threatened legal action in response to situations
> they didn't like. There is no denying any of that. What will Gentoo do
> about it when it's one of our own who loses their job or their life at
> the hands of an angry person with a phone? Should we stand by and wait
> until damage is done before acting? I think we can do better than that.
>
> As mentioned in my prior mail, it's a draft. Patches welcome.
> >
> > -Daniel
> >
> > On Wed, Feb 7, 2018 at 9:50 PM, zlg <zlg@gentoo.org> wrote:
> >
> > >[snip]
> > >
>
[-- Attachment #2: Type: text/html, Size: 4532 bytes --]
next prev parent reply other threads:[~2018-02-08 21:34 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 [this message]
2018-02-08 22:03 ` Rich Freeman
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=CAPDOV49Xy+izCTxRUGXm405UzBcY3GJj1-Xwwi2JX5jBm0DgoQ@mail.gmail.com \
--to=drobbins@funtoo.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