We really appreciate the efforts of people who help in keeping the Dropilio updated. Dropilio is provides a important upgradation to the powerful Twilio API by helping the developers create more user oriented apps.
We suggest you to take a moment to review this document in order to make the contribution process easy and effective for everyone involved.
In order to maintain a uniformity across the application, we have made a certain set of rules and templates that you should follow in order to provide us with useful contributions. Following these guidelines will help to communicate that you respect the time of the developers managing and developing the code. In return, they should reciprocate that respect in addressing your issue, assessing changes, and helping you finalize your pull requests.
As for everything else in the project, the contributions to Dropilio are governed by the [Code of Conduct][code-of-conduct].
Dropilio is an open source project and we love to receive contributions from our community — you! You can contribute to the Dropilio in any way you want, that has the potential to make Dropilio a better website. Some common ways to contribute are listed below:
- Bug Tracking
- Feature Requests
- Blog Posts
- Documentation website
- Usecase Studies
- Open an issue and provide us with appropriate information.
- (Optional) If you can solve the issue filed by you, read below on how to submit a pull request.
If you find yourself wishing for a something that doesn't exist in Dropilio, you are probably not alone. Open an issue which describes the feature you would like to see, how it would affect the community, and how it should work.
- Create your own fork of the code.
- Do the changes in your fork.
- Send us a pull request with appropriate information using our Pull Request Template.