+1

We can use it for user forums while still maintaining dev@ for development.

> On Aug 24, 2023, at 2:26 AM, Volkan Yazıcı <vol...@yazi.ci> wrote:
> 
> Piotr shared a very good observation (in a private Slack post
> <https://the-asf.slack.com/archives/C4TQW0M5L/p1692821047719209>) that
> users ask questions in GitHub Issues, we point them to the mailing list,
> and they disappear. See this ticket
> <https://github.com/apache/logging-log4j2/issues/1722> for an example.
> Consequently, Matt proposed using GitHub Discussions. Robert added Pulser
> already has it enabled <https://github.com/apache/pulsar/discussions>. I
> think many users are more keen on forums, GitHub, StackOverflow, etc. We
> should position ourselves where our users expect us to be. In that
> regard, *GitHub
> Discussions sounds like a great idea and I propose experimenting with it*:
> 
>   - Enable GitHub Actions
>   - Update our support page accordingly
>   - Update README
> 
> One would think this should be a matter of a `.asf.yaml` one-liner, but it
> is not
> <https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INFRA&title=Git+-+.asf.yaml+features#Git.asf.yamlfeatures-GitHubDiscussions>
> :
> 
> *"GitHub Discussions is currently a beta feature and does not have an API
> endpoint. Until this is addressed, please open an Infra Jira ticket with a
> link to a consensus discussion thread for your project."*
> 
> 
> Hence, *I need your approval in the form of a reply to this post*.

Reply via email to