You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
*Note*: this Code of Conduct pertains to individuals' behavior. Please also see the [Organizational Code of Conduct][OCoC].
6
+
# Contributor Covenant Code of Conduct
4
7
5
8
## Our Pledge
6
9
7
-
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.
10
+
In the interest of fostering an open and welcoming environment, we as
11
+
contributors and maintainers pledge to make participation in our project and
12
+
our community a harassment-free experience for everyone, regardless of age, body
13
+
size, disability, ethnicity, sex characteristics, gender identity and expression,
14
+
level of experience, education, socio-economic status, nationality, personal
15
+
appearance, race, religion, or sexual identity and orientation.
8
16
9
17
## Our Standards
10
18
11
-
Examples of behavior that contributes to creating a positive environment include:
19
+
Examples of behavior that contributes to creating a positive environment
20
+
include:
12
21
13
22
* Using welcoming and inclusive language
14
23
* Being respectful of differing viewpoints and experiences
@@ -18,32 +27,55 @@ Examples of behavior that contributes to creating a positive environment include
18
27
19
28
Examples of unacceptable behavior by participants include:
20
29
21
-
* The use of sexualized language or imagery and unwelcome sexual attention or advances
30
+
* The use of sexualized language or imagery and unwelcome sexual attention or
31
+
advances
22
32
* Trolling, insulting/derogatory comments, and personal or political attacks
23
33
* Public or private harassment
24
-
* Publishing others' private information, such as a physical or electronic address, without explicit permission
25
-
* Other conduct which could reasonably be considered inappropriate in a professional setting
34
+
* Publishing others' private information, such as a physical or electronic
35
+
address, without explicit permission
36
+
* Other conduct which could reasonably be considered inappropriate in a
37
+
professional setting
26
38
27
39
## Our Responsibilities
28
40
29
-
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.
41
+
Project maintainers are responsible for clarifying the standards of acceptable
42
+
behavior and are expected to take appropriate and fair corrective action in
43
+
response to any instances of unacceptable behavior.
30
44
31
-
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.
45
+
Project maintainers have the right and responsibility to remove, edit, or
46
+
reject comments, commits, code, wiki edits, issues, and other contributions
47
+
that are not aligned to this Code of Conduct, or to ban temporarily or
48
+
permanently any contributor for other behaviors that they deem inappropriate,
49
+
threatening, offensive, or harmful.
32
50
33
51
## Scope
34
52
35
-
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.
53
+
This Code of Conduct applies within all project spaces, and it also applies when
54
+
an individual is representing the project or its community in public spaces.
55
+
Examples of representing a project or community include using an official
56
+
project e-mail address, posting via an official social media account, or acting
57
+
as an appointed representative at an online or offline event. Representation of
58
+
a project may be further defined and clarified by project maintainers.
36
59
37
60
## Enforcement
38
61
39
-
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the Bytecode Alliance CoC team at [[email protected]](mailto:[email protected]). 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.
62
+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
complaints will be reviewed and investigated and will result in a response that
65
+
is deemed necessary and appropriate to the circumstances. The project team is
66
+
obligated to maintain confidentiality with regard to the reporter of an incident.
67
+
Further details of specific enforcement policies may be posted separately.
40
68
41
-
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.
69
+
Project maintainers who do not follow or enforce the Code of Conduct in good
70
+
faith may face temporary or permanent repercussions as determined by other
71
+
members of the project's leadership.
42
72
43
73
## Attribution
44
74
45
-
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
75
+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
76
+
available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,4 +36,5 @@ We use GitHub issues to track public bugs. Report a bug by [open a new issue](ht
36
36
Code of Conduct
37
37
===============
38
38
39
-
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).
39
+
This project is governed by the [Contributor Covenant](CODE_OF_CONDUCT.md).
40
+
All contributors and participants agree to abide by its terms.
- Supports for [WASI API](https://github.com/WebAssembly/WASI)
19
14
- Provides embedding C API
20
15
- Provides a mechanism for exporting native API's to WASM applications
21
16
- Supports the programming of firmware apps in a large range of languages (C/C++/Java/Rust/Go/TypeScript etc.)
@@ -62,7 +57,7 @@ Embed WAMR
62
57
63
58
WAMR can be built into a standalone executable which takes the WASM application file name as input, and then executes it. In some other situations, the WAMR source code is embedded the product code and built into the final product.
64
59
65
-
WAMR provides a set of C API for loading the WASM module, instantiating the module and invoking a WASM function from a native call.
60
+
WAMR provides a set of C API for loading the WASM module, instantiating the module and invoking a WASM function from a native call.
66
61
67
62
See the [doc/embed_wamr.md](./doc/embed_wamr.md) for the details.
0 commit comments