├── .gitignore ├── CODE_OF_CONDUCT.md ├── GOVERNANCE.md ├── LICENSE └── README.md /.gitignore: -------------------------------------------------------------------------------- 1 | book/* 2 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 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 | ## Enforcement 36 | 37 | Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at aturon@mozilla.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. 38 | 39 | 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 project's leadership. 40 | 41 | ## Attribution 42 | 43 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version] 44 | 45 | [homepage]: http://contributor-covenant.org 46 | [version]: http://contributor-covenant.org/version/1/4/ 47 | -------------------------------------------------------------------------------- /GOVERNANCE.md: -------------------------------------------------------------------------------- 1 | # Governance of the `rustwasm` Organization 2 | 3 | This document describes the lightweight governance structure used in the 4 | [`rustwasm` organization][org]. 5 | 6 | - [Code of Conduct](#code-of-conduct) 7 | - [Membership](#membership) 8 | - [Teams](#teams) 9 | - [`@rustwasm/core`](#rustwasmcore) 10 | - [`@rustwasm/book`](#rustwasmbook) 11 | - [Creating New Teams](#creating-new-teams) 12 | - [Repositories](#repositories) 13 | - [Adding New Repositories to `rustwasm`](#adding-new-repositories-to-rustwasm) 14 | 15 | ## Code of Conduct 16 | 17 | We abide by the [Rust Code of Conduct][conduct] and ask that you do as well. 18 | 19 | ## Membership 20 | 21 | Membership into the `rustwasm` GitHub organization is given to anyone who is 22 | involved in Rust and WebAssembly development or otherwise contributing to the 23 | `rustwasm/*` repositories. 24 | 25 | Does that describe you or someone you know? Request membership or nominate 26 | someone for membership by contacting anyone in the [`@rustwasm/core` 27 | team][core-team]. We welcome you with open arms! 28 | 29 | Note that membership alone does not grant commit access to all of the 30 | repositories in the organization. Commit access is managed by a combination of 31 | the `@rustwasm/*` team membership and on a per-repository basis. 32 | 33 | ## Teams 34 | 35 | Teams make design, architectural, and new-membership decisions for their 36 | relevant domains and repositories by consensus. If consensus can't be made, then 37 | the `@rustwasm/core` team may act as a tie-breaker. 38 | 39 | ### [`@rustwasm/core`][core-team] 40 | 41 | The core team manages the vision and navigates the future for the overall 42 | `rustwasm` organization. 43 | 44 | ### [`@rustwasm/wasm-pack`][wasmpack-team] 45 | 46 | The `wasm-pack` team is made up of frequent contributors to `wasm-pack`. It 47 | is led by [ashleygwilliams] and [drager]. 48 | 49 | [wasmpack-team]: https://github.com/orgs/rustwasm/teams/wasm-pack 50 | [ashleygwilliams]: https://github.com/ashleygwilliams 51 | [drager]: https://github.com/drager 52 | 53 | ### Creating New Teams 54 | 55 | The [`@rustwasm/core` team][core-team] decides when and whether to create new 56 | teams and which `rustwasm/*` repositories are within the domain of the new team. 57 | 58 | ## Repositories 59 | 60 | Unless otherwise noted, each `rustwasm/*` repository has the following general 61 | policies: 62 | 63 | * All pull requests must be reviewed and approved of by at least one relevant 64 | team member or repository collaborator before merging. 65 | 66 | * Larger, more nuanced decisions about design, architecture, breaking changes, 67 | trade offs, etc are made by the relevant team and/or repository collaborators 68 | consensus. In other words, decisions on things that aren't straightforward 69 | improvements to or bug fixes for things that already exist in the project. 70 | 71 | * If you make two or three significant contributions to a repository, you should 72 | seriously consider requesting collaborator status! 73 | 74 | * On the flip side: if you are a collaborator on a `rustwasm/*` repository and 75 | notice that someone has made two or three significant contributions to it, you 76 | should seriously consider nominating them for collaborator status! 77 | 78 | ### Adding New Repositories to `rustwasm` 79 | 80 | The [`@rustwasm/core` team][core-team] decides whether a repository should be 81 | included in the `rustwasm` organization and which if any teams should have 82 | commit access. 83 | 84 | [org]: https://github.com/rustwasm 85 | [conduct]: https://www.rust-lang.org/en-US/conduct.html 86 | [core-team]: https://github.com/orgs/rustwasm/teams/core/members 87 | [book-team]: https://github.com/orgs/rustwasm/teams/book/members 88 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) 2018 Aaron Turon 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE. 22 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 |
2 | 3 |

Rust + WebAssembly = 💖

4 | 5 | A point of coordination for the Rust and WebAssembly Working Group 6 | 7 |

8 | Get Involved 9 |

10 | 11 | Built with 🦀🕸 by The Rust and WebAssembly Working Group 12 |
13 | 14 | ## About 15 | 16 | This repository is a simple, organic means of coordinating work on using Rust 17 | and WebAssembly together. 18 | 19 | ## Get Involved! 20 | 21 | Get involved with the Rust and WebAssembly community in just **three easy 22 | steps!** 23 | 24 | ### 1. Join our Chat 25 | 26 | Join the [Rust project's Discord server][rust-discord] and chat with the Rust and WebAssembly community in the `#wg-wasm` channel. 27 | 28 | Say "hello" and introduce yourself! 29 | 30 | ### 2. Do some Rust and WebAssembly Yourself 31 | 32 | Read our short [Rust and WebAssembly book][book], complete its [tutorial][], and 33 | compile some Rust into WebAssembly. If you run into a paper cut or roadblock, 34 | [let us know by filing an issue!][file-issue-book] 35 | 36 | ### 3. Join the Rust and WebAssembly Working Group 37 | 38 | We meet on [Zoom](https://zoom.us/) every other week to track progress, give status 39 | updates, and discuss issues. We coordinate meetings with [issues labeled 40 | "meeting" in the `rustwasm/team` repository][meetings]. 41 | 42 | First, get your feet wet by tackling one of these issues: 43 | 44 | * [Issues labeled "good first issue" in the `rustwasm/*` repositories][good-first-issue] 45 | 46 | * [Issues labeled "help wanted" in the `rustwasm/*` repositories.][help-wanted] 47 | 48 | Next, take a look at [our 2019 roadmap][roadmap] to get a grasp on our goals for 49 | the year, and see where you might be able to lend a hand. Unsure how to help 50 | with a project or who to reach out to for a specific project? Ask in [our 51 | chat][wasm-discord] and someone will point you in the right direction :) 52 | 53 | Finally, if you've gotten this far, see [`GOVERNANCE.md#membership`][membership] 54 | for information on becoming an official member of the working group! 55 | 56 | [help-wanted]: https://github.com/search?q=is%3Aopen+is%3Aissue+user%3Arustwasm+archived%3Afalse+label%3A%22help+wanted%22 57 | [good-first-issue]: https://github.com/search?q=is%3Aopen+is%3Aissue+user%3Arustwasm+archived%3Afalse+label%3A%22good+first+issue%22 58 | [meetings]: https://github.com/issues?utf8=%E2%9C%93&q=user%3Arustwasm+label%3Ameeting+ 59 | [membership]: https://github.com/rustwasm/team/blob/master/GOVERNANCE.md#membership 60 | [book]: https://rustwasm.github.io/book 61 | [tutorial]: https://rustwasm.github.io/book/game-of-life/introduction.html 62 | [irc]: irc://irc.mozilla.org#rust-wasm 63 | [rust-discord]: https://discordapp.com/invite/rust-lang 64 | [wasm-discord]: https://discordapp.com/channels/442252698964721669/443151097398296587 65 | [irc-web-client]: https://client00.chat.mibbit.com/?channel=%23rust-wasm&server=irc.mozilla.org 66 | [file-issue]: https://github.com/rustwasm/team/issues/new 67 | [file-issue-book]: https://github.com/rustwasm/book/issues/new 68 | [roadmap]: https://rustwasm.github.io/rfcs/007-2019-roadmap.html 69 | --------------------------------------------------------------------------------