From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Better communication
Date: Sun, 03 Sep 2023 19:30:10 +0200 [thread overview]
Message-ID: <20230903173010.KUsIPRbA_-Hcf5J0IALdjtzXgKV_KBSE_TmArkTahJM@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: 1110 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/issues/45892#issuecomment-1704359041
Comment:
You are painting a negative picture of how bad maintainers have been. Your issue is that in two instances packages have been removed from the repository.
In one instance the packages were later added back because, there was not enough communication between maintainers and contributors and while most of them either agreed with the removal or abstained from commenting on this, some stepped up and took over maintenance.
For the minecraft launcher, I don't see any issue at all. The maintainers treated you right and did nothing wrong. They explained why the package was removed and suggested or agreed that an install message would have been good.
There is no problem at all and I don't see how you can take this interaction and now turn it into some big issue that helps you to show a pattern is issues.
I deleted my earlier response since it failed to address the whole picture. I don't think there is any issue or pattern that is not already addressed.
next prev parent reply other threads:[~2023-09-03 17:30 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 [this message]
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=20230903173010.KUsIPRbA_-Hcf5J0IALdjtzXgKV_KBSE_TmArkTahJM@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).