Skip to content

Commit de1762d

Browse files
authored
Merge pull request #13 from asteurer/ba-template
doc: adding relevant docs from the bytecodealliance/ba-template repo
2 parents b297fe1 + cc85a58 commit de1762d

3 files changed

Lines changed: 82 additions & 0 deletions

File tree

CODE_OF_CONDUCT.md

Lines changed: 49 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,49 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
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.
6+
7+
## Our Standards
8+
9+
Examples of behavior that contributes to creating a positive environment include:
10+
11+
* Using welcoming and inclusive language
12+
* Being respectful of differing viewpoints and experiences
13+
* Gracefully accepting constructive criticism
14+
* Focusing on what is best for the community
15+
* Showing empathy towards other community members
16+
17+
Examples of unacceptable behavior by participants include:
18+
19+
* The use of sexualized language or imagery and unwelcome sexual attention or advances
20+
* Trolling, insulting/derogatory comments, and personal or political attacks
21+
* Public or private harassment
22+
* Publishing others' private information, such as a physical or electronic address, without explicit permission
23+
* Other conduct which could reasonably be considered inappropriate in a professional setting
24+
25+
## Our Responsibilities
26+
27+
Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
28+
29+
Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
30+
31+
## Scope
32+
33+
This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
34+
35+
## Code of Conduct Team
36+
37+
The Organization’s Code of Conduct Team is responsible for ensuring that all Code of Conduct complaints are investigated and resolved. It consists of the members of the Technical Steering Commmittee along with the Executive Director acting as Compliance Officer. The Compliance Officer, on behalf of the Code of Conduct Team, will advise the Board of all complaints and their resolution and will report at least annually to the Board on compliance activity relating to the organizational Code of Conduct.
38+
39+
## Enforcement
40+
41+
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.
42+
43+
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.
44+
45+
## Attribution
46+
47+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at http://contributor-covenant.org/version/1/4.
48+
49+
[homepage]: https://www.contributor-covenant.org

CONTRIBUTING.md

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
# Contributing
2+
3+
This project welcomes contributions for bug fixes, documentation updates, new
4+
features, or whatever you might like. Development is done through GitHub pull
5+
requests. Feel free to reach out on the [Bytecode Alliance
6+
Zulip](https://bytecodealliance.zulipchat.com/) as well if you'd like assistance
7+
in contributing or would just like to say hi.
8+
9+
## Code of Conduct
10+
11+
This is a [Bytecode Alliance](https://bytecodealliance.org/) project, and follows the Bytecode Alliance's [Code of Conduct](CODE_OF_CONDUCT.md).
12+
13+
## License
14+
15+
This project is licensed under the Apache 2.0 license with the LLVM exception.
16+
See [LICENSE](LICENSE) for more details.
17+
18+
### Contribution
19+
20+
Unless you explicitly state otherwise, any contribution intentionally submitted
21+
for inclusion in this project by you, as defined in the Apache-2.0 license,
22+
shall be licensed as above, without any additional terms or conditions.

SECURITY.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
# Security Policy
2+
3+
Please refer to the [Bytecode Alliance security
4+
policy](https://bytecodealliance.org/security) for details on how to report
5+
security issues in componentize-go, our disclosure policy, and how to receive
6+
notifications about security issues.
7+
8+
For classification of what is and what isn't a security issue please see our
9+
[online
10+
documentation](https://docs.wasmtime.dev/security-what-is-considered-a-security-vulnerability.html)
11+
on the subject.

0 commit comments

Comments
 (0)