Hi Aashna, First of all, thank you for having an interest in contributing to Apache Camel.
Here are some guidelines on how to best approach the Apache Camel community and how to best apply yourself. 1. Communication Apache Camel is an Apache Software Foundation project, all communication is done in the open on the project mailing lists. You can read more on the reasoning behind this to get a better understanding of: https://www.apache.org/foundation/mailinglists.html All communication is subject to the ASF Code of Conduct, which you can read here: https://www.apache.org/foundation/policies/conduct.html For questions and guidance around contributing subscribe to the developer's mailing list by sending an e-mail to dev-subscr...@camel.apache.org. We can also be reached on the Gitter chat at https://gitter.im/apache/apache-camel/. We track issues using ASF Jira located at: https://issues.apache.org/jira/browse/CAMEL Where we maintain a list of issues that are easy to get started with, so you can familiarize yourself with the process and get your first contribution in: https://issues.apache.org/jira/issues/?filter=12348073 And some areas that we are actively looking for help on: https://issues.apache.org/jira/issues/?filter=12348074 When you're ready to contribute create a Pull request to one of the Camel projects you can find under the Apache organization on GitHub: https://github.com/apache?q=camel Expect that your Pull request will receive a review and that you will need to respond and correspond to that via comments at GitHub. 2. Getting started Read the "Contributing to Apache Camel" document on the Camel website: https://camel.apache.org/manual/latest/contributing.html Identify areas you can contribute first. You don't have to be an expert in an area, the Apache Camel developers are available to offer help and guidance. Introduce yourself on the developer's mailing list (see above), tell us what area of work or problem you wish to address in Camel. Create a draft of your solution, this can be simple 1-2 sentences on the change you wish to make. Try to be as specific as you can: include a short description of your intent, what you tried and what didn't work, or what you need help with. The best way of approaching the developers is by describing what you would like to work on and asking specific questions on how to get started. We'll do our best to guide you and help you make your contribution. We also participate in Google Summer of Code and Outreachy programs, for information about those look at those program websites. If you wish to participate in either of those follow the guidelines and schedule set by those programs. If you're unsure please reach out via official communication channels of those programs, or ask on the developer's mailing list for help. 3. Your first contribution Make sure you followed the steps and guidelines outlined above. For bigger changes, make sure that you have discussed on the developer's mailing list or in the Jira issue tracker before hand. We love receiving contributions, to get the best response make sure that the reasoning behind the contribution you wish to make is clear: outline the problem and explain your solution for it. Make sure you follow the guidelines outlined in the "Contributing to Apache Camel" document. Be respectful of the source checks, formatting and the structure of the git commit message we abide by. This will help you in getting your contribution accepted. Outline any changes you made but are unaware or unsure of any consequences or sideeffects. Stay engaged, follow and respond to comments or questions you might be asked. With that I wish you all the best and please do have fun while contributing to Apache Camel, we certainly do :) zoran On Thu, Mar 5, 2020 at 5:39 PM Aashna Jena <jenaaas...@gmail.com> wrote: > > Dear mentor, > > Hello, I am Aashna Jena. Currently a junior at IIIT Hyderabad, India. > I was looking through the potential Outreachy projects for this season and > was interested in the project titled "Improve Apache Camel Website". > I want to start making some contributions to understand the code base and > would love it if you could help me in this direction. > > Thank you > Aashna Jena > Junior, IIIT Hyderabad -- Zoran Regvart
