Hi Prerna, We much appreciate your interest and willingness to contribute, I don't think it makes much sense for all of you to work on the same issue. There's also no need to have a competition on who gets to contribute first, we have plenty of other issues (outlined below) that you can help with. Since most of you are interested in participating in the Outreachy program, and help with the website, please have a look at some issues in that area via this search:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20status%20%3D%20Open%20AND%20component%20%3D%20website And feel free to propose new ideas by creating new issues around the website. For those wondering how to get started contributing to the website. Make sure have a [GitHub account|https://github.com/join], read how you can [get started|https://help.github.com/en/github/getting-started-with-github], and [create a pull request|https://help.github.com/en/github/collaborating-with-issues-and-pull-requests]. Have a look at the [README.md|https://github.com/apache/camel-website/blob/master/README.md] in the website project on how to build and how to preview your changes on your own computer. I'll try to address the questions in you comments here, for future conversations please do subscribe to the developer's mailing list and send emails there, discussions on the Jira issues can get a bit out of control and it's not that easy to follow the conversation here. The following text includes information on how to reach us, and get started: 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 side effects. 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 :) On Thu, Mar 5, 2020 at 10:40 PM prerna singh <psingh1999...@gmail.com> wrote: > > Hello , > I am Prerna Singh, a 2nd year undergraduate student of NIT Jamshedpur, > India. I am interested in this project and want to work for it. I am a > novice to Open Source but I love to learn new things and I will do this too. > Kindly help me get started with this. > Thank you -- Zoran Regvart
