Merge upstream

CONTRIBUTING.md

+# Contributing Guide
+
+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.

docs/concepts/Camera Geometry and Projections/Camera Geometry.md → docs/concepts/camera-geometry-and-projections/camera-geometry.md

@@ -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
 true) in the following command:

docs/concepts/SPICE/SPICE Overview.md → docs/concepts/spice/spice-overview.md

@@ -33,7 +33,7 @@ processing will not be possible.
 
 At a minimum 'spiceinit' requires SpacecraftName, InstrumentId,
 TargetName, StartTime and StopTime. These keywords are loaded at the
-ingestion step ( [Importing Mission Data](../../getting-started/Using%20ISIS:%20First%20Steps/Locating%20and%20Ingesting%20Image%20Data.md) ).
+ingestion step ([Importing Mission Data](../../getting-started/using-isis-first-steps/locating-and-ingesting-image-data.md)).
 
 See also: [**Mission Specific
 Programs**](http://isis.astrogeology.usgs.gov/Application/index.html)

docs/how-to-guides/Image Processing/Map Projecting Images.md → docs/how-to-guides/image-processing/map-projecting-images.md

@@ -27,11 +27,11 @@ The main application to project an image is
     that is supported within ISIS
   @TODO
   - Proper ingestion of the image data into ISIS ( [**Importing Mission
-    Data**](Map%20Projecting%20Images.md) )
+    Data**](map-projecting-images.md) )
   @TODO
-  - Available [**SPICE**](Map%20Projecting%20Images.md) information for every
+  - Available [**SPICE**](map-projecting-images.md) information for every
     individual image
-  - A [**map template**](../../concepts/Camera%20Geometry%20and%20Projections/Learning%20About%20Map%20Projections.md) to define an
+  - A [**map template**](../../concepts/camera-geometry-and-projections/learning-about-map-projections.md) to define an
     output map projection
 
 
@@ -39,10 +39,10 @@ The main application to project an image is
 
 -----
 
-[**ISIS Supported Projections**](../../concepts/Camera%20Geometry%20and%20Projections/Learning%20About%20Map%20Projections.md)
+[**ISIS Supported Projections**](../../concepts/camera-geometry-and-projections/learning-about-map-projections.md)
 
   - For detailed information about Map Projections within ISIS refer to
-    [Learning About Map Projections](../../concepts/Camera%20Geometry%20and%20Projections/Learning%20About%20Map%20Projections.md) .
+    [Learning About Map Projections](../../concepts/camera-geometry-and-projections/learning-about-map-projections.md) .
 
 
 ## Defining an Output Map 
@@ -63,8 +63,8 @@ parameter to a supported map projection.
   - In conjunction with the supplied map templates; the default for an
     output map are as follows:
     
-      - The original [**raw camera geometry**](../../concepts/Camera%20Geometry%20and%20Projections/Camera%20Geometry.md)
-      - [**Computed parameters**](../../concepts/Camera%20Geometry%20and%20Projections/Learning%20About%20Map%20Projections.md)
+      - The original [**raw camera geometry**](../../concepts/camera-geometry-and-projections/camera-geometry.md)
+      - [**Computed parameters**](../../concepts/camera-geometry-and-projections/learning-about-map-projections.md)
       - The target body is defined in the system defaults which can be
         found in $ISISDATA/base/templates/targets/.
 
@@ -74,7 +74,7 @@ parameter to a supported map projection.
   - The viewing geometry of an image(s) are important details to
     consider when defining an output map projection.
       - There are a number of applications that report relevant
-        [**camera geometry**](../../concepts/Camera%20Geometry%20and%20Projections/Camera%20Geometry.md) information for a given
+        [**camera geometry**](../../concepts/camera-geometry-and-projections/camera-geometry.md) information for a given
         image or a list of images.
       - Does your input cover the north or south pole of the body?
       - Do you want your output map to be centered at a specific
@@ -82,7 +82,7 @@ parameter to a supported map projection.
       - Do you plan on mosaicking your images together?
       - An output mosaic (digital image map-DIM) is a major
         consideration before projecting multiple images. Refer to
-        [**Making Mosaics**](../../concepts/Camera%20Geometry%20and%20Projections/Learning%20About%20Map%20Projections.md).
+        [**Making Mosaics**](../../concepts/camera-geometry-and-projections/learning-about-map-projections.md).
 
 
 #### The Custom Map Template