Moving issues to discussions #2345
Closed
codingjoe
started this conversation in
Contributing
Replies: 1 comment 3 replies
-
|
I'm not able to to see a major difference. They are likely to sit around waiting for someone to give it some attention. Even closed issues can be revived if there's a reason. Splitting up where we do triaging may make sense if things were a flurry of activity, but it's not. If the underlying concern is, "I don't know how to best help!" I think that's valid. But changing our process probably isn't the answer. Communicating where to look for issues (things that are recently created with discussions, newcomer friendly label) in the docs seems like a more effective solution. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, y'all,
While starting to grind through the issues, I started to look into the oldest issues without updates. Many of which are feature proposals. Over a decade-old feature proposals…
I often move future feature ideas to the
Ideassection in discussions instead of maintaining an issue graveyard.I'd love to hear your thoughts, should you have any. Otherwise, I'd start moving some accompanied by a nice comment.
Cheers!
Joe
Beta Was this translation helpful? Give feedback.
All reactions