Github messages for voidlinux
 help / color / mirror / Atom feed
From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Better communication
Date: Sun, 03 Sep 2023 19:20:34 +0200	[thread overview]
Message-ID: <20230903172034.jTjSNn7IB_pf4e-Sq_U2EnH3JnOygXGn9zyWxTrIk-4@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: 5202 bytes --]

New comment by Duncaen on void-packages repository

https://github.com/void-linux/void-packages/issues/45892#issuecomment-1704354724

Comment:
Users don't even read INTSALL.msg's, adding a bunch of PRs and Issues doesn't provide any benefit.

We don't ask users or have polls to make decisions, maintainers and contributors make decisions by taking time and implementing changes. This generally works well because the maintainers and contributors generally try to maintain compatibility and avoid causing trouble with changes. This is not debian and its bureaucracy, which comes with up and downsides.

The cryptocurrency removal was not well communicated with some contributors who later stepped up and took over maintenance and could have been avoided by pinging/tagging all contributors in the PR.

In the end because of the picture you are trying to paint of negative experiences and what not, I don't really care. I would just close this Issues to be honest. You didn't like the decision of dropping the minecraft launcher from the repository and replacing it with an actively maintained fork, that's fine. You thought your PR was closed with no comment, but it was merged and there was even a comment later that it was reverted. 

> I have lost all trust in the current maintainers of this project. I still like this distribution and really wish I could continue using it without worrying. I want things to improve. The usual disgruntled response is "Yeah, well, I'm gonna go build my own distribution. With blackjack and hookers!", but I don't have the desire, skill or time to maintain a gnu+linux distribution or a repo. Instead I am making my voice known and maybe something positive can happen.

Its gnu/linux.

> I believe the main issue is one of communication. I think solving communication between users and maintainers would do void a lot of good. I would like to get an opinion from the maintainers on this.

The issue tracker is open and we don't exclude anyone from contributing.

> 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.

Wow that sounds bad, what did they do to you?



> 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)

As mentioned in an earlier reply, it was merged and two days later the contributor who merged it commented about reverting it since it caused issues. There is nothing rude about it. You are making this up because it fits your narrative.

>  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, for a small amount of time thought my 7 year old world was lost, that was stressful.

1. You should have backups.
2. xbps does not delete user data.
3. There was internal drama with the launcher and there was the possibility of malware.
4. The fork is evidently now more actively maintained.

>  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 give you that this was miscommunicated between contributors, more people should have been pinged/tagged.

> 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 17:20 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 [this message]
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
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=20230903172034.jTjSNn7IB_pf4e-Sq_U2EnH3JnOygXGn9zyWxTrIk-4@z \
    --to=duncaen@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).