From: Yorizuka <Yorizuka@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Better communication
Date: Sun, 03 Sep 2023 23:22:50 +0200 [thread overview]
Message-ID: <20230903212250.E0YY9i0Fh9hCdXpKr5wfPSrssqtO1Y5C5FgZnGFMEUo@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: 2153 bytes --]
New comment by Yorizuka on void-packages repository
https://github.com/void-linux/void-packages/issues/45892#issuecomment-1704407346
Comment:
With the crypto PR, I am upset that out of the blue void is taking an anti crypto stance & then doing a wide purging of packages it's users depend on, regardless of how well they where maintained or if there was any willing maintainers.
There was also zero links to any IRC log, or any summery of the WHAT & WHY for the ""consensus"". The way this was handled feels like there is an alternative non technical motive that is trying to be hidden.
* The crypto software is opensource software.
* The crypto software was maintained or had willing maintainers if needed.
* The crypto software has no malicious anti features a user might not want.
* The crypto software is not a superficial tweak or shell script.
* The crypto software was allowed on void for a long time, until now.
I do not understand why it would be removed.
The PR adds new language to the CONTRIBUTING.md file, clearly saying crypto is not welcome. Unlike the segment about browser forks, there is no maybe, it also includes no explanation as to why, and is worded in a more strict way. Why will a browser fork be **generally** not accepted and the crypto flat out "are not accepted"?
If there is no intent on being neutral, then please make your political or social stance explicit and clear, if crypto people are not welcome in the void ecosystem then please just tell us that.
If crypto in it self is not a problem and its a problem with maintaining packages, then lets work on that, I may be interested in helping with packaging if crypto packaging needs help, but I don't want to bother if that is not welcome.
the bit on crypto: `Packages related to cryptocurrencies (wallets, miners, nodes, etc) are not accepted.`
the bit on browsers: `Browser forks, including those based on Chromium and Firefox, are generally not accepted.
Such forks require heavy patching, maintenance and hours of build time.`
https://github.com/0x5c/void-packages/blob/a5af93198436f779e3f9eda4666f06bd1bb75ac8/CONTRIBUTING.md?plain=1#L23
next prev parent reply other threads:[~2023-09-03 21:22 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 [this message]
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
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=20230903212250.E0YY9i0Fh9hCdXpKr5wfPSrssqtO1Y5C5FgZnGFMEUo@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).