The goal of this document is to create a contribution process that:
* Encourages new contributions.
* Encourages contributors to remain involved.
* Avoids unnecessary processes and bureaucracy whenever possible.
* Creates a transparent decision making process which makes it clear how
contributors can be involved in decision making.
## Vocabulary
* A **Contributor** is any individual creating or commenting on an issue or pull request.
* A **Committer** is a subset of contributors who have been given write access to the repository.
# Logging Issues
Log an issue for any question or problem you might have. When in doubt, log an issue,
any additional policies about what to include will be provided in the responses. The only
exception is security disclosures which should be sent privately.
Committers may direct you to another repository, ask for additional clarifications, and
add appropriate metadata before the issue is addressed.
## Reporting bugs
Before submitting a bug report, please follow the checklist to help us address the bug efficiently:
- Make sure you are using the latest version.
- Check other open or closed issues within the project repository to see if other users have experienced the same bug.
- Regarding the bug:
- Detail the steps in reproducing the bug.
- Attach your input and output, if feasible.
- Attach the stack trace.
- Make note of your OS, Platform and Version.
- Make not of your environment configs (compiler, package manager, conda env dependencies)
- Verify that the bug is reproducible.
# Contributions
Any change to resources in this repository must be through pull requests. This applies to all changes
to documentation, code, binary files, etc.
:exclamation: No pull request can be merged without being reviewed.
You may request a specific contributor who is most versed in the issue at hand to review your pull request. Once all the feedback is addressed, any automated tests pass, and the pull request is approved, then the PR may be merged in.
In the case of an objection being raised in a pull request by another committer, all involved
committers should seek to arrive at a consensus by way of addressing concerns being expressed
by discussion, compromise on the proposed change, or withdrawal of the proposed change.
## First-time contributor
When making a contribution for the first time, please add your name to the `.zenodo.json` file. We strongly recommend adding your affiliation and ORCiD to the `zenodo.json` file. These additions only have to happen once.
@@ -28,7 +28,7 @@ though it does not require radiometric calibration).
- **Longitude Direction = East** Longitude values increase to the
east
Definitions for the geometric reference terms can be found in [Learning About Map Projections](../Camera%20Geometry%20and%20Projections/Learning%20About%20Map%20Projections.md)
Definitions for the geometric reference terms can be found in [Learning About Map Projections](../camera-geometry-and-projections/learning-about-map-projections.md)
## Camera Information Applications
@@ -175,7 +175,7 @@ Enceladus. In this example, **phocube** will generate a 6-band output
cube.
@TODO
!!! Note "The image used in this example has been processed through Level1 \[ingestion, spiceinit and radiometric calibration\]. Refer to: [Working with Cassini ISS Data](Camera%20Geometry.md)"
!!! Note "The image used in this example has been processed through Level1 \[ingestion, spiceinit and radiometric calibration\]. Refer to: [Working with Cassini ISS Data](camera-geometry.md)"
Each band will contain the information asked for (parameters set to
