No more "Issues"

[antonmedv]

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:

1. People use them as a catch-all for bugs, features, and questions, which leads to extra work sorting through them.
2. The “open” or “closed” status can cause frustration. People sometimes feel slighted when an issue is closed, interpreting it as a negative response from maintainers.

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.

[hashimaziz1]

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.

[antonmedv]

Weren't you on another repo just a few weeks ago complaining about this behaviour for an issue you created

No.

You even copied that dev's announcement post word for word, do they know about that?

Yes, copied. In my own words. The repo I copied this idea was livewire. And to copy idea is okay. Livewire devs, I copied your idea.

I disagreed in that case and I disagree now

It is okay. You have a right to be disagree.

I've seen they have helped you fix many bugs in the software and improve Deployer massively over time.

Issues are the way of keeping track of bugs/features/discussions/questions. Lately the become unmanageable and duplicated by discussions.

I can't see any benefit to this move at all.

We will see how a new approach works and decide later on

[pniederlag]

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.

[pniederlag]

Maybe it's a good idea to either drop the issues tab completly or to add a single issue pointing to this discussion... currently I see 0 open issues on the issues tab.

[antonmedv]

I thought about hiding "Issues" tab completely. But this can lead to confusion on there to open an issue. Now people can still do to "Issues" tab, and click "New issue" button to be redirected to "Discussions". I think this is a good compromise for now.

[alexislefebvre]

What about the issues that were "open"?

Like this one:

• Docker-image for Deployer #3118

Do you plan to migrate the issues to discussions so that people can upvote them?

[antonmedv]

Yes. I added a tag (still open) to all remaining issues and have plans to go through all of them. Fix issues or convert to a discussion if needed.