Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given.
You can contribute in many ways:
Types of Contributions
If you are reporting a bug, please include:
Your operating system name and version.
Any details about your local setup that might be helpful in troubleshooting.
Detailed steps to reproduce the bug.
Look through the GitHub issues for bugs. Anything tagged with “bug” and “help wanted” is open to whoever wants to implement it.
Look through the GitHub issues for features. Anything tagged with “enhancement” and “help wanted” is open to whoever wants to implement it.
rapid-models could always use more documentation, whether as part of the official rapid-models docs, in docstrings, or even on the web in blog posts, articles, and such.
The best way to send feedback is to file an issue at https://dnvgl-one.visualstudio.com/GRD%20Maritime/_git/rapid_models/issues.
If you are proposing a feature:
Explain in detail how it would work.
Keep the scope as narrow as possible, to make it easier to implement.
Remember that this is a volunteer-driven project, and that contributions are welcome :)
Ready to contribute? Here’s how to set up rapid_models for local development.
Clone the rapid_models repo on GitHub.
Install your local copy into a pyenv or conda environment.
Create a branch for local development:
$ git checkout -b name-of-your-bugfix-or-feature
Now you can make your changes locally.
When you’re done making changes, check that your changes pass flake8 and the tests, including testing other Python versions with tox:
$ flake8 rapid_models tests $ python setup.py test or pytest $ tox
To get flake8 and tox, just pip install them into your Python environment.
Commit your changes and push your branch to the source repo:
$ git add . $ git commit -m "Your detailed description of your changes." $ git push origin name-of-your-bugfix-or-feature
Submit a pull request through the Azure DevOps website.
Pull Request Guidelines
Before you submit a pull request, check that it meets these guidelines:
The pull request should include tests.
If the pull request adds functionality, the docs should be updated. Put your new functionality into a function with a docstring, and add the feature to the list in README.md.
The pull request should work for Python 3.7 and 3.8 (will be tested by a DevOps pipeline when pull request is being made)
To run a subset of tests:
$ pytest tests.test_rapid_models
A reminder for the maintainers on how to deploy. Make sure all your changes are committed (including an entry in HISTORY.rst). Then run:
$ bump2version patch # possible: major / minor / patch $ git push $ git push --tags