Documentation Update For WAMR's New Home

CODE_OF_CONDUCT.md

@@ -1,7 +1,5 @@
 # Contributor Covenant Code of Conduct
 
-*Note*: this Code of Conduct pertains to individuals' behavior. Please also see the [Organizational Code of Conduct][OCoC].
-
 ## Our Pledge
 
 In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
@@ -36,14 +34,12 @@ This Code of Conduct applies both within project spaces and in public spaces whe
 
 ## Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the Bytecode Alliance CoC team at [report@bytecodealliance.org](mailto:report@bytecodealliance.org). The CoC team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The CoC team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the WAMR Core team at [wamr-core@googlegroups.com](mailto:wamr-core@googlegroups.com). The core team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The core team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
 
-Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the Bytecode Alliance's leadership.
 
 ## Attribution
 
 This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
 
-[OCoC]: ORG_CODE_OF_CONDUCT.md
 [homepage]: https://www.contributor-covenant.org
 [version]: https://www.contributor-covenant.org/version/1/4/

CONTRIBUTING.md

@@ -40,4 +40,4 @@ We use GitHub issues to track public bugs. Report a bug by [open a new issue](ht
 Code of Conduct
 ===============
 
-WAMR is a [Bytecode Alliance](https://bytecodealliance.org/) project, and follows the Bytecode Alliance's [Code of Conduct](CODE_OF_CONDUCT.md) and [Organizational Code of Conduct](ORG_CODE_OF_CONDUCT.md).
+WAMR follows its own [Code of conduct](CODE_OF_CONDUCT.md). 

README.md

@@ -1,11 +1,7 @@
 # WebAssembly Micro Runtime
 
 
-**A [Bytecode Alliance][BA] project**
-
-[BA]: https://bytecodealliance.org/
-
-**[Guide](https://wamr.gitbook.io/)**  **[Website](https://bytecodealliance.github.io/wamr.dev)**  **[Chat](https://bytecodealliance.zulipchat.com/#narrow/stream/290350-wamr)**
+**[Guide](https://wamr.gitbook.io/)**  **[Website](https://bytecodealliance.github.io/wamr.dev)**
 
 [Build WAMR](./doc/build_wamr.md) | [Build AOT Compiler](./wamr-compiler/README.md) | [Embed WAMR](./doc/embed_wamr.md) | [Export Native API](./doc/export_native_api.md) | [Build Wasm Apps](./doc/build_wasm_app.md) | [Samples](./samples/README.md)
 

SECURITY.md

@@ -1,3 +1,42 @@
 # Security Policy
 
-Please refer to the [Bytecode Alliance security policy](https://bytecodealliance.org/security) for details on how to report security issues in WebAssembly Micro Runtime, our disclosure policy, and how to receive notifications about security issues.
+## Reporting a security bug in a the WAMR Project
+Security is a top priority for the WAMR Project. As such, we take all reports of suspected security vulnerabilities seriously, and have a number of ways to report them.
+
+For suspected vulnerabilities in a specific project, prefer to report the issue using GitHub’s [private vulnerability reporting facilities](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability). Maintainers will then work with you to resolve the issue.
+
+If you think that that channel isn’t right for reporting your specific issue, you can also send email to the WAMR core team directly via [wamr-core@googlegroups.com](mailto:wamr-core@googlegroups.com). We will then acknowledge receipt of your report and prioritize initial analysis of severity.
+
+The security team may work in private with individuals from the WAMR Core team, supporting WAMR organizations, core contributors to the affected project, and, where applicable, affected downstream projects and products.
+
+After the initial reply to your report, the core team will endeavor to keep you informed of the progress being made towards a fix and full announcement, and may ask for additional information or guidance surrounding the reported issue.
+
+If you have not received a reply to your report within two days, please reach out again via our email address : [wamr-core@googlegroups.com](mailto:wamr-core@googlegroups.com)
+
+
+## Preferences
+* Please provide detailed reports with reproducible steps and a clearly defined impact.
+* Submit one vulnerability per report.
+* Social engineering (e.g. phishing, vishing, smishing) is prohibited.
+
+## Disclosure Policy
+* The security report is received and is assigned a primary handler. This person will coordinate the fix and release process. The problem is confirmed and a list of all affected versions is determined. Code is audited to find any potential similar problems. Fixes are prepared for all releases which are still under maintenance. These fixes are not committed to the public repository but rather held locally pending the announcement.
+
+* A suggested embargo date for this vulnerability is chosen and a CVE (Common Vulnerabilities and Exposures (CVE®)) is requested for the vulnerability.
+
+* A prenotification may be published on the wamr-dev mailing list, providing information about affected projects, severity, and the embargo date.
+
+* On the embargo date, the wamr-dev mailing list is sent a copy of the announcement. The changes are pushed to the public repository and new builds are deployed.
+
+* Typically the embargo date will be set 72 hours from the time the CVE is issued. However, this may vary depending on the severity of the bug or difficulty in applying a fix.
+
+* This process can take some time, especially when coordination is required with maintainers of other projects. Every effort will be made to handle the bug in as timely a manner as possible; however, it’s important that we follow the release process above to ensure that the disclosure is handled in a consistent manner.
+
+* Core team members are encouraged to write a post-mortem for the WAMR blog, detailing the vulnerability and steps being taken to identify and prevent similar vulnerabilities in the future.
+
+## Receiving Security Updates
+Security notifications will be distributed our wamr-dev email list. Please do join this here:
+[https://groups.google.com/g/wamr-dev](https://groups.google.com/g/wamr-dev).
+
+
+