1 files changed, 0 insertions, 28 deletions
diff --git a/embassy-mcxa/CONTRIBUTING.md b/embassy-mcxa/CONTRIBUTING.md
deleted file mode 100644
index f10eb5be9..000000000
--- a/embassy-mcxa/CONTRIBUTING.md
+++ /dev/null
@@ -1,28 +0,0 @@
-# Contributing to Open Device Partnership
-The Open Device Partnership project welcomes your suggestions and contributions! Before opening your first issue or pull request, please review our
-[Code of Conduct](CODE_OF_CONDUCT.md) to understand how our community interacts in an inclusive and respectful manner.
-## Contribution Licensing
-Most of our code is distributed under the terms of the [MIT license](LICENSE), and when you contribute code that you wrote to our repositories,
-you agree that you are contributing under those same terms. In addition, by submitting your contributions you are indicating that
-you have the right to submit those contributions under those terms.
-## Other Contribution Information
-If you wish to contribute code or documentation authored by others, or using the terms of any other license, please indicate that clearly in your
-pull request so that the project team can discuss the situation with you.
-## Commit Message
-* Use meaningful commit messages. See [this blogpost](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html)
-## PR Etiquette
-* Create a draft PR first
-* Make sure that your branch has `.github` folder and all the code linting/sanity check workflows are passing in your draft PR before sending it out to code reviewers.
-## Regressions
-When reporting a regression, please ensure that you use `git bisect` to find the first offending commit, as that will help us finding the culprit a lot faster.

diff --git a/embassy-mcxa/CONTRIBUTING.md b/embassy-mcxa/CONTRIBUTING.md deleted file mode 100644 index f10eb5be9..000000000 --- a/embassy-mcxa/CONTRIBUTING.md +++ /dev/null
@@ -1,28 +0,0 @@
1	# Contributing to Open Device Partnership
2
3	The Open Device Partnership project welcomes your suggestions and contributions! Before opening your first issue or pull request, please review our
4	[Code of Conduct](CODE_OF_CONDUCT.md) to understand how our community interacts in an inclusive and respectful manner.
5
6	## Contribution Licensing
7
8	Most of our code is distributed under the terms of the [MIT license](LICENSE), and when you contribute code that you wrote to our repositories,
9	you agree that you are contributing under those same terms. In addition, by submitting your contributions you are indicating that
10	you have the right to submit those contributions under those terms.
11
12	## Other Contribution Information
13
14	If you wish to contribute code or documentation authored by others, or using the terms of any other license, please indicate that clearly in your
15	pull request so that the project team can discuss the situation with you.
16
17	## Commit Message
18
19	* Use meaningful commit messages. See [this blogpost](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html)
20
21	## PR Etiquette
22
23	* Create a draft PR first
24	* Make sure that your branch has `.github` folder and all the code linting/sanity check workflows are passing in your draft PR before sending it out to code reviewers.
25
26	## Regressions
27
28	When reporting a regression, please ensure that you use `git bisect` to find the first offending commit, as that will help us finding the culprit a lot faster.