This is an automated email from the ASF dual-hosted git repository.
joerghoh pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-site.git
The following commit(s) were added to refs/heads/master by this push:
new 4509f2b update link for good-first-issues: just list open issues.
4509f2b is described below
commit 4509f2b8db23f9c80ca45285310fe44fab38d85e
Author: Joerg Hoh <[email protected]>
AuthorDate: Mon Feb 7 11:19:48 2022 +0100
update link for good-first-issues: just list open issues.
---
src/main/jbake/content/contributing.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/main/jbake/content/contributing.md
b/src/main/jbake/content/contributing.md
index edc7025..8c87215 100644
--- a/src/main/jbake/content/contributing.md
+++ b/src/main/jbake/content/contributing.md
@@ -33,7 +33,7 @@ If pull requests are familiar to you, the next step is to
open one against [one
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/issues/?jql=project%20%3D%20SLING%20AND%20labels%20%3D%20good-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.
+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/issues/?jql=project%20%3D%20SLING%20AND%20status%20%3D%20Open%20AND%20labels%20%3D%20good-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.
For relatively large contributions (e.g. new modules), we recommend one of the
following two approaches:
