Clarifying internal vs external contributing requirements

[jhkennedy]

In the contributing guide, there's a section on "Commits" which refers to a seemingly internal ticketing tool (jira?) and requests you include ticket numbers in your commits.

For outside contributors, it isn't clear how to handle this, and it invokes some questions, like:

• Where is the ticketing tool, can I see it/access it, and should I be using it?
• Should all contributors open a GitHub issue first and wait to receive a ticket number to be worked?
• Do all feature branch commits need to have that prefix, or will branches be squash-merged and the prefix added at that point?

[vinnyinverso]

These are all really good points. Thank you for raising them.

I added a ticket in our internal JIRA to address these issues. We're going to take a look at what other teams across EOSDIS have done as well as the feedback that you provided.

HARMONY-1836