Hi Volkan, I would prefer option 1.3, because most of the users will look for discussions in the most relevant Github repo (for them). I'm not a fan of Discourse (another app to install and no integration with Github).
Let's try and find out whether it works for us. We need to decide, whether we include voting on topics and releases should be done via Discussions (and get it approved by the ASF in case we want that). What about the private@ and security@ lists? Is it possible to do restricted discssions? Regards. Jan Friday, October 11, 2024, 9:03:31 AM, you wrote: > That is something we can decide together: > 1. Have project-specific discussion repositories (i.e., Log4j users will > use `logging-log4j2`, LogNet users will use `logging-log4net`, and so on) > 2. Have a shared discussion repository (e.g., we can create > `logging-discuss` repository and create `General`, `Log4j`, `Log4Net`, etc. > sections there) > 3. Have project-specific discussion repositories (`logging-log4j2`, > `logging-log4net`, etc.) and also a shared one (i.e., `logging-discuss` > with only `General` section) > My point is, we can configure GitHub Discussions to suit our needs. But, > are we willing to take that step?
