Repository navigation
Introducing GitHub Discussions #15515
Replies: 1 comment
|
Honestly the problem with this (that I pointed out when I closed a "discussion" for PS3), is that having "upvotes" having any influence on what gets fixed is the wrong way to go about things.
That's precisely what is going to happen here. The "It doesn't happen to me" crowd is going to mean actual issues get drowned out by popularity instead of actual fixes.
I had a PS3 issue that's replicable moved to discussions where it can safely be ignored and drowned out by the voting system. Overall from a user perspective, this is a horrible way to go about things. It makes it seem like my issue isn't important enough and therefor will not actually be looked into or fixed. It's putting a bandaid over a gushing wound. Not a fix, and it's going to drive your users away. |
Uh oh!
There was an error while loading. Please reload this page.
We are opening GitHub Discussions! This announcement summarizes why we decided to enable the feature, what we hope to achieve with it and what it means for the users contributing to the PrusaSlicer project.
Motivation
Sadly, the current state of PrusaSlicer issue tracker is sub-optimal. In one big pile of issues, there are serious reproducible bugs, feature requests, questions, suggestions and everything in between and more. This makes it very hard for us to track bugs that need our utmost attention as opposed to laid-back suggestions and feature requests that may have to be discussed and analysed before an action is taken.
GitHub issue tracker is very well suited to tracking bugs, but it lacks serious categorization (labels have not worked out for us) and upvote capabilities. Often, when it comes to suggestions and feature requests we are forced to judge the community sentiment based on the number of emojis and comments, which can be very misleading and is of no use to anyone.
We are hoping to address these problems by introducing GitHub Discussions and providing clear guidelines as to how to engage with our project.
Goals
Our hope is that by introducing GitHub Discussions, we will be able to keep the issue tracker under control while not discarding any community input we might receive. We will be actively moving anything that is not a reproducible bug to the discussions.
What used to happen is that some issues in the issue tracker remained without an answer. We would like to prevent that in the issue tracker and stay on top of the incoming issues there. Furthermore, we do not want to let any of the bugs slip our attention by being drowned in a sea of non-bug-related issues.
By moving everything else to discussion, we hope to be able to better prioritize most requested features, allow users to ask questions and ask for help. We cannot guarantee to provide an official statement to every single discussion, but we hope that the upvoting system and our awesome community members can foster an environment where you can provide feedback without feeling left out.
Execution
In the issue tracker, anything that is not a reproducible bug will be moved to discussions. There will be a clear policy as to what constitutes a reproducible bug.
There are 4 main categories in the discussions:
Announcements: These are official statements from us where we can clearly communicate with you.
Community help: If you need help with something, try asking here. Either we or someone from the community might be able to solve your issue.
Feature requests: Here you can suggest new PrusaSlicer features and discuss/upvote other people's suggestions.
General: Anything that does not fit the previous categories will go here.
We will start migrating to this model starting now.
Final thoughts
By introducing GitHub Discussions we hope to make engaging with our project more pleasant for you, while providing the added benefit of more clarity and organization to us. It might take some time for our plan to fully materialize, so please bear with us during this migration period!
All reactions