From: zlg <zlg@gentoo.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:00:06 -0800 [thread overview]
Message-ID: <20180209090006.GC20340@clocktown> (raw)
In-Reply-To: <23165.22019.87619.931665@a1i15.kph.uni-mainz.de>
[-- Attachment #1: Type: text/plain, Size: 1998 bytes --]
On Fri, Feb 09, 2018 at 09:04:19AM +0100, Ulrich Mueller wrote:
> >>>>> On Fri, 9 Feb 2018, Daniel Robbins wrote:
>
> [Please don't top-post.]
>
> > You are using hyperbole. A majority vote of trustees is required.
> > That is not haphazard, as you state -- it is a process that requires
> > majority consensus of elected officials. We assume that the trustees
> > are looking out for the project. The trustees are there to protect
> > the community so they must have this ability.
>
> 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).
>
> Ulrich
From what I've seen, a common approach to conflict resolution is via the
bug-tracker, or e-mails to comrel. These create 'paper trails' for us,
so I don't think that's much of a problem in terms of discovery. The
Trustees could suggest that official channels be used before petitioning
them for a decision on Foundation membership. They are not required to
do so, but I agree that knowing the reason is helpful. And instead of
the reasoning being some sort of rationale, it should be something
grounded in fact and fact alone:
"You did X, which we have communicated results in Y. Z person went
through our official channels and those channels failed to resolve the
situation. Thus, the Trustees are taking action to protect the
Foundation and community. You may re-apply for Foundation membership on
[date]."
Anything less is favoritism or double-standard. If we cannot enforce our
guidelines evenly, then we lack credibility and don't deserve to be
taken seriously.
Enforcement is made difficult because we allow our decisions to be
impacted by the social status of the person who is being claimed
against. Others see this, and it reduces our reputation.
Short, fact-oriented messaging I think is the way to go for enforcement.
~zlg
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-02-09 9:00 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
2018-02-09 9:00 ` zlg [this message]
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=20180209090006.GC20340@clocktown \
--to=zlg@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