Welcome to the dicom_parser repository! We're excited you're here and want to contribute.
These guidelines are designed to make it as easy as possible to get involved. If you have any questions that aren't discussed below, please let us know by opening an issue!
Before you start you'll need to set up a free GitHub account and sign in.
Already know what you're looking for in this guide? Jump to the following sections:
The current list of issue labels are here and include:
-
These issues point to problems in the project.
If you find a new bug, please provide as much information as possible to recreate the error. The issue template will automatically populate any new issue you open, and contains information we've found to be helpful in addressing bug reports. Please fill it out to the best of your ability!
If you experience the same bug as one already listed in an open issue, please add any additional information that you have as a comment.
-
These issues contain a task that a member of the team has determined we need additional help with.
If you feel that you can contribute to one of these issues, we especially encourage you to do so! Issues that are also labelled as good-first-issue are a great place to start if you're looking to make your first contribution.
-
These issues are asking for new features to be added to the project.
Please try to make sure that your requested enhancement is distinct from any others that have already been requested or implemented. If you find one that's similar, but there are subtle differences, please reference the other request in your issue.
We appreciate all contributions to dicom_parser, but those accepted fastest will follow a workflow similar to the following:
This allows other members of the dicom_parser development team to confirm that you aren't overlapping with work that's currently underway and that everyone is on the same page with the goal of the work you're going to carry out.
This blog is a nice explanation of why putting this work in up front is so useful to everyone involved.
2. Fork the dicom_parser repository to your profile.
This is now your own unique copy of the dicom_parser repository. Changes here won't affect anyone else's work, so it's a safe space to explore edits to the code!
You can clone your dicom_parser repository in order to create a local copy of the code on your machine. To install your version of dicom_parser, and the dependencies needed for development, in your Python environment, run pip install -e ".[dev]" from your local dicom_parser directory.
Make sure to keep your fork up to date with the original dicom_parser repository. One way to do this is to configure a new remote named "upstream" and to sync your fork with the upstream repository.
When you are working on your changes, test frequently to ensure you are not breaking the existing code. For more on testing, please see the testing section of dicom_parser README.
It's a good practice to create a new branch of the repository for a new set of changes.
4. Submit a pull request.
A new pull request for your changes should be created from your fork of the repository.
pre-commit is a git hook for running operations at commit time. To use it in your environment, do pip install pre-commit following by pre-commit install inside your source directory.
Pull requests should be submitted early and often (please don't mix too many unrelated changes within one PR)! If your pull request is not yet ready to be merged, please also include the [WIP] prefix (you can remove it once your PR is ready to be merged) or label it is a "draft". This tells the development team that your pull request is a "work-in-progress", and that you plan to continue working on it.
Review and discussion on new code can begin well before the work is complete, and the more discussion the better! The development team may prefer a different path than you've outlined, so it's better to discuss it and get approval at the early stage of your work.
One your PR is ready a member of the development team will review your changes to confirm that they can be merged into the main codebase.
New code should be tested, whenever feasible. Bug fixes should include an example that exposes the issue. Any new features should have tests that show at least a minimal example. If you're not sure what this means for your code, please ask in your pull request.
We welcome and recognize all contributions from documentation to testing to code development.
The development team member who accepts/merges your pull request will update the CHANGES file to reference your contribution.
You can see a list of current contributors in our zenodo file. If you are new to the project, don't forget to add your name and affiliation there!
You're awesome. 👋😃
— Based on contribution guidelines from the nipype project.