We would like to thank you for your interest in The Gita Initiative and are grateful that you have decided to make a contribution. We are very excited to work with you.
We invite you to join our team! Everyone is welcome to contribute code via pull requests, to file issues on GitHub, to help people asking for help, to help triage, reproduce, or fix bugs that people have filed, to add to our documentation, or to help out in any other way.
We grant commit access to people who have gained our trust and demonstrated a commitment to Bhagavad Gita.
We communicate primarily over Github and on chat channels.
The goal of this document is to provide a high-level overview of how you can get involved.
Have a question? Rather than opening an issue, please ask away on our chat channels.
The active community will be eager to assist you.
Your comments and feedback are welcome, and the development team is available via a handful of different channels.
See the Feedback Channels wiki page for details on how to share your thoughts.
Have you identified a reproducible problem in any of the apps? Have a feature request? We want to hear about it! Here's how you can make reporting your issue as effective as possible.
The Gita Initiative is distributed across multiple repositories. Try to file the issue against the correct repository. Check the list of Related Projects if you aren't sure which repo is correct.
Before you create a new issue, please do a search in open issues to see if the issue or feature request has already been filed.
Be sure to scan through the most popular feature requests.
If you find your issue already exists, make relevant comments and add your reaction. Use a reaction in place of a "+1" comment:
- 👍 - upvote
- 👎 - downvote
If you cannot find an existing issue that describes your bug or feature, create a new issue using the guidelines below.
File a single issue per problem and feature request. Do not enumerate multiple bugs or feature requests in the same issue.
Do not add your issue as a comment to an existing issue unless it's for the identical input. Many issues look similar, but have different causes.
The more information you can provide, the more likely someone will be successful at reproducing the issue and finding a fix.
Please remember to do the following:
-
Search the issue repository to ensure your report is a new issue
-
Simplify your code around the issue to better isolate the problem
Don't feel bad if the developers can't reproduce the issue right away. They will simply ask for more information!
If you are interested in writing code to fix issues, please see How to Contribute in the wiki.
Your contributions to open source, large or small, make great projects like this possible. Thank you for taking the time to contribute.