git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kaue Doretto Grecchi <kauedg@gmail.com>
To: peff@peff.net
Cc: git@vger.kernel.org, kauedg@gmail.com
Subject: Re: git-for-windows supporting public shaming and repressing community's opinion
Date: Tue, 16 Jun 2020 20:09:28 -0300	[thread overview]
Message-ID: <CAMWmj-xA2f0rT=NZqkR8iE-o4k7=Y20mSev_D_rdmzUfOOeyKA@mail.gmail.com> (raw)

I agree about the "he did it first" point and that's not what I'm
bringing up here. The discussion is
drifting from the main statement: the git-for-windows maintainers were
biased and blocked (by *selectively* applying the CoC) people who
disagreed on politically motivated changes, to which the community has
clearly manifested against.

> I do notice you've also been blocked from the project.
A very, very disproportional action. Hiding my comment *when it was
made* would be enough. People are allowed to make mistakes and defend
themselves.

> AFAICT the hiding of comments and the blocking of people happened more or less at the same time (from the perspective of the commenters).
> Maintainers of projects aren't reading comments in real-time.
The repo's crew had plenty of time and opportunity to act on bad
behaviour and when they did, it was selective. If a comment goes
against the CoC, it doesn't go against it *after other comments* or
when the debate gets heated. I understand that the timing of the
events can't be clearly demonstrated from a plain-text message but I'm
very sure of what happened there.

> I'm open to the notion that a maintainer is abusing their power and silencing dissent under the guise of the CoC. But I don't really see evidence of that here.
Just consider that the user mlvzk wasn't blocked or banned from the
project. He did not even have his comment deleted, even it suggesting
some nazi-like actions (come on, icons to identify dangerous people?
What about a yellow star?). And his comment wasn't hidden until some
time after people were blocked. I'd be glad to get the list of users
who liked his comment but it's blocked.

Isn't it disproportional, considering that user A suggests an open
witch hunt and user B uses mild "bad language"?


> OK. Thank you for making us aware of your viewpoint. It sounds like there's no specific action you're asking to be taken, so I'll leave it at this response for now.
I think it was clear that the repo's maintainers, or at least one of
them, is willingly ignoring the community's manifestation using the
CoC as muzzle to enforce his/their political beliefs. This is what my
first message is about. There were 490 downvotes on the first issue's
message and 133 "pro" manifestations. The issue should be closed in
respect to the community.

> I'm not sure what you're asking here.
That the git-for-windows team (or member) should be reprehended for
not accepting the community's decision and opinion and being selective
on their bannings. Their (his) actions send a very nasty message to
the community, that, basically, we don't matter in the discussion. And
that it reflects on git's reputation.

             reply	other threads:[~2020-06-16 23:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-16 23:09 Kaue Doretto Grecchi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-06-16 20:52 git-for-windows supporting public shaming and repressing community's opinion Kaue Doretto Grecchi
2020-06-16 22:03 ` Jeff King
2020-06-16 19:28 Kaue Doretto Grecchi
2020-06-16 20:15 ` Elijah Newren
2020-06-16 21:44 ` Jeff King

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='CAMWmj-xA2f0rT=NZqkR8iE-o4k7=Y20mSev_D_rdmzUfOOeyKA@mail.gmail.com' \
    --to=kauedg@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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;
as well as URLs for NNTP newsgroup(s).