Skip to content

Commit 2e16297

Browse files
authored
Add files via upload
1 parent c604fa0 commit 2e16297

1 file changed

Lines changed: 30 additions & 0 deletions

File tree

CONTRIBUTING.md

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
# Contributing guide
2+
3+
This document serves as a checklist before contributing to this repository. It includes links to read up on if topics are unclear to you.
4+
5+
This guide mainly focuses on the proper use of Git.
6+
7+
## 1. Issues
8+
9+
STM32MPU projects do not activate "Github issues" feature for the time being. If you need to report an issue or question about this project deliverables, you can report them using [ ST Support Center ](https://my.st.com/ols#/ols/newrequest) or [ ST Community MPU Forum ](https://community.st.com/s/topic/0TO0X0000003u2AWAQ/stm32-mpus).
10+
11+
## 2. Pull Requests
12+
13+
STMicrolectronics is happy to receive contributions from the community, based on an initial Contributor License Agreement (CLA) procedure.
14+
15+
* If you are an individual writing original source code and you are sure **you own the intellectual property**, then you need to sign an Individual CLA (https://cla.st.com).
16+
* If you work for a company that wants also to allow you to contribute with your work, your company needs to provide a Corporate CLA (https://cla.st.com) mentioning your GitHub account name.
17+
* If you are not sure that a CLA (Individual or Corporate) has been signed for your GitHub account you can check here (https://cla.st.com).
18+
19+
Please note that:
20+
* The Corporate CLA will always take precedence over the Individual CLA.
21+
* One CLA submission is sufficient, for any project proposed by STMicroelectronics.
22+
23+
__How to proceed__
24+
25+
* We recommend to fork the project in your GitHub account to further develop your contribution. Please use the latest commit version.
26+
* Please, submit one Pull Request for one new feature or proposal. This will ease the analysis and final merge if accepted.
27+
28+
__Note__
29+
30+
Merge will not be done directly in GitHub but it will need first to follow internal integration process before public deliver in a standard release. The Pull request will stay open until it is merged and delivered.

0 commit comments

Comments
 (0)