Added Contribution guidelines doc

Author: spcaipers-arm

CONTRIBUTING.md

@@ -0,0 +1,68 @@
+# Contribution Guide
+
+Thank you for your interest in contributing to our project! We strive to maintain a welcoming and inclusive community.
+
+## Ways to Contribute
+
+There are multiple ways you can contribute to this project:
+
+1. **Report an Issue**: If you encounter a bug or have a suggestion, please open an issue on our
+[GitHub Issues page](https://github.com/Open-CMSIS-Pack/devtools/issues) to start the discussion about your proposal.
+
+2. **Open a Pull Request**: Contributions are welcome, whether you're fixing a bug, adding a new feature, or improving
+documentation. You can submit a pull request to our
+[GitHub repository](https://github.com/Open-CMSIS-Pack/devtools/pulls) to:
+   - Provide a bug fix
+   - Add new features or enhancements
+   - Improve or expand existing documentation
+
+### Report an Issue
+
+Please feel free to raise an [issue on GitHub](https://github.com/Open-CMSIS-Pack/Open-CMSIS-Pack/issues)
+to report misbehavior (i.e. bugs)
+
+Issues are your best way to interact directly with the maintenance team and the community.
+We encourage you to append implementation suggestions as this helps to decrease the
+workload of the very limited maintenance team.
+
+We shall be monitoring and responding to issues as best we can.
+Please attempt to avoid filing duplicates of open or closed items when possible.
+In the spirit of openness we shall be tagging issues with the following:
+
+- **bug** – This issue is identified as a bug and will be investigated.
+- **discussion** – This issue is currently under discussion.
+- **discussion done** – The discussion on this issue is complete.
+- **documentation** – This issue highlights a documentation gap, which will be addressed in future updates.
+- **duplicate** – This issue duplicates an existing one; see comments for related references.
+- **enhancement** – This issue represents a request for a new feature or improvement.
+- **question** – We need further information or clarification on this issue; please review and respond.
+- **wontfix** – While we appreciate this suggestion, we have decided not to make changes at this time.
+
+### Open a Pull Request
+
+We encourage contributions of all sizes, but please keep each contribution focused and independent. We prefer smaller,
+more manageable pull requests, which makes it easier for us to review, provide feedback, and merge changes quickly.
+
+#### Contribution Process
+
+To make a successful contribution, please follow these steps:
+
+1. **Fork the Repository**: Start by forking the repository to your GitHub account.
+
+2. **Make Your Changes**:
+   - Implement your changes, ensuring that you match the existing coding style and documentation conventions.
+   - Write unit tests for your code to ensure it is functional and reliable.
+
+3. **Write a Clear Commit Message**: Write a concise and informative commit message summarizing your changes.
+
+4. **Push to Your Fork**: Push your changes to your forked repository.
+
+5. **Submit a Pull Request (PR)**: Open a pull request against the main repository.
+
+### Review Process
+
+Our team will review your proposed changes as soon as possible. Since our tools are complex and cover a wide range of
+use cases, we may request additional modifications. This helps ensure that your contribution meets our quality
+standards, is generally applicable, and doesn’t negatively impact other use cases or maintainability.
+
+Thank you for helping us improve this project! We value your effort and commitment.

README.md

@@ -455,50 +455,3 @@ configuration.
 ## License
 
 Open-CMSIS-Pack is licensed under Apache 2.0.
-
-## Contributions and Pull Requests
-
-Contributions are accepted under Apache 2.0. Only submit contributions where you have authored all of the code.
-
-### Proposals, Reviews and Project
-
-Please feel free to raise an [issue on GitHub](https://github.com/Open-CMSIS-Pack/Open-CMSIS-Pack/issues)
-to start the discussion about your proposal.
-
-We are in the early days and discuss proposals which we are dividing into 5 work streams with a dedicated label:
-
-- **Core Library Components** - common libraries that are re-used across a range of tools. The PoC Tools are the first
-  consumers, but the library components can also be used to create commercial derivatives or in-house tooling.
-- **Overall Project Concept** - procedures to generate packs and application software. We shall consider complex
-  applications such as multi-core processor systems or secure/non-secure partitions.
-- **PoC Tools** - command line tools and utilities that implement the overall concepts and are intended to be used for
-  open-source projects or even integrated into commercial software tools.
-- **Process Improvements** - documentation and tools that help the software community to streamline and secure the
-  software delivery to the user base.
-- **Resource Management** - describes the data models used to manage and organized software packs and application
-  projects.
-
-These Issues are tracked inside the [project board](https://github.com/Open-CMSIS-Pack/Open-CMSIS-Pack/projects/1)
-
-### Issues, Labels
-
-Please feel free to raise an [issue on GitHub](https://github.com/Open-CMSIS-Pack/Open-CMSIS-Pack/issues)
-to report misbehavior (i.e. bugs)
-
-Issues are your best way to interact directly with the maintenance team and the community.
-We encourage you to append implementation suggestions as this helps to decrease the
-workload of the very limited maintenance team.
-
-We shall be monitoring and responding to issues as best we can.
-Please attempt to avoid filing duplicates of open or closed items when possible.
-In the spirit of openness we shall be tagging issues with the following:
-
-- **bug** – We consider this issue to be a bug that shall be investigated.
-- **wontfix** - We appreciate this issue but decided not to change the current behavior.
-- **out-of-scope** - We consider this issue loosely related to CMSIS. It might be implemented outside of CMSIS. Let us
-  know about your work.
-- **question** – We have further questions about this issue. Please review and provide feedback.
-- **documentation** - This issue is a documentation flaw that shall be improved in the future.
-- **DONE** - We consider this issue as resolved - please review and close it. In case of no further activity, these
-  issues shall be closed after a week.
-- **duplicate** - This issue is already addressed elsewhere, see a comment with provided references.