[logging-log4j-kotlin] 03/11: Update contributing info to reference github issues

[ma...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

mattsicker pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/logging-log4j-kotlin.git

commit 51bb3a44670ed74fd7efe22350fe8a20ea5069eb
Author: Matt Sicker <ma...@apache.org>
AuthorDate: Sun Jan 29 18:26:42 2023 -0600

    Update contributing info to reference github issues
---
 src/site/asciidoc/contributing.adoc | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/src/site/asciidoc/contributing.adoc b/src/site/asciidoc/contributing.adoc
index 4730d54..0ea6998 100644
--- a/src/site/asciidoc/contributing.adoc
+++ b/src/site/asciidoc/contributing.adoc
@@ -22,7 +22,6 @@ Before you dig right into the code there are a few guidelines that we need contr
 
 === Getting Started
 
-* Make sure you have a https://issues.apache.org/jira/[Jira account].
 * Make sure you have a https://github.com/signup/free[GitHub account].
 * If you're planning to implement a new feature it makes sense to discuss your changes on the https://logging.apache.org/log4j/2.x/mail-lists.html[dev list] first.
   This way you can make sure you're not wasting your time on something that isn't considered to be in Apache Log4j's scope.
@@ -47,19 +46,18 @@ Before you dig right into the code there are a few guidelines that we need contr
 
 === Making Trivial Changes
 
-For changes of a trivial nature to comments and documentation, it is not always necessary to create a new ticket in JIRA.
+For changes of a trivial nature to comments and documentation, it is not always necessary to create a new ticket in GitHub Issues.
 In this case, it is appropriate to start the first line of a commit with '(doc)' instead of a ticket number.
 
 === Submitting Changes
 
 * Sign the https://www.apache.org/licenses/#clas[Contributor License Agreement] if you haven't already.
 * Push your changes to a topic branch in your fork of the repository.
-* Submit a pull request to the repository in the apache organization.
-* Update your Jira ticket and include a link to the pull request in the ticket.
+* Submit a pull request to the repository in the apache organization and reference the GitHub Issue id.
 
 === Additional Resources
 
-* https://issues.apache.org/jira/browse/LOG4J2[Apache Log4j 2 Jira project page]
+* https://github.com/apache/logging-log4j-kotlin/issues[Apache Log4j Kotlin API GitHub Issues]
 * https://www.apache.org/licenses/#clas[Contributor License Agreement]
 * https://help.github.com/[General GitHub documentation]
 * https://help.github.com/send-pull-requests/[GitHub pull request documentation]