I've been answering some tickets the last few days and came across some issues that would be better suited for GitHub Discussions. It sometimes feels wrong that someone has a question, gets this answered, and then the ticket just vanishes inside the closed issue section, never to be seen again. GitHub discussions are more long-lived than issues, thus enabling better visibility for our users.

There will still be topics that need to be addressed in issues, such as bugs, but most of them belong to a category in discussion (in my opinion). For example, tickets such as reactphp/event-loop#257 could exist under a "show and tell" section. If necessary I can come up with a short plan on which types of issues should be discussions and which not.

We also have to decide whether to open Discussions in all ReactPHP repositories or just inside this (meta) repository. If we only activate them in this repository we'd have everything (questions/feature requests) in one place, on the other hand, this can get overloaded with tickets really fast. If we'd activate them in every ReactPHP repository it could be sometimes hard to tell, if a ticket belongs in the socket or http or event-loop, etc. discussion. But there's always the choice to transfer discussions between different repositories.

Those are just a few points I want to start this discussion with. We've done the same thing in clue/framework-x a while back.

What do you think about this?