Proposed CONTRIBUTING.md file using a standardized template

[riverma]

Purpose

• New CONTRIBUTING.md file format
• Leveraging https://nasa-ammos.github.io/slim/documentation/starter-kits/#contributing-guide-template
• NOTE: this is a DRAFT pull-request and it needs to be customized / adapted to your repo - please commit to this PR branch with your customizations before merging!
• NOTE: make your modifications by searching for the string INSERT in the file and replacing with appropriate values for your repo
• NOTE: read through the file thoroughly to ensure its well adapted for your repo and your scenario, feel free to modify as needed

Proposed Changes

• [ADD] CONTRIBUTING.md file with sample content

Testing

• For live example, see: https://github.com/riverma/terraformly/blob/main/CONTRIBUTING.md

[jpl-jengelke]

My concern with the contribution guide is the split arrow in the diagram that implies a PR can be duplicated between two repos. PRs are tied to repos in a 1:1 correspondence. So PR comments/metadata/metachanges on a forked repo will be not be seen in the main ("our repository") repo. I would remove the arrow that goes back to the forked repo with the PR. If users comment there it will be them commenting on the fork only. (PRs aren't carried with merges, only the content itself.) Sure, the content will be retained but I think there's value in documenting the process as well as the comments. Also, it's not customary for PRs on the fork to be the source of review -- gatekeeper is the PR on the main repo.

See image: