From: Rich Freeman <rich0@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] ComRel / disciplinary action reform proposal
Date: Tue, 17 Jan 2017 14:03:56 -0500 [thread overview]
Message-ID: <CAGfcS_mTspzJih+=o5B0bX4AeTRF1FGcqQ6xqL1ybNz76zxE0g@mail.gmail.com> (raw)
In-Reply-To: <assp.01902c546b.1850599.PWcJoYvLOJ@wlt>
On Tue, Jan 17, 2017 at 1:54 PM, William L. Thomson Jr.
<wlt-ml@o-sinc.com> wrote:
>
> This is an area I do care about as it has effected me likely more than anyone.
> I am not sure anyone has tried to return for some 8+ years. Or the amount of
> attempts I have to return. During every attempt Comrel/Devrel has bee in the
> way. A problem they started years ago by getting involved when they need not.
>
> ...
>
> I am quite aware. I have been moderated several times. I have seen the harm
> that protecting the community via moderation causes. The damage is far worse
> than what they seek to prevent in the first place.
Hmm, I can't imagine that if you have been moderated several times
that it might have some bearing on why you feel that Comrel/Devrel has
tended to get in the way of your rejoining...
In any case, as has been pointed out you could have appealed these
issues and would likely have gotten a final answer one way or the
other by now. But then we can't just complain about them forever.
> I am not sure anyone around Gentoo has been treated as poorly as I have. Very
> few would stick around for the punishment I get on the regular.
Indeed, most people who regularly get moderated tend to go away. I'm
not sure that is entirely a bad thing.
If people are willing to change they can of course stick around, and
if abuse is a concern that is why we have appeals.
--
Rich
next prev parent reply other threads:[~2017-01-17 19:03 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-15 19:23 [gentoo-project] ComRel / disciplinary action reform proposal Michał Górny
2017-01-15 19:38 ` Raymond Jennings
2017-01-15 20:06 ` Rich Freeman
2017-01-15 20:02 ` Rich Freeman
2017-01-15 20:13 ` Kent Fredric
2017-01-15 23:05 ` M. J. Everitt
2017-01-16 17:54 ` Alec Warner
2017-01-15 21:59 ` Dale
2017-01-16 5:00 ` Dean Stephens
2017-01-15 22:55 ` M. J. Everitt
2017-01-16 0:25 ` Jorge Manuel B. S. Vicetto
2017-01-16 0:44 ` Raymond Jennings
2017-01-16 0:55 ` Rich Freeman
2017-01-16 11:16 ` Jeroen Roovers
2017-01-16 19:35 ` Jorge Manuel B. S. Vicetto
2017-01-17 17:38 ` Michał Górny
2017-01-16 4:56 ` Dean Stephens
2017-01-16 13:22 ` Paweł Hajdan, Jr.
2017-01-16 13:40 ` Kristian Fiskerstrand
2017-01-17 4:30 ` Dean Stephens
2017-01-17 4:29 ` Dean Stephens
2017-01-17 17:41 ` Michał Górny
2017-01-20 5:02 ` Dean Stephens
2017-01-16 20:57 ` William L. Thomson Jr.
2017-01-17 17:49 ` Michał Górny
2017-01-17 18:54 ` William L. Thomson Jr.
2017-01-17 19:03 ` Rich Freeman [this message]
2017-01-17 19:40 ` William L. Thomson Jr.
2017-01-17 20:20 ` Rich Freeman
2017-01-18 5:33 ` Raymond Jennings
2017-01-18 17:07 ` William L. Thomson Jr.
2017-01-17 14:38 ` Daniel Campbell
2017-01-17 15:26 ` Rich Freeman
2017-01-17 18:05 ` Michał Górny
2017-01-17 18:13 ` Kristian Fiskerstrand
2017-01-18 17:31 ` William L. Thomson Jr.
2017-01-18 18:25 ` Michał Górny
2017-01-18 18:31 ` William L. Thomson Jr.
2017-01-18 19:05 ` Rich Freeman
2017-01-18 19:13 ` William L. Thomson Jr.
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_mTspzJih+=o5B0bX4AeTRF1FGcqQ6xqL1ybNz76zxE0g@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