From: Yorizuka <Yorizuka@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Better communication
Date: Tue, 05 Sep 2023 02:49:28 +0200 [thread overview]
Message-ID: <20230905004928.R-6xGpRxTPrNNpIS_aPG4MEB45EX2rjfolE3U5xasps@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45892@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2218 bytes --]
New comment by Yorizuka on void-packages repository
https://github.com/void-linux/void-packages/issues/45892#issuecomment-1705802918
Comment:
To be transparent, this post https://github.com/void-linux/void-packages/issues/45892#issuecomment-1704742605 was written with anger, I was attributing malice to your PR and was "reading in between the lines", that was wrong of me.
> > Also the claim in the PR opening comment is false, not all the PRs referenced where dead or tiny unimportant projects.
>
> As the person who wrote the PR, what claim are you talking about, and where are they contained in the PR's text? Note that no edits were made to the PR
I will attempt to explain my thoughts at that moment.
I was viewing the entire PR from an adversarial prospective, I believed the PR never had attempted consensus and that the initial post was simply a cover story to remove stuff that was not liked.
To my eyes the inital post was specifically crafted to be vague and hard to counter. I believed the `This has been discussed multiple times on IRC, and it seems the general consensus was towards removal` was written to create more credibility without anything backing the statement. To anyone who was not in the IRC at that point, there is no way verify. Also this created the question of how many people does it take to count as a "consensus".
So discarding the IRC statement as unverifiable, there was no more text that could explain the justification for what was in my eyes a huge change.
Then next was the CONTRIBUTING.md change, The way it was worded made it look like a non reversible project wide change to kill all possible reverts. I interpreted the language as specifically crafted to shoot down all possible conversations, due to omitting words like "generally" signaling that no debate could be had.
Lastly this PR was huge touching all crypto, usually most PR I have looked at touch a few packages. So that read to me as a attempt to do this quickly before people would notice.
To be fair, you did call your branch `remove/cryptoshit` so honestly I still of you as an non neutral adversary & am skeptical of anything you say, but attributing pure malice is not a good approach.
next prev parent reply other threads:[~2023-09-05 0:49 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-03 5:23 [ISSUE] " Yorizuka
2023-09-03 5:43 ` classabbyamp
2023-09-03 6:00 ` Yorizuka
2023-09-03 6:00 ` Yorizuka
2023-09-03 6:29 ` Yorizuka
2023-09-03 11:11 ` Duncaen
2023-09-03 16:20 ` Yorizuka
2023-09-03 17:07 ` Duncaen
2023-09-03 17:07 ` Duncaen
2023-09-03 17:08 ` Duncaen
2023-09-03 17:18 ` Duncaen
2023-09-03 17:20 ` Duncaen
2023-09-03 17:20 ` Duncaen
2023-09-03 17:24 ` Duncaen
2023-09-03 17:30 ` Duncaen
2023-09-03 17:31 ` Duncaen
2023-09-03 18:54 ` Duncaen
2023-09-03 18:55 ` Duncaen
2023-09-03 20:18 ` Yorizuka
2023-09-03 20:38 ` Eloitor
2023-09-03 21:22 ` Yorizuka
2023-09-04 0:13 ` Duncaen
2023-09-04 0:14 ` Duncaen
2023-09-04 0:15 ` Duncaen
2023-09-04 0:16 ` Duncaen
2023-09-04 0:18 ` Duncaen
2023-09-04 7:20 ` Yorizuka
2023-09-04 7:21 ` Yorizuka
2023-09-04 7:22 ` Yorizuka
2023-09-04 7:27 ` Yorizuka
2023-09-04 7:35 ` Yorizuka
2023-09-04 7:37 ` Yorizuka
2023-09-04 9:54 ` Duncaen
2023-09-04 9:56 ` Duncaen
2023-09-04 10:01 ` Duncaen
2023-09-04 10:05 ` Yorizuka
2023-09-04 10:07 ` Yorizuka
2023-09-04 10:07 ` Yorizuka
2023-09-04 10:17 ` Duncaen
2023-09-04 10:24 ` Yorizuka
2023-09-04 11:10 ` Yorizuka
2023-09-04 11:12 ` Yorizuka
2023-09-04 11:17 ` Yorizuka
2023-09-04 11:25 ` Yorizuka
2023-09-04 11:39 ` Yorizuka
2023-09-04 23:35 ` 0x5c
2023-09-05 0:49 ` Yorizuka [this message]
2023-09-05 0:53 ` Yorizuka
2023-09-05 1:09 ` Yorizuka
2023-09-16 15:52 ` [ISSUE] [CLOSED] " ahesford
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=20230905004928.R-6xGpRxTPrNNpIS_aPG4MEB45EX2rjfolE3U5xasps@z \
--to=yorizuka@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).