The Rust and WebAssembly RFCs
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
text
.gitignore
.travis.yml
000-template.md template: Add a stakeholders and outreach section Jul 9, 2018
LICENSE-APACHE
LICENSE-MIT
README.md
book.toml
generate-book.sh Initial commit! Jun 28, 2018

README.md

Rust and WebAssembly RFCs

Many changes, including bug fixes and documentation improvements can be implemented and reviewed via the normal GitHub pull request workflow.

Some changes though are "substantial", and we ask that these be put through a bit of a design process and produce a consensus among the Rust and WebAssembly community.

The "RFC" (request for comments) process is intended to provide a consistent and controlled path for substantial changes and additions to enter the Rust and WebAssembly ecosystem, so that all stakeholders can be confident about the direction the ecosystem is evolving in.

The RFC Process

When does a change require an RFC? How does an RFC get approved or rejected? What is the RFC life cycle?

These questions are answered in RFC 001.

License

This repository is currently in the process of being licensed under either of

at your option. Some parts of the repository are already licensed according to those terms. For more see RFC 2044 and its tracking issue.

Contributions

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.