Adopt “good first issue” and CONTRIBUTING.txt/md/adoc

In order for community members to be able to contribute, we should make it easy for them to discover issues that they can pick up and work on. For contributors newly joining the community, some projects have adopted the “good-first-issue” or “Good First Issue” label on the issue trackers.

Project owners should update their mindset and proactively create and label issues that are easy to pick up for community members.

Tip
Do not spend too much time on this activity. Label only a couple of issues to get the ball rolling and have a link to add to the contributing guide.

Examples:

https://github.com/quarkusio/quarkus/labels/good%20first%20issue (GitHub issues)

https://issues.redhat.com/issues/?jql=labels%20%3D%20good-first-issue (Jira)

Activity

Analyze issues that are suitable for first time contributors and label them. Link to them from the contributing guide. Update the spreadsheet with the status.

This CONTRIBUTING file explains how people can contribute to the project (what the development process looks like, how to interact with SCM, setting up IDE, how to create useful Jiras, etc). This file can help people submit well-formed pull requests.

GitHub links to this file, on the page "New Issue" and the page "New Pull Request".

Examples:

https://github.com/wildfly-security/wildfly-elytron/blob/1.x/CONTRIBUTING.md

https://github.com/hal/console/blob/main/CONTRIBUTING.md

Activity

Create/update/verify CONTRIBUTING file is present and properly picked up by GitHub. If it isn’t open a pull request to remedy the situation. Update the spreadsheet with the status.

link to document: https://docs.google.com/document/d/1dbOk4eorV4LQGNrhNVB1bLyiowGBkhdf5o3bLNEfVJY