[age-website] branch new-web updated: Update how.md

[ak...@apache.org]

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

ako pushed a commit to branch new-web
in repository https://gitbox.apache.org/repos/asf/age-website.git


The following commit(s) were added to refs/heads/new-web by this push:
     new 1c41a22  Update how.md
1c41a22 is described below

commit 1c41a22fcba79ca55ab29be749fcb68cee0c7f2c
Author: Andrew Ko <76...@users.noreply.github.com>
AuthorDate: Tue Sep 6 14:57:52 2022 +0900

    Update how.md
---
 src/pages/contribution/how.md | 48 ++++++++-----------------------------------
 1 file changed, 8 insertions(+), 40 deletions(-)

diff --git a/src/pages/contribution/how.md b/src/pages/contribution/how.md
index b53dcc7..e672884 100644
--- a/src/pages/contribution/how.md
+++ b/src/pages/contribution/how.md
@@ -9,12 +9,12 @@ title:
 There are multiple ways you can contribute to the project. And help is always welcome! All details can be found on the contributing page. Keep reading for a quick overview!
 
 ## Becoming a Committer
-If you are interested in the project and looking for ways to help, consult the list of tasks in JIRA, or ask the mailing list.
+If you are interested in the project and looking for ways to help, consult the list of projects in the Apache AGE and AGE Viewer GitHub repositories, or ask the mailing list.
 
-## Contributing by Helping Other Users
-A great way to contribute to AGE is to help answer user questions on the mailing list or on StackOverflow. There are always many new AGE users; taking a few minutes to help answer a question is a very valuable community service. 
+## Contributing by Helping Others
+A great way to contribute to AGE is to help answering questions from other community members or making comments on the mailing lists, GitHub Issues or on the Apache AGE Reddit forum (r/apacheage). There are always many new AGE users; taking a few minutes to help answer a question is a very valuable community service. 
 
-Contributors should subscribe to this list and follow it to keep up to date on what's happening in AGE. Answering questions is an excellent and visible way to help the community, which also demonstrates your expertise.
+Contributors should subscribe to the mailing lists and/or join the Apache AGE Reddit community (r/apacheage) to keep up to date on what's happening in AGE. Answering questions is an excellent and visible way to help the community, which also demonstrates your expertise.
 
 ## Contributing by Reviewing Changes
 Changes to AGE source code are proposed, reviewed, and committed via Github pull requests (described in Developer Guidelines). Anyone can view and comment on active changes here. Reviewing others' changes is a good way to learn how the change process works and gain exposure to activity in various parts of the code. You can help by reviewing the changes and asking questions or pointing out issues as simple as typos or small issues of style.
@@ -23,42 +23,10 @@ Changes to AGE source code are proposed, reviewed, and committed via Github pull
 To propose a change to release documentation (that is, docs that appear here), edit the Markdown source files in the right branch on the Age website repository. The documentation will be build automatically after the changes have been merged.
 
 ## Contributing Bug Reports
-Ideally, bug reports are accompanied by a proposed code change to fix the bug. This isn't always possible, as those who discover a bug may not have the experience to fix it. A bug may be reported by creating a JIRA issue but without creating a pull request. 
+Ideally, bug reports are accompanied by a proposed code change to fix the bug. This isn't always possible, as those who discover a bug may not have the experience to fix it. A bug may be reported by creating a GitHub issue but without creating a pull request. 
 
-Bug reports are only useful, however, if they include enough information to understand, isolate and ideally reproduce the bug. Simply encountering an error does not mean a bug should be reported; search JIRA and inquire on the AGE user / dev mailing lists first. Unreproducible bugs, or simple error reports, may be closed. 
+Bug reports are only useful, however, if they include enough information to understand, isolate and ideally reproduce the bug. Simply encountering an error does not mean a bug should be reported; search GitHub and inquire on the Apache AGE's dev mailing list first. Unreproducible bugs, or simple error reports, may be closed. 
 
-The more context the reporter can give about a bug, the better, such as: how the bug was introduced, by which commit, etc. It assists the committers in the decision process on how far the bug fix should be backported, when the pull request is merged. The pull request to fix the bug should narrow down the problem to the root cause. Data correctness/data loss bugs are very serious. Make sure the corresponding bug report JIRA issue is labeled as correctness or data-loss. Please send an emai [...]
+The more context the reporter can give about a bug, the better, such as: how the bug was introduced, by which commit, etc. It assists the committers in the decision process on how far the bug fix should be backported, when the pull request is merged. The pull request to fix the bug should narrow down the problem to the root cause. Data correctness/data loss bugs are very serious. Make sure the corresponding bug report GitHub issue is labeled as correctness or data-loss. Please send an em [...]
 
-## Contributing to JIRA Maintenance
-Most contributors can directly resolve JIRA issues. Use judgment in determining whether you are confident the issue should be resolved (although changes can be easily undone). When resolving JIRA tickets, please observe the following conventions:
-
-When resolving JIRA tickets, please observe the following conventions:
-
-* Resolve as Fixed if there's a release or code commit that resolved the issue.
-  * Set Fix Version(s), if and only if the resolution is Fixed
-  * Set Assignee to the person who contributed the most to its resolution, usually the person who opened the PR that resolved the issue.
-* For issues that can't be reproduced against master as reported, resolve as Cannot Reproduce.
-* If the issue is the same as or a subset of another issue, resolved as Duplicate
-  * Mark the issue that has less activity or discussion as the duplicate.
-  * Link it to the JIRA ticket it duplicates.
-* If the issue seems clearly obsolete and applies to issues or components that have changed radically since it was opened, resolve as Not a Problem
-* If the issue doesn't make sense or is not actionable resolve as Invalid.
-* If it's a coherent issue, but there is a clear indication that there is no support or interest in acting on it, then resolve as Won't Fix.
-
-<b>Searching JIRA</b> How to search JIRA for existing issues:
-
-1. Basic:
-    1. Visit <b>AGE JIRA</b>
-    2. Type query into search box in top right (beware this will return results from all projects)
-<br />
-
-2. Advanced:
-    1. Visit AGE JIRA Advanced Search
-    2. Replace the empty quotes with quoted text (such as "cypher")
-<br />
-
-3. Search Now:
-    1. Use the search box below
-    2. Search
-
-</div>
\ No newline at end of file
+</div>