Keep in mind that decisions for the project still must be recorded on the mailing list. This might be a silly reminder since the issue is the same with Jira. Let's just be mindful of this information tracking as we've moved more of our infrastructure to GitHub. Don't get me wrong, I love working with GitHub, I just want to make sure that we play by our Apache rules.
Gary On Wed, Feb 14, 2024, 8:47 AM Robert Middleton <rmiddle...@apache.org> wrote: > I have no strong feelings either way. Turning on github discussions is a > good idea in my mind. > > +0 > > -Robert Middleton > > On Tue, Feb 13, 2024 at 12:45 PM Jan Friedrich <freeand...@gmx.net.invalid > > > wrote: > > > +1 from me > > > > Jan > > > > XA> +1. > > XA> ________________________________ > > XA> From: Matt Sicker <m...@musigma.org> > > XA> Sent: Wednesday, February 14, 2024 1:22:48 AM > > XA> To: Apache Logging Developers List <dev@logging.apache.org> > > XA> Subject: Re: Migrate *all* Issue Tracking and Discussions to GitHub > > > > XA> I think it’s a good idea, especially since Jira registrations are > > closed. > > > > >> On Feb 13, 2024, at 02:20, Volkan Yazıcı <vol...@yazi.ci> wrote: > > >> > > >> Log4j has deprecated JIRA in favor of GitHub Issues and enabled GitHub > > >> Discussions as an alternative (not replacement!) to mailing lists. So > > far > > >> it has been a great success[1]. I suggest doing the same for Log4cxx > and > > >> Log4net too. Thoughts? Objections? > > >> > > >> Note that I am not talking about only enabling these features. But to > > >> actively promote them on the website too. Check out the Log4j support > > page > > >> <https://logging.apache.org/log4j/2.x/support.html> for an example. > > >> > > >> [1] Code was already on GitHub. Now we can refer to PRs, issues, > > commits, > > >> code blocks, etc. while having conversations on any GitHub text > input. I > > >> find this quite convenient. IMO, as a result of this convenience, I > see > > way > > >> more maintainer engagement in PRs and issues. Next to that, GitHub > > >> Discussions clearly enabled more user interactions. It works around > the > > >> mailing list subscription barrier. > > > > >
