Skip to content

Commit 1c79103

Browse files
yoshuawuytsyoshuawuyts
committed
get ready to submit to the BA
1 parent 4c5701f commit 1c79103

File tree

3 files changed

+363
-1
lines changed

3 files changed

+363
-1
lines changed

‎CODE_OF_CONDUCT.md

Lines changed: 143 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,143 @@
1+
# Bytecode Alliance Organizational Code of Conduct (OCoC)
2+
3+
*Note*: this Code of Conduct pertains to organizations' behavior. Please also see the [Individual Code of Conduct](CODE_OF_CONDUCT.md).
4+
5+
## Preamble
6+
7+
The Bytecode Alliance (BA) welcomes involvement from organizations,
8+
including commercial organizations. This document is an
9+
*organizational* code of conduct, intended particularly to provide
10+
guidance to commercial organizations. It is distinct from the
11+
[Individual Code of Conduct (ICoC)](CODE_OF_CONDUCT.md), and does not
12+
replace the ICoC. This OCoC applies to any group of people acting in
13+
concert as a BA member or as a participant in BA activities, whether
14+
or not that group is formally incorporated in some jurisdiction.
15+
16+
The code of conduct described below is not a set of rigid rules, and
17+
we did not write it to encompass every conceivable scenario that might
18+
arise. For example, it is theoretically possible there would be times
19+
when asserting patents is in the best interest of the BA community as
20+
a whole. In such instances, consult with the BA, strive for
21+
consensus, and interpret these rules with an intent that is generous
22+
to the community the BA serves.
23+
24+
While we may revise these guidelines from time to time based on
25+
real-world experience, overall they are based on a simple principle:
26+
27+
*Bytecode Alliance members should observe the distinction between
28+
public community functions and private functions — especially
29+
commercial ones — and should ensure that the latter support, or at
30+
least do not harm, the former.*
31+
32+
## Guidelines
33+
34+
* **Do not cause confusion about Wasm standards or interoperability.**
35+
36+
Having an interoperable WebAssembly core is a high priority for
37+
the BA, and members should strive to preserve that core. It is fine
38+
to develop additional non-standard features or APIs, but they
39+
should always be clearly distinguished from the core interoperable
40+
Wasm.
41+
42+
Treat the WebAssembly name and any BA-associated names with
43+
respect, and follow BA trademark and branding guidelines. If you
44+
distribute a customized version of software originally produced by
45+
the BA, or if you build a product or service using BA-derived
46+
software, use names that clearly distinguish your work from the
47+
original. (You should still provide proper attribution to the
48+
original, of course, wherever such attribution would normally be
49+
given.)
50+
51+
Further, do not use the WebAssembly name or BA-associated names in
52+
other public namespaces in ways that could cause confusion, e.g.,
53+
in company names, names of commercial service offerings, domain
54+
names, publicly-visible social media accounts or online service
55+
accounts, etc. It may sometimes be reasonable, however, to
56+
register such a name in a new namespace and then immediately donate
57+
control of that account to the BA, because that would help the project
58+
maintain its identity.
59+
60+
For further guidance, see the BA Trademark and Branding Policy
61+
[TODO: create policy, then insert link].
62+
63+
* **Do not restrict contributors.** If your company requires
64+
employees or contractors to sign non-compete agreements, those
65+
agreements must not prevent people from participating in the BA or
66+
contributing to related projects.
67+
68+
This does not mean that all non-compete agreements are incompatible
69+
with this code of conduct. For example, a company may restrict an
70+
employee's ability to solicit the company's customers. However, an
71+
agreement must not block any form of technical or social
72+
participation in BA activities, including but not limited to the
73+
implementation of particular features.
74+
75+
The accumulation of experience and expertise in individual persons,
76+
who are ultimately free to direct their energy and attention as
77+
they decide, is one of the most important drivers of progress in
78+
open source projects. A company that limits this freedom may hinder
79+
the success of the BA's efforts.
80+
81+
* **Do not use patents as offensive weapons.** If any BA participant
82+
prevents the adoption or development of BA technologies by
83+
asserting its patents, that undermines the purpose of the
84+
coalition. The collaboration fostered by the BA cannot include
85+
members who act to undermine its work.
86+
87+
* **Practice responsible disclosure** for security vulnerabilities.
88+
Use designated, non-public reporting channels to disclose technical
89+
vulnerabilities, and give the project a reasonable period to
90+
respond, remediate, and patch. [TODO: optionally include the
91+
security vulnerability reporting URL here.]
92+
93+
Vulnerability reporters may patch their company's own offerings, as
94+
long as that patching does not significantly delay the reporting of
95+
the vulnerability. Vulnerability information should never be used
96+
for unilateral commercial advantage. Vendors may legitimately
97+
compete on the speed and reliability with which they deploy
98+
security fixes, but withholding vulnerability information damages
99+
everyone in the long run by risking harm to the BA project's
100+
reputation and to the security of all users.
101+
102+
* **Respect the letter and spirit of open source practice.** While
103+
there is not space to list here all possible aspects of standard
104+
open source practice, some examples will help show what we mean:
105+
106+
* Abide by all applicable open source license terms. Do not engage
107+
in copyright violation or misattribution of any kind.
108+
109+
* Do not claim others' ideas or designs as your own.
110+
111+
* When others engage in publicly visible work (e.g., an upcoming
112+
demo that is coordinated in a public issue tracker), do not
113+
unilaterally announce early releases or early demonstrations of
114+
that work ahead of their schedule in order to secure private
115+
advantage (such as marketplace advantage) for yourself.
116+
117+
The BA reserves the right to determine what constitutes good open
118+
source practices and to take action as it deems appropriate to
119+
encourage, and if necessary enforce, such practices.
120+
121+
## Enforcement
122+
123+
Instances of organizational behavior in violation of the OCoC may
124+
be reported by contacting the Bytecode Alliance CoC team at
125+
[[email protected]](mailto:[email protected]). The
126+
CoC team will review and investigate all complaints, and will respond
127+
in a way that it deems appropriate to the circumstances. The CoC team
128+
is obligated to maintain confidentiality with regard to the reporter of
129+
an incident. Further details of specific enforcement policies may be
130+
posted separately.
131+
132+
When the BA deems an organization in violation of this OCoC, the BA
133+
will, at its sole discretion, determine what action to take. The BA
134+
will decide what type, degree, and duration of corrective action is
135+
needed, if any, before a violating organization can be considered for
136+
membership (if it was not already a member) or can have its membership
137+
reinstated (if it was a member and the BA canceled its membership due
138+
to the violation).
139+
140+
In practice, the BA's first approach will be to start a conversation,
141+
with punitive enforcement used only as a last resort. Violations
142+
often turn out to be unintentional and swiftly correctable with all
143+
parties acting in good faith.

‎LICENSE

Lines changed: 219 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,219 @@
1+
2+
Apache License
3+
Version 2.0, January 2004
4+
http://www.apache.org/licenses/
5+
6+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
7+
8+
1. Definitions.
9+
10+
"License" shall mean the terms and conditions for use, reproduction,
11+
and distribution as defined by Sections 1 through 9 of this document.
12+
13+
"Licensor" shall mean the copyright owner or entity authorized by
14+
the copyright owner that is granting the License.
15+
16+
"Legal Entity" shall mean the union of the acting entity and all
17+
other entities that control, are controlled by, or are under common
18+
control with that entity. For the purposes of this definition,
19+
"control" means (i) the power, direct or indirect, to cause the
20+
direction or management of such entity, whether by contract or
21+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
22+
outstanding shares, or (iii) beneficial ownership of such entity.
23+
24+
"You" (or "Your") shall mean an individual or Legal Entity
25+
exercising permissions granted by this License.
26+
27+
"Source" form shall mean the preferred form for making modifications,
28+
including but not limited to software source code, documentation
29+
source, and configuration files.
30+
31+
"Object" form shall mean any form resulting from mechanical
32+
transformation or translation of a Source form, including but
33+
not limited to compiled object code, generated documentation,
34+
and conversions to other media types.
35+
36+
"Work" shall mean the work of authorship, whether in Source or
37+
Object form, made available under the License, as indicated by a
38+
copyright notice that is included in or attached to the work
39+
(an example is provided in the Appendix below).
40+
41+
"Derivative Works" shall mean any work, whether in Source or Object
42+
form, that is based on (or derived from) the Work and for which the
43+
editorial revisions, annotations, elaborations, or other modifications
44+
represent, as a whole, an original work of authorship. For the purposes
45+
of this License, Derivative Works shall not include works that remain
46+
separable from, or merely link (or bind by name) to the interfaces of,
47+
the Work and Derivative Works thereof.
48+
49+
"Contribution" shall mean any work of authorship, including
50+
the original version of the Work and any modifications or additions
51+
to that Work or Derivative Works thereof, that is intentionally
52+
submitted to Licensor for inclusion in the Work by the copyright owner
53+
or by an individual or Legal Entity authorized to submit on behalf of
54+
the copyright owner. For the purposes of this definition, "submitted"
55+
means any form of electronic, verbal, or written communication sent
56+
to the Licensor or its representatives, including but not limited to
57+
communication on electronic mailing lists, source code control systems,
58+
and issue tracking systems that are managed by, or on behalf of, the
59+
Licensor for the purpose of discussing and improving the Work, but
60+
excluding communication that is conspicuously marked or otherwise
61+
designated in writing by the copyright owner as "Not a Contribution."
62+
63+
"Contributor" shall mean Licensor and any individual or Legal Entity
64+
on behalf of whom a Contribution has been received by Licensor and
65+
subsequently incorporated within the Work.
66+
67+
2. Grant of Copyright License. Subject to the terms and conditions of
68+
this License, each Contributor hereby grants to You a perpetual,
69+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
70+
copyright license to reproduce, prepare Derivative Works of,
71+
publicly display, publicly perform, sublicense, and distribute the
72+
Work and such Derivative Works in Source or Object form.
73+
74+
3. Grant of Patent License. Subject to the terms and conditions of
75+
this License, each Contributor hereby grants to You a perpetual,
76+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
77+
(except as stated in this section) patent license to make, have made,
78+
use, offer to sell, sell, import, and otherwise transfer the Work,
79+
where such license applies only to those patent claims licensable
80+
by such Contributor that are necessarily infringed by their
81+
Contribution(s) alone or by combination of their Contribution(s)
82+
with the Work to which such Contribution(s) was submitted. If You
83+
institute patent litigation against any entity (including a
84+
cross-claim or counterclaim in a lawsuit) alleging that the Work
85+
or a Contribution incorporated within the Work constitutes direct
86+
or contributory patent infringement, then any patent licenses
87+
granted to You under this License for that Work shall terminate
88+
as of the date such litigation is filed.
89+
90+
4. Redistribution. You may reproduce and distribute copies of the
91+
Work or Derivative Works thereof in any medium, with or without
92+
modifications, and in Source or Object form, provided that You
93+
meet the following conditions:
94+
95+
(a) You must give any other recipients of the Work or
96+
Derivative Works a copy of this License; and
97+
98+
(b) You must cause any modified files to carry prominent notices
99+
stating that You changed the files; and
100+
101+
(c) You must retain, in the Source form of any Derivative Works
102+
that You distribute, all copyright, patent, trademark, and
103+
attribution notices from the Source form of the Work,
104+
excluding those notices that do not pertain to any part of
105+
the Derivative Works; and
106+
107+
(d) If the Work includes a "NOTICE" text file as part of its
108+
distribution, then any Derivative Works that You distribute must
109+
include a readable copy of the attribution notices contained
110+
within such NOTICE file, excluding those notices that do not
111+
pertain to any part of the Derivative Works, in at least one
112+
of the following places: within a NOTICE text file distributed
113+
as part of the Derivative Works; within the Source form or
114+
documentation, if provided along with the Derivative Works; or,
115+
within a display generated by the Derivative Works, if and
116+
wherever such third-party notices normally appear. The contents
117+
of the NOTICE file are for informational purposes only and
118+
do not modify the License. You may add Your own attribution
119+
notices within Derivative Works that You distribute, alongside
120+
or as an addendum to the NOTICE text from the Work, provided
121+
that such additional attribution notices cannot be construed
122+
as modifying the License.
123+
124+
You may add Your own copyright statement to Your modifications and
125+
may provide additional or different license terms and conditions
126+
for use, reproduction, or distribution of Your modifications, or
127+
for any such Derivative Works as a whole, provided Your use,
128+
reproduction, and distribution of the Work otherwise complies with
129+
the conditions stated in this License.
130+
131+
5. Submission of Contributions. Unless You explicitly state otherwise,
132+
any Contribution intentionally submitted for inclusion in the Work
133+
by You to the Licensor shall be under the terms and conditions of
134+
this License, without any additional terms or conditions.
135+
Notwithstanding the above, nothing herein shall supersede or modify
136+
the terms of any separate license agreement you may have executed
137+
with Licensor regarding such Contributions.
138+
139+
6. Trademarks. This License does not grant permission to use the trade
140+
names, trademarks, service marks, or product names of the Licensor,
141+
except as required for reasonable and customary use in describing the
142+
origin of the Work and reproducing the content of the NOTICE file.
143+
144+
7. Disclaimer of Warranty. Unless required by applicable law or
145+
agreed to in writing, Licensor provides the Work (and each
146+
Contributor provides its Contributions) on an "AS IS" BASIS,
147+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
148+
implied, including, without limitation, any warranties or conditions
149+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
150+
PARTICULAR PURPOSE. You are solely responsible for determining the
151+
appropriateness of using or redistributing the Work and assume any
152+
risks associated with Your exercise of permissions under this License.
153+
154+
8. Limitation of Liability. In no event and under no legal theory,
155+
whether in tort (including negligence), contract, or otherwise,
156+
unless required by applicable law (such as deliberate and grossly
157+
negligent acts) or agreed to in writing, shall any Contributor be
158+
liable to You for damages, including any direct, indirect, special,
159+
incidental, or consequential damages of any character arising as a
160+
result of this License or out of the use or inability to use the
161+
Work (including but not limited to damages for loss of goodwill,
162+
work stoppage, computer failure or malfunction, or any and all
163+
other commercial damages or losses), even if such Contributor
164+
has been advised of the possibility of such damages.
165+
166+
9. Accepting Warranty or Additional Liability. While redistributing
167+
the Work or Derivative Works thereof, You may choose to offer,
168+
and charge a fee for, acceptance of support, warranty, indemnity,
169+
or other liability obligations and/or rights consistent with this
170+
License. However, in accepting such obligations, You may act only
171+
on Your own behalf and on Your sole responsibility, not on behalf
172+
of any other Contributor, and only if You agree to indemnify,
173+
defend, and hold each Contributor harmless for any liability
174+
incurred by, or claims asserted against, such Contributor by reason
175+
of your accepting any such warranty or additional liability.
176+
177+
END OF TERMS AND CONDITIONS
178+
179+
APPENDIX: How to apply the Apache License to your work.
180+
181+
To apply the Apache License to your work, attach the following
182+
boilerplate notice, with the fields enclosed by brackets "[]"
183+
replaced with your own identifying information. (Don't include
184+
the brackets!) The text should be enclosed in the appropriate
185+
comment syntax for the file format. We also recommend that a
186+
file or class name and description of purpose be included on the
187+
same "printed page" as the copyright notice for easier
188+
identification within third-party archives.
189+
190+
Copyright [yyyy] [name of copyright owner]
191+
192+
Licensed under the Apache License, Version 2.0 (the "License");
193+
you may not use this file except in compliance with the License.
194+
You may obtain a copy of the License at
195+
196+
http://www.apache.org/licenses/LICENSE-2.0
197+
198+
Unless required by applicable law or agreed to in writing, software
199+
distributed under the License is distributed on an "AS IS" BASIS,
200+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
201+
See the License for the specific language governing permissions and
202+
limitations under the License.
203+
204+
205+
--- LLVM Exceptions to the Apache 2.0 License ----
206+
207+
As an exception, if, as a result of your compiling your source code, portions
208+
of this Software are embedded into an Object form of such source code, you
209+
may redistribute such embedded portions in such Object form without complying
210+
with the conditions of Sections 4(a), 4(b) and 4(d) of the License.
211+
212+
In addition, if you combine or link compiled forms of this Software with
213+
software that is licensed under the GPLv2 ("Combined Software") and if a
214+
court of competent jurisdiction determines that the patent provision (Section
215+
3), the indemnity provision (Section 9) or other Section of the License
216+
conflicts with the conditions of the GPLv2, you may retroactively and
217+
prospectively choose to deem waived or otherwise exclude such Section(s) of
218+
the License, but only in their entirety and only with respect to the Combined
219+
Software.

‎README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -60,6 +60,6 @@ on the pull + serve pattern we've shown here.
6060

6161
## License
6262

63-
MIT OR Apache-2.0
63+
Apache-2.0 with LLVM Exception
6464

6565
[cargo-component]: https://github.com/bytecodealliance/cargo-component

0 commit comments

Comments
 (0)