Add contributing docs

Does not contain links to issues and does not have a code of conduct

Signed-off-by: Mick Tarsel <[email protected]>

Author: mtarsel

CONTRIBUTING.md

@@ -0,0 +1,40 @@
+# Contributing
+
+[fork]: https://github.com/IBM/python-versions-pz/fork
+
+We're thrilled that you'd like to contribute to this project. Your help is essential for keeping it great.
+
+Contributions to this project are welcome under the [Apache](LICENSE) license.
+
+## Contents
+- [Submitting a pull request](#submitting-a-pull-request)
+- [Code style guide (coming soon!)](#code-style-guide)
+
+## Submitting a pull request
+
+1. [Fork][fork] and clone the repository.
+2. Create a new branch: `git checkout -b my-branch-name`.
+3. Make your changes, ensuring that they include steps to install and validation post-install
+4. Test your changes by creating and deploying the image
+5. Push to your fork and [submit a pull request][pr].
+
+### Commit Messages
+
+__All commit messages must include a Sign-off line__
+
+Please consider out commit message standards in order for your contribution to be merged into the main branch.
+
+#### Subject Line
+* __Conciseness__: Limit the subject line to around 50 characters to ensure readability in various Git tools.
+* __Imperative Mood__: Use the imperative mood, as if giving a command. For example, "Fix bug" instead of "Fixed bug" or "Fixes bug."
+* __Capitalization__: Capitalize the first letter of the subject line.
+* __No Period__: Do not end the subject line with a period.
+* __Clarity__: Summarize the core change or purpose of the commit clearly and directly.
+
+#### Body (Optional but highly recommended)
+* __Separate from Subject__: Leave a blank line between the subject line and the body.
+* __Explain "What" and "Why"__: Detail what changes were made and, more importantly, why those changes were necessary. Focus on the problem solved or the feature implemented, rather than the specific implementation details (the "how").
+* __Wrap Lines__: Wrap body lines at approximately 72 characters for better readability.
+* __Provide Context__: Include any relevant context, such as links to issues, bug reports, or design documents, if applicable.
+* __Explain Side Effects__: Note any potential side effects or non-obvious consequences of the changes. 
+