From: Daniel Robbins <drobbins@funtoo.org>
To: gentoo-nfp <gentoo-nfp@lists.gentoo.org>
Subject: Re: [gentoo-project] [gentoo-nfp] Foundation meeting agenda for April 2018 - update1
Date: Sat, 14 Apr 2018 23:09:00 -0600 [thread overview]
Message-ID: <CAPDOV4-fLR3D70ZDricxQYALwVUyhDYXfiCdDfjj4oErjMRsNA@mail.gmail.com> (raw)
In-Reply-To: <87tvsdi0bn.fsf@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 907 bytes --]
On Sat, Apr 14, 2018 at 10:02 PM, Matthias Maier <tamiko@gentoo.org> wrote:
> Dear Daniel,
>
> OK. Full stop right here.
What I would like to achieve is quite simple. I would like ComRel to be
consistent in their meting of discipline on the lists, and in the project
in general. I care about Gentoo developers, and don't care very much for
blatant hypocrisy. Nor do, I think, quite a few Gentoo developers who have
suffered because of this lack of consistency.
You don't owe me a justification. You owe the entire project and its users
an explanation for why you apply the CoC inconsistently. What I would
expect from ComRel is some kind of commitment to the community to enforce
standards fairly rather than selectively.
I think to people on the outside looking in, the lack of consistency and
playing of favorites is blatant and offensive.
I hope I have answered your questions.
Sincerely,
Daniel
[-- Attachment #2: Type: text/html, Size: 1367 bytes --]
next prev parent reply other threads:[~2018-04-15 5:09 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-10 20:51 [gentoo-nfp] Foundation meeting agenda for April 2018 - update1 Matthew Thode
2018-04-10 21:56 ` Andreas K. Huettel
2018-04-10 22:23 ` Matthew Thode
2018-04-10 22:27 ` Alec Warner
2018-04-11 0:34 ` Matthew Thode
2018-04-14 21:27 ` [gentoo-project] " Rich Freeman
2018-04-14 21:39 ` Matthew Thode
2018-04-14 21:51 ` Michał Górny
2018-04-14 22:12 ` Matthew Thode
2018-04-14 23:07 ` Daniel Robbins
2018-04-15 0:46 ` Luca Barbato
2018-04-15 1:42 ` Daniel Robbins
2018-04-15 2:52 ` Daniel Robbins
2018-04-15 4:02 ` Matthias Maier
2018-04-15 5:09 ` Daniel Robbins [this message]
2018-04-15 8:48 ` Luca Barbato
2018-04-15 9:13 ` Luca Barbato
2018-04-15 16:50 ` Daniel Robbins
2018-04-15 17:31 ` M. J. Everitt
2018-04-15 17:50 ` Daniel Robbins
[not found] ` <CAEdQ38E1SGhrzOmbN80HnKFRtsWj0HcVncFtdDoOuzyAKYXhBA@mail.gmail.com>
2018-04-15 18:01 ` M. J. Everitt
2018-04-15 23:09 ` Luca Barbato
2018-04-16 16:42 ` Daniel Robbins
2018-04-16 17:05 ` Daniel Robbins
2018-04-16 18:00 ` Rich Freeman
2018-04-16 18:06 ` Daniel Robbins
2018-04-16 18:09 ` Daniel Robbins
2018-04-16 18:35 ` Raymond Jennings
2018-04-16 18:45 ` Matthew Thode
2018-04-16 19:06 ` Daniel Robbins
2018-04-16 19:13 ` Matthew Thode
2018-04-16 19:39 ` Daniel Robbins
2018-04-16 21:25 ` Rich Freeman
2018-04-16 21:32 ` Matthew Thode
2018-04-17 0:01 ` Daniel Robbins
2018-04-17 0:10 ` Daniel Robbins
2018-04-17 5:28 ` Ulrich Mueller
2018-04-17 8:34 ` Raymond Jennings
2018-04-15 14:28 ` Jorge Manuel B. S. Vicetto
2018-04-15 14:29 ` Marta
2018-04-15 14:31 ` Francisco Blas Izquierdo Riera (klondike)
2018-04-15 17:29 ` M. J. Everitt
2018-04-15 18:48 ` Andreas K. Huettel
2018-04-15 18:57 ` M. J. Everitt
[not found] ` <CAAD4mYgDHAgw+jrb_pUas-d-o0ozZqo_Nj0QbexA1Mu-vqK_oA@mail.gmail.com>
2018-04-15 4:10 ` Raymond Jennings
2018-04-15 11:09 ` Michał Górny
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-fLR3D70ZDricxQYALwVUyhDYXfiCdDfjj4oErjMRsNA@mail.gmail.com \
--to=drobbins@funtoo.org \
--cc=gentoo-nfp@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