I’m supportive of using GitHub issues for a few reasons: It’s more inclusive to our users who can no longer create jira accounts. My account is more secure, requiring hardware tokens to log in. Unlike jira, it renders correctly on my phone.
-ck > On Nov 4, 2022, at 09:43, Matt Sicker <m...@musigma.org> wrote: > > I’m fairly neutral on the change. At least you can reply to GitHub Issue > emails and have them added to the conversation (like with PRs). We don’t > really use any fancy Jira features that aren’t also available in GitHub. > >> On Nov 4, 2022, at 9:06 AM, Volkan Yazıcı <vol...@yazi.ci> wrote: >> >> Given the last update from INFRA that new JIRA accounts will only be >> allowed through (PMC?) approval, I propose switching Log4j issue tracking >> to GitHub Issues. Do you have any objections? If not, I volunteer to create >> a ticket for this and implement it. >> >> What needs to be done for Log4j? >> - Update[1] docs, READMEs, Confluence, POM files, anywhere JIRA is mentioned >> - See if `changes.xml` et al. still functions >> >> [1] While updating, I will keep a reference to JIRA too, wherever necessary. >
