Github messages for voidlinux
 help / color / mirror / Atom feed
From: Yorizuka <Yorizuka@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: srcpkgs/*: remove all cryptocurrency/blockchain packages
Date: Sun, 03 Sep 2023 06:59:36 +0200	[thread overview]
Message-ID: <20230903045936.lnek8jOryviojiisrrHO1RuzIp9kbWydJ3xtD7nVEn0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44422@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 2671 bytes --]

New comment by Yorizuka on void-packages repository

https://github.com/void-linux/void-packages/pull/44422#issuecomment-1704007166

Comment:
Every encounter I have had with the maintainers has been a negative one for the last few years. Look I understand opensource work pays nothing and is often a thankless job. But I have interacted with maintainers for other project and it never was this bad.
Consistently moves are made with zero attempt to communicate them before they are done. This is not a one-off, this is a pattern, I will list the last 3 times that upsetting actions have been done before communicating them from my memory.

1. I have attempted to a good user and to give back, on my first contribution I had my Pull request closed with no explanation as to why. (An explanation did come, but it was a day later, after I gave up.) https://web.archive.org/web/20230903041209/https://github.com/void-linux/void-packages/pull/37370 While I still feel it was a bit rude, I forgive this one. (please do not harass any of the people involved)
2. Another upsetting action the maintainers have done is hijacking an existing packages and shipping a different program under the same name with zero communication about it before they did so. https://web.archive.org/web/20230903034123/https://github.com/void-linux/void-packages/pull/40044 This one alone under other a sightly different context would of had mobs of angry people & is still in principle an unacceptable behavior. The new launcher was not 1 to 1 compatible & gave me quite the scare, I a small amount of time thought my 7 year old world was lost, that was stressful.
3. This: Most users do not interact with the maintainers of the software they use. There is a silent majority that is not hanging out in the IRC. Given the current popular stance on Crypto, I'm guessing this has more then just technical motivations, I understand not adding new coins, but looking at the Monero wallet, this clearly is a quick and dirty hit job, The Monero wallet was removed, but the debug and development files are still showing up in the search. https://web.archive.org/web/20230903044828/https://voidlinux.org/packages/?arch=x86_64&q=monero

I do not appreciate the maintainers making life style choices for me, Whats next? Are you going to remove TOR, that allows you to access and do bad things. Maybe void should remove everything with encryption, it's what bad people use to hide things.
I use to run xbps-install -Suy weekly, keeping my system up to date, Now hesitate to update, every time I do so there is a chance something annoying will be done by the maintainers and that I should go double check.

  parent reply	other threads:[~2023-09-03  4:59 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-14  5:59 [PR PATCH] " 0x5c
2023-06-15 19:47 ` paper42
2023-06-16  8:39 ` [PR PATCH] [Updated] " 0x5c
2023-06-16 19:26 ` ar-jan
2023-06-19  1:06 ` [PR PATCH] [Updated] " 0x5c
2023-06-26 20:07 ` [PR PATCH] [Merged]: " leahneukirchen
2023-06-28 14:56 ` SpecialBomb
2023-06-28 17:28 ` lemmi
2023-06-30 11:41 ` kevcrumb
2023-07-16  9:59 ` drizzt
2023-07-30  8:06 ` uberscientist
2023-07-30 17:37 ` 0x5c
2023-07-31 16:39 ` maciozo
2023-07-31 16:42 ` maciozo
2023-07-31 19:49 ` lemmi
2023-07-31 20:00 ` 0x5c
2023-07-31 20:07 ` maciozo
2023-07-31 20:09 ` maciozo
2023-07-31 20:12 ` ar-jan
2023-07-31 20:21 ` 0x5c
2023-07-31 20:36 ` maciozo
2023-07-31 20:37 ` lemmi
2023-09-03  4:59 ` Yorizuka [this message]
2023-09-03  5:28 ` Yorizuka
2023-09-03 22:01 ` Yorizuka

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=20230903045936.lnek8jOryviojiisrrHO1RuzIp9kbWydJ3xtD7nVEn0@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).