# `🌻 opensource-template`
**Template for creating new open source repositories that follow the Embark open source guidelines**
[](https://embark.dev)
[](https://discord.gg/dAuKfZS)
[](https://crates.io/crates/rust-gpu)
[](https://docs.rs/rust-gpu)
[](https://embarkstudios.github.io/presser/presser/index.html)
[](https://deps.rs/repo/github/EmbarkStudios/rust-gpu)
[](https://github.com/EmbarkStudios/physx-rs/actions)
TEMPLATE INSTRUCTIONS
- Create a new repository under EmbarkStudios using this template.
- Title: Change the first line of this README to the name of your project, and replace the sunflower with an emoji that represents your project. 🚨 Your emoji selection is critical.
- Badges: In the badges section above, change the repo name in each URL. If you are creating something other than a Rust crate, remove the crates.io and docs badges (and feel free to add more appropriate ones for your language).
- CI: In
./github/workflows/renamerust-ci.yml(or the appropriate config for your language) toci.yml. And go over it and adapt it to work for your project- If you aren't using or customized the CI workflow, also see the TODO in
.mergify.yml - If you want to use the automatic rustdoc publishing to github pages for git main, see
rustdoc-pages.yml
- If you aren't using or customized the CI workflow, also see the TODO in
- Issue & PR Templates: Review the files in
.github/ISSUE_TEMPLATEand.github/pull_request_template. Adapt them to suit your needs, removing or re-wording any sections that don't make sense for your use case. - CHANGELOG.md: Change the
$REPO_NAMEin the links at the bottom to the name of the repository, and replace the example template lines with the actual notes for the repository/crate. - release.toml: in
./release.tomlchange the$REPO_NAMEto the name of the repository - Cleanup: Remove this section of the README and any unused files (such as configs for other languages) from the repo.
Contributing
We welcome community contributions to this project.
Please read our Contributor Guide for more information on how to get started. Please also read our Contributor Terms before you make any contributions.
Any contribution intentionally submitted for inclusion in an Embark Studios project, shall comply with the Rust standard licensing model (MIT OR Apache 2.0) and therefore be dual licensed as described below, without any additional terms or conditions:
License
This contribution is dual licensed under EITHER OF
- Apache License, Version 2.0, (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
- MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT)
at your option.
For clarity, "your" refers to Embark or any other licensee/user of the contribution.