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: Fri, 9 Feb 2018 01:20:05 -0700 [thread overview]
Message-ID: <CAPDOV4-4JZJxbwRDiRoqZoAfU8xH5NJyBbntirQ5oHP9oyMKOg@mail.gmail.com> (raw)
In-Reply-To: <23165.22019.87619.931665@a1i15.kph.uni-mainz.de>
[-- Attachment #1: Type: text/plain, Size: 1040 bytes --]
On Fri, Feb 9, 2018 at 1:04 AM, Ulrich Mueller <ulm@gentoo.org> wrote:
>
>
> I don't disagree with this. Still, trustees should not be able to
> exclude a member without a reason, and they should communicate that
> reason (not necessarily in public, but at least to the excluded
> member)
Well, they would need to have a reason to go through the hassle of removing
a member. I would be more concerned that they would communicate a general
reason to the Gentoo community so that there would be some accountability.
Of course, this is a delicate balancing act -- how much information to
share, etc. I think it would be highly specific on the circumstances how
much information is appropriate to share, which would be hard to predict
ahead of time and make rules about. I think that in these circumstances,
the more reason/justification that is provided, the more 'ammunition' you
are giving to a potentially combative person to continue a conflict that
the trustees are desperately trying to end for the sake of the project.
Best,
Daniel
[-- Attachment #2: Type: text/html, Size: 1424 bytes --]
next prev parent reply other threads:[~2018-02-09 8:20 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
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 [this message]
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=CAPDOV4-4JZJxbwRDiRoqZoAfU8xH5NJyBbntirQ5oHP9oyMKOg@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