Merge pull request openhwgroup#278 from MikeOpenHWGroup/quicktest

Quicktest: add info for new contributors

Author: DBees

CONTRIBUTING.md

@@ -0,0 +1,23 @@
+# Contributing
+New Contributors are always welcome!
+
+## Contributor Agreement
+Most Contributors are [members](https://www.openhwgroup.org/membership/) of the
+OpenHW Group and participate in one or more [Technical Task Groups](https://www.openhwgroup.org/working-groups/).
+Membership is strongly encouraged, but not required.
+Contributors must be covered by the terms of the [Eclipse Contributor Agreement](https://www.eclipse.org/legal/ECA.php)
+(for individuals) **or** the [Eclipse Member Committer and Contributor Agreement](https://www.eclipse.org/legal/committer_process/EclipseMemberCommitterAgreement.pdf)
+(for employees of Member companies).
+The ECA/MCCA provides a legal framework for a Contributor's technical contributions to the OpenHW Group,
+including provisions for grant of copyright license and a Developer
+Certificate of Origin on contributions merged into OpenHW Group repositories.
+
+## The Mechanics
+1. [Fork](https://help.github.com/articles/fork-a-repo/) the [core-v-mcu](https://github.com/openhwgroup/core-v-mcu) repository
+2. Clone repository: `git clone https://github.com/[your_github_username]/core-v-mcu`
+3. Checkout the correct branch reflecting the nature of your contribution.
+4. Create your feature branch: `git checkout -b <my_branch>.`<br> Please uniquify your branch name.  See the [Git Cheats](https://github.com/openhwgroup/core-v-verif/blob/master/GitCheats.md) for a useful nominclature.
+5. Commit your changes: `git commit -m 'Add some feature'
+6. Push feature branch: `git push origin <my_branch>`
+7. Submit a [pull request](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork).
+8. If known, it is advisable to select one or more appropriate reviewers for your PR.

README.md

@@ -3,11 +3,12 @@
 
 # CORE-V MCU
 
-> CORE-V MCU originated from PULPissimo \[[1](https://ieeexplore.ieee.org/abstract/document/8640145)\], \[[2](https://ieeexplore.ieee.org/document/9369856)\]. and is now a
-> stand-alone project within OpenHW Group independent from PULPIssimo.
->
-> In case you should be interested to join the project please feel free to open
-> an issue, or involve yourself in any open issues/discussions.
+CORE-V MCU originated from PULPissimo \[[1](https://ieeexplore.ieee.org/abstract/document/8640145)\], \[[2](https://ieeexplore.ieee.org/document/9369856)\],
+and is now a stand-alone project within OpenHW Group independent from PULPIssimo.
+
+In case you would be interested to join the project please feel free to open an issue, or involve yourself in any open issues/discussions.
+Contributions are always welcome!
+First time contributors should review the [Contributing](https://github.com/openhwgroup/core-v-mcu/tree/master/CONTRIBUTING.md) guide.
 
 ## Quick Start Guide
 
@@ -128,7 +129,8 @@ fusesoc --cores-root . run --target=sim --setup --build --run openhwgroup.org:sy
 
 ## Contributing: Pre-commit checks
 
-If you are submitting a pull-request, it will be subject to pre-commit checks.  The two that most likely cause problems are the Verilator Lint check and the Verible format check.
+If you are submitting a pull-request, it will be subject to pre-commit checks.
+The two that most likely cause problems are the Verilator Lint check and the Verible format check.
 
 ### Verilator model library