Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update CONTRIBUTING with MCCA requirements #361

Merged
merged 3 commits into from
Mar 11, 2021
Merged

Update CONTRIBUTING with MCCA requirements #361

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
894a536
Update CONTRIBUTING with MCCA requirements
MikeOpenHWGroup Mar 8, 2021
6490e55
Add cycle timer to VPs supported by mm_ram
MikeOpenHWGroup Mar 8, 2021
7bf7ab2
Roll back sim_test.rst
MikeOpenHWGroup Mar 8, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 20 additions & 5 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,10 +1,25 @@
<!--- SPDX-License-Identifier: Apache-2.0 WITH SHL-2.0 --->
# Contributing
Contributors are required to be a [member](https://www.openhwgroup.org/membership/) of the OpenHW Group. New members are always welcome.
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.
<br><br>
All pull-requests to OpenHW Group git repositories must be signed-off using the
`--signoff` (or `-s`) option to the git commit command (see below).

## The Mechanics
1. [Fork](https://help.github.com/articles/fork-a-repo/) the [core-v-docs](https://github.com/openhwgroup/core-v-docs) repository
2. Clone repository: `git clone https://github.com/[your_github_username]/core-v-docs`
3. Create your feature branch: `git checkout -b my-new-feature`
4. Commit your changes: `git commit -m 'Add some feature' -s`
5. Push feature branch: `git push origin my-new-feature`
6. Submit a pull request
3. 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.
4. Commit your changes: `git commit -m 'Add some feature' --signoff`<br>...remember to **--signoff**. We cannot accept your pull-request without it.
5. Push feature branch: `git push origin <my_branch>`
6. Submit a [pull request](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork).