Great to have you here. Here are a few ways you can help make kepler.gl even better!
The DCO is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:
By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or
(b) The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or
(c) The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it.
(d) I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.
Contributors sign-off that they adhere to these requirements by adding a Signed-off-by line to commit messages.
--signoffcommand line to append this automatically to your commit message:
$ git commit -s -m 'This is my commit message'
We are trying to keep our Github page for issues, bugs and feature requests only. You've got much better chances of getting supports on Stack Overflow. Many people including our engineers are ready to answer questions on Stack Overflow. Your question might already been answered there.
If you would like to implement a new feature then consider what kind of change it is:
- Pick your item Pick an item to execute
- Claim the item Reply in the ticket linked in the roadmap to claim the item, one of the member of the technical team will respond
- Major Changes that you wish to contribute to the project should be discussed first in an[GitHub issue][github-issues] that clearly outlines the changes and benefits of the feature.
- Let's review your code Create a pull request
- Make your changes in a new git branch:
$ git checkout -b my-fix-branch master
- Create your patch commit, including appropriate test cases.
- Commit your changes using a descriptive commit message that follows ourcommit message conventions. Adherence to the conventions is required, because release notes are automatically generated from these messages.