[GitHub] [sling-site] joerghoh commented on a change in pull request #78: update the contribution page

[GitBox <gi...@apache.org>]

joerghoh commented on a change in pull request #78:
URL: https://github.com/apache/sling-site/pull/78#discussion_r794330303



##########
File path: src/main/jbake/content/contributing.md
##########
@@ -21,25 +21,20 @@ a committer.
 
 ## How to contribute
 
-Apache Sling is a volunteer effort, so there is always plenty of work that needs to be accomplished. If you want to help supporting Apache
-Sling, this page is intended as a starting point for specific contribution ideas. To further understand how the Sling community operates,
-refer to the [Community Roles and Processes document](https://www.apache.org/foundation/how-it-works.html) and/or join our mailing lists.
+Apache Sling is a volunteer effort, so there is always plenty of work that needs to be accomplished. If you want to help supporting Apache Sling, this page is intended as a starting point for specific contribution ideas. To further understand how the Sling community operates, refer to the [Community Roles and Processes document](https://www.apache.org/foundation/how-it-works.html) and/or join our [mailing lists](http://sling.apache.org/project-information.html#mailing-lists).
+
+For people who are completely new to contributing to an Apache Software Foundation project, the
+[Get Involved](https://www.apache.org/foundation/getinvolved.html) page provides you with enough resources to understand how the foundation works and how its projects are structured - and don't hesitate to ask on our [mailing lists](http://sling.apache.org/project-information.html#mailing-lists)!
 
 See [Project Information](/project-information.html) for details about the tools mentioned below.
 
-The Apache Sling project organizes its "to do" list using the Apache [JIRA issue tracking system](https://issues.apache.org/jira/browse/SLING).
-No matter if you are a programmer or not, it is probably best to check JIRA first to figure out if the problem you identified is already
-known. If not, please create a JIRA issue in which you try to describe to the best of your knowledge the bug that you want to fix or the
-improvement that you would like to contribute. There are many recommendations on the Web on how to write a good bug report, like
-[Haje Jan Kamps' How to write the perfect bug report](https://medium.com/@Haje/how-to-write-the-perfect-bug-report-6430f5a45cd) blog post.
+The Apache Sling project organizes its "to do" list using the Apache [JIRA issue tracking system](https://issues.apache.org/jira/browse/SLING). No matter if you are a programmer or not, it is probably best to check JIRA first to figure out if the problem you identified is already known. If not, please create a JIRA issue in which you try to describe to the best of your knowledge the bug that you want to fix or the improvement that you would like to contribute. There are many recommendations on the Web on how to write a good bug report, like [Haje Jan Kamps' How to write the perfect bug report](https://medium.com/@Haje/how-to-write-the-perfect-bug-report-6430f5a45cd) blog post.
+
+If pull requests are familiar to you, the next step is to open one against [one of our modules](https://github.com/apache/?q=sling&type=all&language=&sort=). If creating a pull request from your own repository, setting the _[allow edits from maintainers](https://docs.github.com/en/github/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork)_ option is convenient as it allows us to update your fork as the pull request evolves.
 
-If pull requests are familiar to you, the next step is to open one against one of our modules. If creating a pull request from your
-own repository, setting the
-_[allow edits from maintainers](https://docs.github.com/en/github/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork)_
-option is convenient as it allows us to update your fork as the pull request evolves.
+More details about how the project is structured in terms of repositories can be read on the [Getting and Building Sling](/documentation/development/getting-and-building-sling.html) page.
 
-More details about how the project is structured in terms of repositories can be read on the
-[Getting and Building Sling](/documentation/development/getting-and-building-sling.html) page.
+If you want to get involved into Sling development, we marked a number of issues in Jira with the label ["good-first-issue"](https://issues.apache.org/jira/browse/SLING-5767?jql=status%20%3D%20Open%20AND%20labels%20%3D%20easy-first-issue); we consider them a good starting point into Sling development. Just assign the ticket to you and create a pull request to address it. We provide you feedback and help you to get your contribution into Sling.

Review comment:
       thank you, fixed




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@sling.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org