Thank you for considering contributing! I write libraries in my free time and contributions from others help me make great tools. Help of any kind is appreciated.
Following these guidelines helps to communicate that you respect my time, as the developer managing and developing this open source project. In return, I should reciprocate that respect in addressing your issue, assessing changes, and helping you finalize your pull requests.
Questions and pull requests are more than welcome. I believe bad documentation is a bug, so if anything is unclear, please file an issue! Ideally, my answer to your question will be in an update to the docs.
Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.
Working on your first Pull Request? You can learn how from this free series How to Contribute to an Open Source Project on GitHub.
If you're using this API for any reason, I'd love to hear from you to understand your use case and priorities. This is a hobby project, and I don't use the API myself, so user feedback would be wonderful.
- Follow the Code of Conduct.
- Keep your commits clear and your pull requests small.
- Be gentle to the HORIZONS telnet service
- Ask questions! I like writing good documentation, and questions make that work more meaningful. Use the issue tracker for questions. There's a questions tag on the issue tracker for that reason.
- Tests are always welcome! Text parsing can be complicated, and NASA is changing the contents of the telnet service all the time.
- Searching issues or pull requests tagged "help wanted" or "good first issue" are great places to get started.
GitHub makes it really easy to submit pull requests. Just:
- Create your own fork of the code
- Do the changes in your fork
- Submit a pull request
I don't require a CLA or anything like that.
The project kanban board is where I prioritize tasks. I want to touch on most major functionality of JPL's Horizons before I try to make any component feature-complete. Correctness of response is also a high priority, so if you are aware of any bug that yields incorrect data, please submit an issue.
If you find a security vulnerability, do NOT open an issue. Contact Rosa on keybase.io instead!
In order to determine whether you are dealing with a security issue, ask yourself these two questions:
- Can I access something that's not mine, or something I shouldn't have access to?
- Can I disable something for other people?
If the answer to either of those two questions are "yes", then you're probably dealing with a security issue. Note that even if you answer "no" to both questions, you may still be dealing with a security issue, so if you're unsure, message me directly.
Please open an issue and follow the directions in the issue template.
Feature requests give meaning to my work. Open an issue that decribes the feature you'd like to see, why you need it, and how you'd like it to work.
As the primary developer, I will be the one reviewing all pull requests. I check GitHub almost every day, so you should be able to hear back from me quickly. However, I only do this in my free time, so please allow me flexibility.
I'm on keybase if you need to message me directly.
If you like this contribution guide, please give a star to Nadia Eghbal's contributing-template project on GitHub.
It was a great help.