Re: [Log4j] GitHub Discussions

+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ı wrote: > > Piotr shared a very good observation (in a private Slack post > ) that > users ask questions in

Re: [Log4j] GitHub Discussions

On Thu, 24 Aug 2023 at 09:27, Volkan Yazıcı wrote: > *"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

Re: [Log4j] GitHub Discussions

+1 BUT we should document on our site and on GH that per Apache requirements, any decisions must be documented on the mailing list; I don't know if that includes the decision process. I don't know that we should or shouldn't get one email per discussion item echoed to a mailing list. Gary On

Re: [Log4j] GitHub Discussions

+1 Ralph > On Aug 24, 2023, at 4:01 AM, Christian Grobmeier wrote: > > +1 > > >> On Thu, Aug 24, 2023, at 09:26, Volkan Yazıcı wrote: >> Piotr shared a very good observation (in a private Slack post >> ) that >> users ask

Re: [Log4j] GitHub Discussions

+1 On Thu, Aug 24, 2023, at 09:26, Volkan Yazıcı wrote: > Piotr shared a very good observation (in a private Slack post > ) that > users ask questions in GitHub Issues, we point them to the mailing list, > and they disappear. See

Re: Remove Noise: using commits@?

I am sorry for this message, I double checked after your comments and I think I have my client misconfigured. I will correct it On Thu, Aug 24, 2023, at 08:54, Ralph Goers wrote: > I took care of most of the noise ages ago. I created folders in my > email client for GitHub, Jira, general

[Log4j] GitHub Discussions

Piotr shared a very good observation (in a private Slack post ) that users ask questions in GitHub Issues, we point them to the mailing list, and they disappear. See this ticket

Re: Shared GitHub actions

Piotr and I are very well aware of reusable GitHub workflows . As a matter of fact, that is what I am currently working on: moving all our shared `pom.xml` (the distribution ZIP creation, signing, changelog management, etc.) and

Re: Remove Noise: using commits@?

I took care of most of the noise ages ago. I created folders in my email client for GitHub, Jira, general notifications, and SVN (now Git). I then set up filters based on the properties in those emails . That said, my GitHub folder currently has 1327 unread emails, Jira 567, notifications 233