From: R0b0t1 <r030t1@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Mailing list moderation and community openness
Date: Tue, 27 Mar 2018 21:55:24 -0500 [thread overview]
Message-ID: <CAAD4mYj7PcdY68eavtSzdcvjhQBkGQc-jCrs0p82wup5mJWgYw@mail.gmail.com> (raw)
In-Reply-To: <CAGfcS_=wy70mVWtNCBCruWy-eA1TdKYGxX7VA6jWHTrAEcW_3g@mail.gmail.com>
I really do hate discussing this. I will pray for Gentoo, friends, as
I hope the distribution continues to receive useful contributions.
On Tue, Mar 27, 2018 at 11:39 AM, Rich Freeman <rich0@gentoo.org> wrote:
> Now a bunch of community members get upset about Fred being booted out
> without reason. Fred claims it is because he disagrees with the
> leadership on something. People start arguing endlessly about
> openness.
>
Explain why the user was removed.
> Ultimately the leaders just want Fred gone so that new contributors
> aren't getting driven away. They can't explain that because then they
> create potential civil liability for the project. The problem is that
> the debate goes on for over a year despite intervening elections and
> now this becomes the issue that is driving new contributors away.
>
This is insane. If they sue produce the emails. At least in the US,
the suit will be thrown out, as truth is a defense to defamation.
If I am not a lawyer and as such can not understand the law and my
opinion should not be trusted, then, as I assume you are not a lawyer,
your opinion should not be trusted either. Even if you have consulted
with a lawyer you are not a lawyer and there is no reason to believe
you could have understood what the lawyer told you.
I do not present this as sophistry: for any progress to be made in the
discussion of your hypothetical situation I sincerely think you need
to consider the above. At what point is one's knowledge of the law
enough to act within society?
> What solution would you propose for this problem? It isn't
> hypothetical at all - I can think of one case in Gentoo's past where
> this happened that I'm aware of, and I'd be shocked if it were the
> only one.
>
Stop using the law as a boogeyman.
Be transparent in why decisions were made. There are no legal concerns
save fair use (the copyright of any published emails) and the
publication of private facts.[1] For a tort involving the disclosure
of public facts, you would need to have no reason to publish those
facts save for the damage they could cause. You may also need to
publish them in a manner far more public than a Linux distribution
mailing list.
To continue the example I doubt anyone would care if it was just a
single Fred, though they may be slightly put off. Multiple Fred (or
related) incidents later it would seem rather strange.
As I have tried to explain my issue with the closure of the mailing
list is not the removal of a user, but the lack of openness with which
decisions are made. Points are brought up in good faith and then
ignored. Requests for clarification may not be greeted amicably.
Overall, this makes it seem like the closure of the development list
is to keep decisions from being questioned. If there were hecklers
asking stupid questions that would be one thing, but that is not what
it looks like to me.
I will note most developers go quietly about maintaining their charges
and make reasonable decisions.
Cheers,
R0b0t1
[1]: http://www.dmlp.org/legal-guide/publication-private-facts
next prev parent reply other threads:[~2018-03-28 2:55 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 12:17 [gentoo-dev] Mailing list moderation and community openness Michael Palimaka
2018-03-20 12:22 ` Kristian Fiskerstrand
2018-03-20 12:26 ` Lars Wendler
2018-03-20 13:41 ` Gregory Woodbury
2018-03-20 16:09 ` [gentoo-project] " Rich Freeman
2018-03-20 15:28 ` Matthew Thode
2018-03-20 18:17 ` Kristian Fiskerstrand
2018-03-21 23:56 ` Chí-Thanh Christopher Nguyễn
2018-03-22 0:24 ` Kristian Fiskerstrand
2018-03-21 5:36 ` Eray Aslan
2018-03-21 11:07 ` Rich Freeman
2018-03-21 14:44 ` Alec Warner
2018-03-21 16:31 ` Eray Aslan
2018-03-21 16:46 ` Alec Warner
2018-03-21 16:55 ` R0b0t1
2018-03-21 17:19 ` Rich Freeman
2018-03-21 23:44 ` Gregory Woodbury
2018-03-22 5:24 ` [gentoo-dev] " Duncan
2018-03-20 15:44 ` [gentoo-dev] " Alexander Berntsen
2018-03-20 16:03 ` William Hubbs
2018-03-20 23:54 ` Benda Xu
2018-03-21 0:08 ` Rich Freeman
2018-03-21 23:56 ` Chí-Thanh Christopher Nguyễn
2018-03-22 0:33 ` Kristian Fiskerstrand
2018-03-22 0:37 ` M. J. Everitt
2018-03-22 6:31 ` Benda Xu
2018-03-22 8:30 ` Alexander Berntsen
2018-03-22 11:38 ` Rich Freeman
2018-03-22 12:07 ` Kristian Fiskerstrand
2018-03-27 1:19 ` kuzetsa
2018-03-27 1:26 ` Rich Freeman
2018-03-27 2:38 ` kuzetsa
2018-03-27 7:35 ` Rich Freeman
2018-03-27 7:34 ` [gentoo-dev] " Martin Vaeth
2018-03-27 12:55 ` Rich Freeman
2018-03-27 16:12 ` Martin Vaeth
2018-03-27 16:39 ` Rich Freeman
2018-03-28 2:21 ` M. J. Everitt
2018-03-28 2:55 ` R0b0t1 [this message]
2018-03-28 4:41 ` Stephen Christie
2018-03-28 13:48 ` Michael Orlitzky
2018-03-28 11:03 ` Rich Freeman
2018-03-28 6:11 ` Dawid Weglinski
2018-03-28 6:33 ` Martin Vaeth
2018-03-28 11:21 ` Rich Freeman
2018-03-29 7:13 ` Martin Vaeth
2018-06-11 1:55 ` R0b0t1
2018-03-20 15:53 ` [gentoo-dev] " Pengcheng Xu
2018-03-21 2:22 ` Paweł Hajdan, Jr.
2018-03-21 23:56 ` Chí-Thanh Christopher Nguyễn
2018-03-22 0:27 ` Kristian Fiskerstrand
2018-06-10 18:29 ` Tom Wijsman
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=CAAD4mYj7PcdY68eavtSzdcvjhQBkGQc-jCrs0p82wup5mJWgYw@mail.gmail.com \
--to=r030t1@gmail.com \
--cc=gentoo-dev@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