poliastro is a community project, hence all contributions are more than welcome!
Not only things break all the time, but also different people have different use cases for the project. If you find anything that doesn’t work as expected or have suggestions, please refer to the issue tracker on GitHub.
Documentation can always be improved and made easier to understand for newcomers. The docs are stored in text files under the docs/source directory, so if you think anything can be improved there please edit the files and proceed in the same way as with code writing.
The Python classes and methods also feature inline docs: if you detect any inconsistency or opportunity for improvement, you can edit those too.
Besides, the wiki is open for everybody to edit, so feel free to add new content.
To build the docs, you must first create a development environment (see
below) and then in the
docs/ directory run:
$ cd docs $ make html
After this, the new docs will be inside
build/html. You can open them
by running an HTTP server:
$ cd build/html $ python -m http.server 8000 --bind 127.0.0.1 Serving HTTP on 127.0.0.1 port 8000 (http://127.0.0.1:8000/) ...
And point your browser to http://127.0.0.1:8000.
Code contributions are welcome! If you are looking for a place to start, help us fixing bugs in poliastro and check out the “good first issue” tag. Those should be easier to fix than the others and require less knowledge about the library.
If you are hesitant on what IDE or editor to use, just choose one that you find comfortable and stick to it while you are learning. People have strong opinions on which editor is better so I recommend you to ignore the crowd for the time being - again, choose one that you like :)
If you ask me for a recommendation, I would suggest PyCharm (complete IDE, free and gratis, RAM-hungry) or vim (powerful editor, very lightweight, steep learning curve). Other people use Spyder, emacs, gedit, Notepad++, Sublime, Atom…
You will also need to understand how git works. git is a decentralized version control system that preserves the history of the software, helps tracking changes and allows for multiple versions of the code to exist at the same time. If you are new to git and version control, I recommend following the Try Git tutorial and Git Workflow tutorial.
If you already know how all this works and would like to contribute new features then that’s awesome! Before rushing out though please make sure it is within the scope of the library so you don’t waste your time -the mailing list or the chat are good places to ask.
If the feature you suggest happens to be useful and within scope, you will probably be advised to create a new wiki page with some information about what problem you are trying to solve, how do you plan to do it and a sketch or idea of how the API is going to look like. You can go there to read other good examples on how to do it. The purpose is to describe without too much code what you are trying to accomplish to justify the effort and to make it understandable to a broader audience.
All new features should be thoroughly tested, and in the ideal case the coverage rate should increase or stay the same. Automatic services will ensure your code works on all the operative systems and package combinations poliastro support - specifically, note that poliastro is a Python 3 only library.
These are some succinct steps to set up a development environment:
Install git on your computer.
Install flit using
python -m pip install flit wheel
Change into the local checkout of your repository and install it in development mode using
flit install --symlink(
--symlinkmeans that the installed code will change as soon as you change it in the download location).
Create a new branch.
Make changes and commit.
For more detailed explanations, please check out the Astropy development docs.