From: the-maldridge <the-maldridge@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] [RFC] enable discussions for void-packages
Date: Wed, 28 Jun 2023 07:18:48 +0200 [thread overview]
Message-ID: <20230628051848.yRgD2YF3h9X53z8NWF7p3J_r-ICU9uDeyoYkfbG1PFI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43081@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1075 bytes --]
Closed issue by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/issues/43081
Description:
### Pros
- Allows the issue tracker to only contain bug reports and RFCs
- Feature and package requests could be converted to discussions to avoid flooding the issue tracker, and kept in separate categories
- Q & A categories could be used as a general support forum for those who don't want to use reddit
- could also be enabled as ["organisation discussions"](https://github.blog/2022-04-12-whats-new-in-github-discussions-organization-discussions-polls-and-more/#introducing-organization-discussions) so it shows up at the org level
- if a support discussion or feature request rises to the level of a bug report or RFC, it can be converted into an issue
### Cons
- no automatic discussion closing via commits/PRs (`fixes #12345`)
- adds an additional support forum for maintainers to keep track of
@void-linux/pkg-committers
previous discussion (discussions can now be closed, so there is a difference from then): #36700
prev parent reply other threads:[~2023-06-28 5:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 20:56 [ISSUE] " classabbyamp
2023-03-28 21:29 ` Duncaen
2023-03-28 21:39 ` leahneukirchen
2023-03-28 22:12 ` ahesford
2023-03-28 22:26 ` classabbyamp
2023-06-27 2:08 ` github-actions
2023-06-28 5:18 ` the-maldridge [this message]
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=20230628051848.yRgD2YF3h9X53z8NWF7p3J_r-ICU9uDeyoYkfbG1PFI@z \
--to=the-maldridge@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).