FYI While it is a different community, I have received negative feedback in Commons against the trend to spread information all over the place, and we don't use GitHub.
The TLDR is that in the past it was easier to find information because you only had the mailing list and later Jira. Now you have multiple mailing lists, Jira, emails from GitHub, plus discussions in GitHub PRs, plus Slack. Adding to the list is GitHub issues... I'm not sure there is anything we can do aside from making sure that GH issue changes get saved in emails to a mailing list which can searched mixed with the rest of our stuff. I won't mention Discord ;-) Gary On Fri, Aug 9, 2024, 4:48 AM Piotr P. Karwasz <piotr.karw...@gmail.com> wrote: > Hi all, > > As specified in the `.asf.yaml` documentation, I am opening this > thread to test the consensus on enabling Github discussions for > `logging-log4j-kotlin` and `logging-log4j-scala`. > > Do you have anything against enabling this feature? > > Piotr > > BTW: an INFRA ticket is already open[2]. > > [1] > https://github.com/apache/infrastructure-asfyaml?tab=readme-ov-file#github-discussions > [2] https://issues.apache.org/jira/browse/INFRA-26013 >
