This is an automated email from the ASF dual-hosted git repository.
fpapon pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/shiro-site.git
The following commit(s) were added to refs/heads/main by this push:
new 47358c4a3 [documentation] Move from Jira to GitHub issue
new 1482af680 Merge pull request #182 from fpapon/jira2github
47358c4a3 is described below
commit 47358c4a32ca0c50927004388f09c0c91cabb0f0
Author: francois papon <[email protected]>
AuthorDate: Tue Jun 27 11:48:39 2023 +0200
[documentation] Move from Jira to GitHub issue
---
src/site/content/community.adoc | 2 +-
src/site/content/how-to-contribute.adoc | 14 +++++++-------
2 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/src/site/content/community.adoc b/src/site/content/community.adoc
index 11edd2b3c..ed9cb319a 100644
--- a/src/site/content/community.adoc
+++ b/src/site/content/community.adoc
@@ -29,6 +29,6 @@ At the Shiro project we make it easy for anyone to join our
great community and
* *link:developer-resources.html[Developer Resources]* - Helpful information
for anyone providing project help as a committer or contributor
-*
*https://issues.apache.org/jira/issues/?jql=project%20%3D%20SHIRO%20AND%20status%20%3D%20Open%20ORDER%20BY%20priority%20DESC[Issue
Tracker]* - Once you're ready to contribute, this is a good place to see what
needs to get done
+* *https://github.com/apache/shiro/issues[Issue Tracker]* - Once you're ready
to contribute, this is a good place to see what needs to get done
* *https://www.apache.org/foundation/sponsorship.html[Donate to ASF]* - Shiro
is a project under the Apache Software Foundation, a non-profit that relies on
donations and community support
diff --git a/src/site/content/how-to-contribute.adoc
b/src/site/content/how-to-contribute.adoc
index 9767b5bcf..dac8b102a 100644
--- a/src/site/content/how-to-contribute.adoc
+++ b/src/site/content/how-to-contribute.adoc
@@ -27,7 +27,7 @@ Or you can participate with resource donations:
* software
* general hardware/money
https://www.apache.org/foundation/thanks.html[donations] via the
https://www.apache.org[Apache Software Foundation]
-You can get your local working copy of the link:download.html[latest and
greatest code] by following the directions in link:download.html[Download]
page. Review the To Do list in the
https://issues.apache.org/jira/browse/SHIRO[issue tracker] and then choose a
task that interests you.
+You can get your local working copy of the link:download.html[latest and
greatest code] by following the directions in link:download.html[Download]
page. Review the To Do list in the https://github.com/apache/shiro/issues[issue
tracker] and then choose a task that interests you.
Perhaps you have noticed something that needs patching or have a new feature
to contribute. Make the changes, do the testing, generate a patch, and discuss
on the https://shiro.apache.org/mailing-lists.html[dev mailing list]. The
process is easy and explained below. Subscribe to the mailing list!
@@ -51,9 +51,9 @@ You can be a huge help by providing extra assistance in any
of the following are
== Procedure for Reporting Bugs and Issues and Enhancement Suggestions
-If you think that you have found a bug, or you have a suggestion for
improvement, then please discuss it on one of the
https://shiro.apache.org/mailing-lists.html[mailing lists]. However, please
check our https://issues.apache.org/jira/browse/SHIRO[issue tracker] first as
it may be already reported.
+If you think that you have found a bug, or you have a suggestion for
improvement, then please discuss it on one of the
https://shiro.apache.org/mailing-lists.html[mailing lists]. However, please
check our https://github.com/apache/shiro/issues[issue tracker] first as it may
be already reported.
-The https://issues.apache.org/jira/browse/SHIRO[Apache Shiro Issue Tracker]
collates our known issues. Obviously not every issue is listed there. Some
issues have been discussed on the mailing list but do not yet have an issue
recorded.
+The https://github.com/apache/shiro/issues[Apache Shiro Issue Tracker]
collates our known issues. Obviously not every issue is listed there. Some
issues have been discussed on the mailing list but do not yet have an issue
recorded.
The Roadmap is the best way to get an overview. The Unscheduled list also
needs regular review, and committers will schedule some of those for the next
release.
@@ -71,15 +71,15 @@ Most issues will be discovered, resolved, and then patched
quickly via the devel
=== Issue Tracker
-Experienced developers use the
https://issues.apache.org/jira/browse/SHIRO[issue tracker] directly, as they
are very sure when they have found a bug and when not. Less experienced users
should first discuss it on the user or developer mailing list (as appropriate).
Impatient people always enter everything into the issue tracker without caring
if it is a bug of Shiro, or their own installation/configuration mistake -
please do not do this.
+Experienced developers use the https://github.com/apache/shiro/issues[issue
tracker] directly, as they are very sure when they have found a bug and when
not. Less experienced users should first discuss it on the user or developer
mailing list (as appropriate). Impatient people always enter everything into
the issue tracker without caring if it is a bug of Shiro, or their own
installation/configuration mistake - please do not do this.
Discuss an issue on the developers mailing list first to work out any details.
After it is confirmed to be worthwhile, and you are clear about it, then submit
the bug description or patch via Bug Tracking.
Perhaps you do not get any answer on your first reply, so just post it again
until you get one. But please not every hour - allow a few days for the list to
deal with it. Bear in mind that other countries will have holidays at different
times to your country and that they are in different time zones. You might also
consider rewriting your initial posting. It may have not been clear to the
readers on the mailing list.
-=== Submitting a Patch Through Jira
+=== Submitting a Patch Through GitHub
-While we encourage you to submit your contribution through GitHub pull
requests, you can also attach a patch in a Jira ticket. For the purpose of
these instructions, we'll assume that you already have a system with Git and
have found a bug to fix or have a feature that you'd like to submit, and you're
willing to contribute that code or documentation under the Apache License 2.0.
+While we encourage you to submit your contribution through GitHub pull
requests, you can also attach a patch in a GitHub issue. For the purpose of
these instructions, we'll assume that you already have a system with Git and
have found a bug to fix or have a feature that you'd like to submit, and you're
willing to contribute that code or documentation under the Apache License 2.0.
Further, if you're fixing a bug, we'll assume that you've either filed a bug
report (where you will attach your patch) or are submitting a fix for a known
bug. If you find a bug and would like to fix it, that's awesome! Please be sure
to file the bug too, though.
@@ -141,7 +141,7 @@ Use `git add` to stage the changes. Commit the changes to
your working branch:
git commit -m "Insert a meaningful summary of changes here."
----
-Finally, you can create a patch and attach it to the Jira issue:
+Finally, you can create a patch and attach it to the Github issue:
[source,bash]
----
