How To Contribute
Apache Hop is developed by an open and friendly community. Everybody is cordially welcome to join the community and contribute to Apache Hop. There are several ways to interact with the community and to contribute to Hop including asking questions, filing bug reports, proposing new features, joining discussions on the mailing lists, contributing code or documentation, improving the website, or testing release candidates.
What do you want to do?
Contributing to Hop goes beyond writing code for the project. Below, we list different opportunities to help the project:
| Area | Further Information |
|---|---|
Report a Bug | To report a problem with Hop, open Hop’s GitHub Issues, log in if necessary, and click on the "New issue" button. Please give detailed information about the problem you encountered and, if possible, add a description that helps to reproduce the problem. For more information go to our info page. |
Contribute Code | Read the Code Contribution Guide |
Help With Code Reviews | Read the Code Review Guide |
Help Prepare a Release | Read the Release Review Guide |
Contribute Documentation | Read the Documentation Contribution Guide |
Translate Hop | Read the Translation Contribution Guide |
Support Hop Users | - Join us on our Slack, more information on how to join here - Check out our GitHub Discussions and help someone out - Reply to Hop related questions on Stack Overflow with the hop tag or the Hop forums - Check the latest issues in GitHub for tickets which are actually user questions |
Improve the Website | Read the Website Contribution Guide |
Spread the Word about Hop | - Organize or attend a Hop Meetup - Contribute to the Hop blog (coming soon) |
Any other questions? Reach out on the Hop Mailing lists to get help. | |
Further Reading
Submit a Contributor License Agreement
Please submit a contributor license agreement to the Apache Hop if you are contributing a lot of code to Apache Hop. The following quote from http://www.apache.org/licenses gives more information about the ICLA and CCLA and why they are necessary.
The ASF desires that all contributors of ideas, code, or documentation to the Apache projects complete, sign, and submit (via postal mail, fax or email) an Individual Contributor License Agreement (CLA) [ PDF form ]. The purpose of this agreement is to clearly define the terms under which intellectual property has been contributed to the ASF and thereby allow us to defend the project should there be a legal dispute regarding the software at some future time. A signed CLA is required to be on file before an individual is given commit rights to an ASF project.
For a corporation that has assigned employees to work on an Apache project, a Corporate CLA (CCLA) is available for contributing intellectual property via the corporation, that may have been assigned as part of an employment agreement. Note that a Corporate CLA does not remove the need for every developer to sign their own CLA as an individual, to cover any of their contributions which are not owned by the corporation signing the CCLA.
Becoming a Hop Committer and PMC member
How to become a committer
Committers are community members that have write access to the project’s repositories, i.e., they can modify the code, documentation, and website by themselves and also accept other contributions.
There is no strict protocol for becoming a committer or PMC member. Candidates for new committers are typically people that are active contributors and community members.
As in all Apache projects, candidates for new committers are suggested by current committers or PMC members, and voted upon by the PMC.
If you would like to become a committer, we encourage you to engage with the community and start contributing to Apache Hop in any possible way. Contributions come in many shapes and forms, and the Hop community appreciates every contributor and contribution. You might also want to talk to other committers and ask for their advice and guidance.