Contributions are welcome and greatly appreciated!
The best way to get in touch with the core developers and mantainers is to join the PyLops slack channel as well as open new Issues directly from the github repo.
Moreover, take a look at the Roadmap page for a list of current ideas for improvements and additions to the PyLops library.
Types of Contributions¶
Report bugs at https://github.com/equinor/pylops/issues.
If you are playing with the PyLops library and find a bug, please report it including:
- Your operating system name and version.
- Any details about your Python environment.
- Detailed steps to reproduce the bug.
Propose New Operators or Features¶
Open an issue at https://github.com/equinor/pylops/issues with tag enhancement.
If you are proposing a new operator or a new feature:
- Explain in detail how it should work.
- Keep the scope as narrow as possible, to make it easier to implement.
Implement Operators or Features¶
Look through the Git issues for operator or feature requests. Anything tagged with enhancement is open to whoever wants to implement it.
Add Examples or improve Documentation¶
Writing new operators is not the only way to get involved and contribute. Create examples with existing operators as well as improving the documentation of existing operators is as important as making new operators and very much encouraged.
Getting Started to contribute¶
Ready to contribute?
- Fork the PyLops repo.
- Clone your fork locally:
>> git clone https://github.com/your_name_here/pylops.git
- Follow the installation instructions for developers that you find in Installation page. Ensure that you are able to pass all the tests before moving forward.
- Add the main repository to the list of your remotes (this will be important to ensure you pull the latest changes before tyring to merge your local changes):
>> git remote add upstream https://github.com/equinor/pylops
- Create a branch for local development:
>> git checkout -b name-of-your-branch
Now you can make your changes locally.
6. When you’re done making changes, check that your code follows the guidelines for Implementing new operators and that the both old and new tests pass successfully:
>> make tests
- Commit your changes and push your branch to GitLab:
>> git add . >> git commit -m "Your detailed description of your changes." >> git push origin name-of-your-branch
Remember to add
-u when pushing the branch for the first time.
- Submit a pull request through the GitHub website.
Pull Request Guidelines¶
Before you submit a pull request, check that it meets these guidelines:
- The pull request should include new tests for all the core routines that have been developed.
- If the pull request adds functionality, the docs should be updated accordingly.
- Ensure that the updated code passes all tests.