Apologies, I responded directly to Volkan instead of the list ):
-d
-------- Forwarded Message --------
Subject: Re:
Date: Tue, 13 Feb 2024 12:00:05 +0200
From: Davyd McColl <dav...@gmail.com>
To: Volkan Yazıcı <vol...@yazi.ci>
I'd really like to chuck JIRA in a lake of fire and watch it burn slowly /2c
On a less crazy note: I'd really like all the things to be at GitHub -
it's easier as a dev or a user to get involved.
-d
On 1970/01/01 02:00, 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.
