Contribution Guide

[dmikusa]

Hi all! We put this guide together for community members that are interested in participating in the Paketo Java subteam. It gives some guidelines for helping the project and becoming a contributor and/or maintainer. Please feel free to post below with questions about the guide. If you have questions about your specific journey, please reach out in #java on Slack.

For those that are interested, there are four ways to join the team.

Java Subteam Contributor

Java subteam contributors contribute to all of the buildpacks across the team and subsequently have contribution rights and responsibilities across all of the repos.

• Follow the project level instructions here
• Has submitted at least 5 PRs across multiple Java subteam projects.
• Participates with the team (examples: joins Paketo WG meetings, joins Java subteam meeting, or talks asynchronously in #java and/or on Github). There is no preference or requirement for synchronous or asynchronous communication. You may contribute in the manner that best suits you.
• Contributes feedback and thoughts on Java subteam RFCs.
• Follow the project code-of-conduct

Java Subteam Maintainer

Java subteam maintainers contribute to all of the buildpacks across the team and subsequently have maintainer rights and responsibilities across all of the repos.

• Follow the project level instructions here
• Has submitted at least 10 PRs to multiple Java subteam prjoects. We would like to see at least one that is a substantial feature enhancement.
• Seeks out and submits PRs for project maintenance related tasks (i.e. CI maintenance, dependency maintenance, non-feature related work).
• Continues to participate on the team
• Continues to participate in RFC discussions
• Has championed at least one RFC. You don’t necessarily have to be the one to submit it, but you should be the one to help it make progress and help with the implementation (i.e. help it go from idea to reality).
• Demonstrates clean coding practices and follows styles and conventions used by the Java team
• Participates in PR review & demonstrates kind/thoughtful feedback to both help encourage contributions and facilitate good code.
• Follow the project code-of-conduct

Java Subteam Buildpack Contributor

Java subteam buildpack contributors contribute to one particular buildpack in the team and subsequently have contribution rights and responsibilities for that buildpack's repo.

• Follow the project level instructions here
• Has submitted at least 5 PRs to the particular buildpack project.
• Demonstrates clean coding practices and willingness to follow styles and conventions used by the Java team.
• Participates with the team (examples: joins Paketo WG meetings, joins Java subteam meeting, or talks asynchronously in #java and/or on Github). There is no preference or requirement for synchronous or asynchronous communication. You may contribute in the manner that best suits you.
• Follow the project code-of-conduct

Java Subteam Buildpack Maintainer

Java subteam buildpack maintainers contribute to one particular buildpack in the team and subsequently have maintainer rights and responsibilities for that buildpack's repo.

• Follow the project level instructions here
• Has submitted at least 10 PRs to the particular buildpack project. We would like to see at least one that is a substantial feature enhancement.
• Seeks out and submits PRs related to buildpack maintenance such as code refactoring, updating libraries, updating deprecated code.
• Continues to participate on the team
• Continues to participate in RFC discussions related to the buildpack
• Work with maintainers around release planning for the buildpack.
• Demonstrates clean coding practices and follows styles and conventions used by the Java team
• Participates in PR review & demonstrates kind/thoughtful feedback to both help encourage contributions and facilitate good code.
• Follow the project code-of-conduct