Dear Orekit users,
Would you like to go further than just using Orekit? Would you like to contribute to the project, but don’t know where to start? Are you afraid of embarking on a complicated development project when you’re not yet familiar with Orekit’s architecture and source code?
In that case, please note that there are currently 13 open issues tagged “Easy to fix”. As for how to contribute, we explain everything in the contribution guide. If that’s not enough, we’ll be happy to answer any questions you may have.
Source code isn’t everything. There are many other ways to make valuable contributions to the project. For example, you can improve the Orekit tutorials or suggest new ones (by the way, the list announced on the website appears not up to date when compared to the repository). You can also contribute to the project’s website (to tell the truth, we’ve even been thinking for a long time of creating a new website, more in the style of the day, possibly using another static generator, more efficient than Jekyll).
I’m certainly forgetting a lot of useful stuff. Don’t hesitate to propose your ideas on the forum. We look forward to hearing from you! 