* [ISSUE] [RFC] enable discussions for void-packages
@ 2023-03-28 20:56 classabbyamp
2023-03-28 21:29 ` Duncaen
` (5 more replies)
0 siblings, 6 replies; 7+ messages in thread
From: classabbyamp @ 2023-03-28 20:56 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1072 bytes --]
New 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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [RFC] enable discussions for void-packages
2023-03-28 20:56 [ISSUE] [RFC] enable discussions for void-packages classabbyamp
@ 2023-03-28 21:29 ` Duncaen
2023-03-28 21:39 ` leahneukirchen
` (4 subsequent siblings)
5 siblings, 0 replies; 7+ messages in thread
From: Duncaen @ 2023-03-28 21:29 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 554 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/issues/43081#issuecomment-1487619662
Comment:
Having discussions for support or questions seems ok and we can move invalid "issues" there instead of just closing them as "not an issue".
I still don't like the idea of moving package requests somewhere else. The forum-like interface encourages users to comment and bump their requests to the top by having pointless discussions or gives the impression that requests with more upvotes would have priority.
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [RFC] enable discussions for void-packages
2023-03-28 20:56 [ISSUE] [RFC] enable discussions for void-packages classabbyamp
2023-03-28 21:29 ` Duncaen
@ 2023-03-28 21:39 ` leahneukirchen
2023-03-28 22:12 ` ahesford
` (3 subsequent siblings)
5 siblings, 0 replies; 7+ messages in thread
From: leahneukirchen @ 2023-03-28 21:39 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 192 bytes --]
New comment by leahneukirchen on void-packages repository
https://github.com/void-linux/void-packages/issues/43081#issuecomment-1487628835
Comment:
Also `Fixes #xxxx` wouldn't work I think.
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [RFC] enable discussions for void-packages
2023-03-28 20:56 [ISSUE] [RFC] enable discussions for void-packages 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
` (2 subsequent siblings)
5 siblings, 0 replies; 7+ messages in thread
From: ahesford @ 2023-03-28 22:12 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 767 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/43081#issuecomment-1487659958
Comment:
I prefer GH to Reddit for general support and would like to pin a message on r/voidlinux directing users to GH Discussions. Over time, if Reddit activity died down, I'd probably just stop checking it.
I don't have a strong opinion about moving new-package requests off the issue page, but it would be nice to reduce the issue clutter and highlight actual problems. People might try to game request discussions, but that certainly doesn't bind anybody to taking action. If we don't move new-package requests to discussions, we might get similar benefit from pruning such requests with stale-not after an extended period.
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [RFC] enable discussions for void-packages
2023-03-28 20:56 [ISSUE] [RFC] enable discussions for void-packages classabbyamp
` (2 preceding siblings ...)
2023-03-28 22:12 ` ahesford
@ 2023-03-28 22:26 ` classabbyamp
2023-06-27 2:08 ` github-actions
2023-06-28 5:18 ` [ISSUE] [CLOSED] " the-maldridge
5 siblings, 0 replies; 7+ messages in thread
From: classabbyamp @ 2023-03-28 22:26 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 321 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/issues/43081#issuecomment-1487682303
Comment:
> Also `Fixes #xxxx` wouldn't work I think.
as a stop-gap until github implements it, a workflow could be used to close discussions, assuming the api endpoints are there
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [RFC] enable discussions for void-packages
2023-03-28 20:56 [ISSUE] [RFC] enable discussions for void-packages classabbyamp
` (3 preceding siblings ...)
2023-03-28 22:26 ` classabbyamp
@ 2023-06-27 2:08 ` github-actions
2023-06-28 5:18 ` [ISSUE] [CLOSED] " the-maldridge
5 siblings, 0 replies; 7+ messages in thread
From: github-actions @ 2023-06-27 2:08 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 293 bytes --]
New comment by github-actions[bot] on void-packages repository
https://github.com/void-linux/void-packages/issues/43081#issuecomment-1608597599
Comment:
Issues become stale 90 days after last activity and are closed 14 days after that. If this issue is still relevant bump it or assign it.
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [ISSUE] [CLOSED] [RFC] enable discussions for void-packages
2023-03-28 20:56 [ISSUE] [RFC] enable discussions for void-packages classabbyamp
` (4 preceding siblings ...)
2023-06-27 2:08 ` github-actions
@ 2023-06-28 5:18 ` the-maldridge
5 siblings, 0 replies; 7+ messages in thread
From: the-maldridge @ 2023-06-28 5:18 UTC (permalink / raw)
To: ml
[-- 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
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2023-06-28 5:18 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-03-28 20:56 [ISSUE] [RFC] enable discussions for void-packages 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 ` [ISSUE] [CLOSED] " the-maldridge
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).