Replies: 4 comments 5 replies
-
Weren't you on another repo just a few weeks ago complaining about this behaviour for an issue you created, and now you're doing it yourself on your own repo? You even copied that dev's announcement post word for word, do they know about that? I disagreed in that case and I disagree now - issues have emojis so they don't need upvotes, and the only "pressure" is self-imposed - the open issue count is motivation to fix bugs, as I've seen they have helped you fix many bugs in the software and improve Deployer massively over time. I can't see any benefit to this move at all. |
Beta Was this translation helpful? Give feedback.
-
I can understand your motivation and reasoning. There is always a decision wether someone elses problem is solved, irrelevant or worth fixing/implementing which is a bunch of work and responsibility put on the maintainer. Also I have already seen a bunch of knowledge beeing hidden in closed bugs und bug-reports that are just mere support-requests So, happy to see you take a different approach, looking forward to see how it turns out in the long run. |
Beta Was this translation helpful? Give feedback.
-
What about the issues that were "open"? Like this one: Do you plan to migrate the issues to discussions so that people can upvote them? |
Beta Was this translation helpful? Give feedback.
-
If it's issues or discussion, is not a big deal to me as long as things get's fixed, if it's a bug, or there is a chance for new features I have had open questions regarding permissions for many month and no responses /solution. I have even offered @antonmedv to pay him to help me with one issue, but that did not work Have a look at the open PR's some is from 2023, so people are willing to help, but as PR's are not merged people looses interest in helping. The request about Ubuntu 22.04 has been there for more than one year and still no ETA I for one would love to help, but I have not the needed skill to do it, so for now I'sponsoring' and let's see how that helps the project and me |
Beta Was this translation helpful? Give feedback.
-
Hey Deployer folks!
I’ve decided to drop the concept of “Issues” from this repo because I believe it’s flawed, and GitHub’s “Discussions” feature handles things better.
Here are my two main problems with issues:
Switching to dedicated “Features” and “Bugs” groups in Discussions will improve things. With no “open issues” counter on the repo’s main page, there’s less pressure to close things too soon.
Plus, both I and the community can prioritize issues better now because they can be upvoted—a great feature missing from Issues (which led to those “+1” comments).
Lastly, Discussions will focus non-contribution activity in one place, meaning more eyes on questions and ideas.
Beta Was this translation helpful? Give feedback.
All reactions