Miscellaneous updates before public release (#87)

This pull request introduces several updates focused on project
ownership, licensing, and contribution guidelines. The main changes
clarify code ownership, update the project's copyright, and reorganize
the contributing documentation for better clarity.

**Project Ownership and Licensing:**

* Added a new `CODEOWNERS` file specifying maintainers and requiring
auditor approval for changes in the `supply-chain` folder, which relates
to cargo vet.
* Updated the copyright in the `LICENSE` file from "OEMWCSE" to "Open
Device Partnership".

**Documentation and Contribution Guidelines:**

* Reorganized the `CONTRIBUTING.md` file by restructuring headings,
clarifying commit message and PR etiquette sections, and removing
redundant or outdated guidelines for branch naming, use of `unsafe`, and
commit history.

**Minor Cleanups:**

* Removed an unnecessary trailing blank line from the end of the
`LICENSE` file.

1 files changed, 3 insertions, 23 deletions

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 7c8289a58..f10eb5be9 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -14,35 +14,15 @@ you have the right to submit those contributions under those terms.
 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.
 
-# Contribution Guideline
+## Commit Message
 
-* For any new HAL driver added, please add corresponding test in the examples
-* Format the code with `cargo fmt`. Or better yet, enable format on save in your IDE for rust source files.
 * Use meaningful commit messages. See [this blogpost](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html)
 
-# PR Etiquette
+## 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.
 
-# Careful Use of `Unsafe`
-
-Working with embedded, using of `unsafe` is a necessity. However, please wrap unsafe code with safe interfaces to prevent `unsafe` keyword being sprinkled everywhere.
-
-# RFC Draft PR
-
-If you want feedback on your design or HAL driver early, please create a draft PR with title prefix `RFC:`.
-
-# Branch Naming Scheme
-
-For now, we're not using forks. Eventually a personal fork will be required for any PRs to limit the amount of people with merge access to the main branch. Until that happens, please use meaningful branch names like this `user_alias/feature` and avoid sending PRs from branches containing prefixes such as "wip", "test", etc. Prior to sending a PR, please rename the branch.
-
-# Clean Commit History
-
-We disabled squashing of commit and would like to maintain a clean commit history. So please reorganize your commits with the following items:
-  * Each commit builds successfully without warning from `rustc` or `clippy`
-  * Miscellaneous commits to fix typos + formatting are squashed
-
-# Regressions
+## 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.