{"id":13423211,"url":"https://github.com/rust-embedded/wg","last_synced_at":"2025-04-08T17:16:30.002Z","repository":{"id":37615865,"uuid":"69520765","full_name":"rust-embedded/wg","owner":"rust-embedded","description":"Coordination repository of the embedded devices Working Group","archived":false,"fork":false,"pushed_at":"2024-04-09T19:24:46.000Z","size":1862,"stargazers_count":1824,"open_issues_count":88,"forks_count":90,"subscribers_count":160,"default_branch":"master","last_synced_at":"2024-04-14T10:19:43.588Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":"","language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/rust-embedded.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":"CODE_OF_CONDUCT.md","threat_model":null,"audit":null,"citation":null,"codeowners":".github/CODEOWNERS","security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null}},"created_at":"2016-09-29T02:01:26.000Z","updated_at":"2024-04-16T20:45:08.883Z","dependencies_parsed_at":"2024-04-16T20:45:07.905Z","dependency_job_id":"22d6c914-02c6-4672-95e4-49f6aa37b8ca","html_url":"https://github.com/rust-embedded/wg","commit_stats":{"total_commits":540,"total_committers":55,"mean_commits":9.818181818181818,"dds":0.6814814814814815,"last_synced_commit":"6d0613a8f3f327e586adb59bc22504babb67c7a4"},"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/rust-embedded%2Fwg","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/rust-embedded%2Fwg/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/rust-embedded%2Fwg/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/rust-embedded%2Fwg/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/rust-embedded","download_url":"https://codeload.github.com/rust-embedded/wg/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":247888559,"owners_count":21013001,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-07-31T00:00:25.098Z","updated_at":"2025-04-08T17:16:29.977Z","avatar_url":"https://github.com/rust-embedded.png","language":null,"readme":"# Embedded devices Working Group\n\n[\u003cimg src=\"assets/logo/ewg-logo-blue-white-on-transparent-256x256.png\" align=\"right\" width=\"256\"\u003e](https://github.com/rust-embedded/wg)\n\n\u003e Coordination repository of the embedded devices Working Group (WG)\n\nThis repository [issue tracker] is used by the embedded WG to coordinate efforts towards making Rust\na great choice for embedded development.\n\n[issue tracker]: https://github.com/rust-embedded/wg/issues\n\n**Want to get started with embedded development with Rust?** Check out our\n[embedded Rust book][book] and the rest of our [bookshelf].\n\nWant to stay up-to-date with community progress? Check out our [newsletter].\n\nJoin the discussion on Matrix! [#rust-embedded:matrix.org][matrix]\n\n[book]: https://docs.rust-embedded.org/book\n[bookshelf]: https://docs.rust-embedded.org\n[newsletter]: https://rust-embedded.github.io/blog/\n[matrix]: https://matrix.to/#/#rust-embedded:matrix.org\n\n## Vision\n\nWhat is it that we really want? At a broad level:\n\n- To improve the absolute quality (functionality, safety, performance) of embedded software in the\n  wild.\n- To improve the productivity of embedded software development teams, by reducing the tangible and\n  intangible costs of achieving a level of quality.\n- To improve the experience for programmers developing for embedded systems.\n- To make embedded systems programming more accessible for people that are not already embedded\n  systems developers.\n\n## What we do\n\nAt a high level we have two main tasks:\n\n*We work with the community to improve the embedded ecosystem.*\n\n- We maintain and develop core crates in the embedded ecosystem ensuring that the development\n  roadmap aligns with the needs of its users. You can find all the crates we maintain in the\n  [Organization](#organization) section.\n\n- We develop and curate resources about embedded Rust development. Check our\n  [bookshelf]!\n\n- We maintain and moderate the venues the embedded community uses to discuss. That includes this\n  coordination repository and our [Matrix room][matrix].\n\nAnd, we serve as a bridge between the [Rust teams] and the embedded community.\n\n[Rust teams]: https://www.rust-lang.org/team.html\n\n## How you can help\n\nEveryone can contribute to the embedded WG efforts! There are several ways to help out:\n\n- [Let us know] where the gaps are. If you think the language, the compiler, the tooling, the\n  documentation or the crate ecosystem is lacking some feature, information or library to build\n  embedded software let us know and we'll bring it up to the Rust teams or organize the community to\n  build the crates or tools to fill the gaps.\n\n[Let us know]: https://github.com/rust-embedded/wg/issues\n\n- Participate in [RFC (Request For Comments)][rfc] threads. We are always looking into ways to\n  improve. This may involve things from changing how we run the WG to landing major breaking changes\n  in core crates. To ensure we are *actually* making things better we need your input! That's why\n  all these changes are preceded by an \"RFC\", a discussion thread (which may or may not be backed by\n  a proper RFC document) where we evaluate the pros and cons of a proposal and explore alternatives.\n  Only after there's consensus on accepting the proposal is the proposal made effective.\n\n[rfc]: https://github.com/search?q=org%3Arust-embedded+is%3Aopen+label%3Arfc\u0026type=Issues\n\n- [Help wanted!]. There's always lots to do but the WG members only have so much free time. You can\n  help us fixing bugs, implementing features, writing tests, trying out examples and tutorials,\n  writing documentation, fixing typos, etc. We'll mentor you through these tasks and review your\n  work. In some cases you may not even need previous embedded experience or access embedded hardware\n  to help us out so don't let that discourage you from checking out our help wanted issues.\n\n[Help wanted!]: https://github.com/search?q=org%3Arust-embedded+is%3Aopen+label%3A%22help+wanted%22\u0026type=Issues\n\n- Join our weekly meetings on [Matrix][matrix]. We use these meetings as a faster, synchronous alternative to the\n  RFC threads on GitHub. The agenda is posted in the matrix channel in advance\n  to the meeting. Everyone is free to join the meeting and share their thoughts. You can also\n  nominate an existing GH thread for discussion if you think it would benefit from a more\n  synchronous discussion.\n  The usual meeting time is Tuesdays, 8pm CET/CEST.\n\n- We have several teams focused on different areas: tooling, Cortex-M crates, etc. and each team\n  maintains several projects (crates, docs and / or tools) that live under the [rust-embedded]\n  organization. You can collaborate with the maintenance and development of these projects by\n  becoming a project collaborator (consult with the team that owns the project) or by [joining] the\n  team.\n\n[rust-embedded]: https://github.com/rust-embedded\n[joining]: https://github.com/rust-embedded/wg/blob/master/rfcs/0136-teams.md#adding-new-members\n\n## Organization\n\nThe WG is composed of several teams whose functions are defined in [RFC\n#136](./rfcs/0136-teams.md). The embedded WG develops and maintains a large set\nof projects under the [rust-embedded] organization. This section lists all the\nteams and all the projects owned by the WG.\n\n[rust-embedded]: https://github.com/rust-embedded\n\n### The core team\n\nThe functions of the core team are:\n\n- Representing the WG in meetings with other [Rust teams].\n- Communicating the needs of the embedded Rust community (e.g. language features, `core` API\n  stabilization) to the Rust teams.\n- Giving the casting vote on intra-WG decisions where no [voting majority] can be achieved.\n- Driving and moderating the weekly meetings.\n\n[Rust teams]: https://www.rust-lang.org/en-US/team.html\n[voting majority]: https://github.com/rust-lang-nursery/embedded-wg/blob/master/rfcs/0136-teams.md#voting-majority\n\n#### Members\n\n- [@adamgreig]\n- [@therealprof]\n\n### The Arm team\n\nThe Arm team develops and maintains the crates related to Arm microprocessors\nand microcontrollers, including Cortex-A, Cortex-R, and Cortex-M.\n\n#### Members\n\n- [@adamgreig]\n- [@berkus]\n- [@jonathanpallant]\n- [@nchong-at-aws]\n- [@newAM]\n- [@raw-bin]\n- [@thalesfragoso]\n- [@therealprof]\n\n#### Projects\n\nProjects maintained by this team.\n\n- [`aarch64-cpu`]\n- [`arm-dcc`]\n- [`cortex-ar`]\n- [`cortex-m-quickstart`]\n- [`cortex-m-rt`]\n- [`cortex-m-semihosting`]\n- [`cortex-m`]\n- [`itm`]\n- [`panic-dcc`]\n- [`panic-itm`]\n- [`panic-semihosting`]\n- [`rust-raspberrypi-OS-tutorials`]\n\n### The embedded Linux team\n\nThe embedded Linux team develops and maintains the core of the embedded Linux crate ecosystem.\n\n#### Members\n\n- [@eldruin]\n- [@nastevens]\n- [@ryankurte]\n- [@sirhcel]\n\n#### Projects\n\nProjects maintained by the embedded Linux team\n\n- [`gpio-cdev`]\n- [`gpio-utils`]\n- [`i2cdev`]\n- [`linux-embedded-hal`]\n- [`meta-rust-bin`]\n- [`spidev`]\n- [`sysfs-gpio`]\n- [`sysfs-pwm`]\n\n### The HAL team\n\nThe HAL team develops and maintains crates containing shared traits and related\ncode that enables the development of hardware abstraction layers and drivers\nwhich can interoperate across all embedded Rust devices on all architectures.\n\n#### Members\n\n- [@therealprof]\n- [@ryankurte]\n- [@eldruin]\n- [@dirbaio]\n- [@MabezDev]\n\n#### Projects\n\nProjects maintained by the HAL team.\n\n- [`embedded-dma`]\n- [`embedded-hal`]\n- [`nb`]\n- [`critical-section`]\n\n### The infrastructure team\n\nThe infrastructure team manages our domains, DNS records, e-mail aliases, etc.\n\n#### Members\n\n- [@nastevens]\n- [@ryankurte]\n\n#### Projects\n\nProjects maintained by this team\n\n- [`rust-embedded-provisioning`]\n\n### The libs team\n\nThe libs team manages library code that is not architecture-specific.\n\n#### Members\n\n- [@dirbaio]\n- [@newAM]\n- [@reitermarkus]\n\n#### Projects\n\nProjects maintained by this team\n\n- [`embedded-alloc`]\n- [`heapless`]\n- [`qemu-exit`]\n- [`volatile-register`]\n\n### The MSP430 team\n\nThe MS430 team develops and maintains the core of the MSP430 crate ecosystem.\n\n#### Members\n\n- [@cr1901]\n\n#### Projects\n\nProjects maintained by this team\n\n- [`msp430-quickstart`]\n- [`msp430-rt`]\n- [`msp430`]\n\n### The RISC-V team\n\nThe RISC-V team develops and maintains the core of the RISC-V crate ecosystem.\n\n#### Members\n\n- [@almindor]\n- [@dkhayes117]\n- [@romancardenas]\n- [@MabezDev]\n- [@jessebraham]\n- [@rmsyn]\n\n#### Projects\n\nProjects maintained by this team\n\n- [`riscv-rust-quickstart`]\n- [`riscv-pac`]\n- [`riscv-rt`]\n- [`riscv-semihosting`]\n- [`riscv`]\n\n### The resources team\n\nThe resources team develops, maintains and curates documentation, books, our\nsocial media accounts and websites, and similar resources on embedded Rust.\n\n#### Members\n\n- [@adamgreig]\n- [@bartmassey]\n- [@eldruin]\n- [@hdoordt]\n- [@jamesmunns]\n- [@therealprof]\n\n#### Projects\n\nProjects maintained by the resources team\n\n- [Awesome embedded Rust]\n- [The Discovery book]\n- [The embedded Rust book]\n- [The embedonomicon]\n- [@rustembedded twitter]\n\n### The tools team\n\nThe tools team maintains and develops software for embedded development\nwhich typically runs on your development machine rather than the\nembedded targets themselves.\n\n#### Members\n\n- [@adamgreig]\n- [@burrbull]\n- [@Emilgardis]\n- [@ryankurte]\n- [@therealprof]\n\n#### Projects\n\nProjects maintained by the tools team\n\n- [`cargo-binutils`]\n- [`itm`]\n- [`svd-parser`]\n- [`svd2rust`]\n\n### The triage team\n\nThe triage team is charge of keeping PR queues moving; they ensure no PR is left unattended.\n\n#### Members\n\n- [@mathk]\n- [@jessebraham]\n- [@jannic]\n\n### Hibernating and Alumni\n\nThe following alumni have put themselves into the hibernation state, due to being absent or busy for an extended amount of time. See [ops/hibernating.md](https://github.com/rust-embedded/wg/blob/master/ops/hibernating.md).\n\n- [@andre-richter]\n- [@awygle]\n- [@bradjc]\n- [@danc86]\n- [@Disasm]\n- [@dvc94ch]\n- [@dylanmckay]\n- [@hannobraun]\n- [@hargoniX]\n- [@ithinuel]\n- [@japaric]\n- [@jcsoo]\n- [@korken89]\n- [@laanwj]\n- [@paoloteti]\n- [@parched]\n- [@pftbest]\n- [@sekineh]\n- [@v-thakkar]\n- [@wizofe]\n- [@posborne]\n- [@thejpster] (Personal) / [@jonathanpallant] (Work)\n- [@YuhanLiin]\n\n### Contact\n\nEach team can be privately contacted via the following e-mail addresses:\n\n- cortex-m@teams.rust-embedded.org\n- embedded-linux@teams.rust-embedded.org\n- hal@teams.rust-embedded.org\n- infrastructure@teams.rust-embedded.org\n- resources@teams.rust-embedded.org\n- risc-v@teams.rust-embedded.org\n- tools@teams.rust-embedded.org\n\nYou can usually find the members of the embedded WG on the Rust Embedded Matrix room\n([#rust-embedded:matrix.org][matrix]).\n\nOur Matrix room is logged by on the bridged IRC channel, and you can find the logs at: https://libera.irclog.whitequark.org/rust-embedded/\n\n[@Disasm]: https://github.com/Disasm\n[@Emilgardis]: https://github.com/Emilgardis\n[@adamgreig]: https://github.com/adamgreig\n[@almindor]: https://github.com/almindor\n[@andre-richter]: https://github.com/andre-richter\n[@awygle]: https://github.com/awygle\n[@bartmassey]: https://github.com/BartMassey\n[@burrbull]: https://github.com/burrbull\n[@bradjc]: https://github.com/bradjc\n[@cr1901]: https://github.com/cr1901\n[@danc86]: https://github.com/danc86\n[@dvc94ch]: https://github.com/dvc94ch\n[@dirbaio]: https://github.com/Dirbaio\n[@dylanmckay]: https://github.com/dylanmckay\n[@eldruin]: https://github.com/eldruin\n[@hannobraun]: https://github.com/hannobraun\n[@hargoniX]: https://github.com/hargoniX\n[@ithinuel]: https://github.com/ithinuel\n[@jamesmunns]: https://github.com/jamesmunns\n[@jannic]: https://github.com/jannic\n[@japaric]: https://github.com/japaric\n[@jcsoo]: https://github.com/jcsoo\n[@jessebraham]: https://github.com/jessebraham\n[@korken89]: https://github.com/korken89\n[@laanwj]: https://github.com/laanwj\n[@MabezDev]: https://github.com/MabezDev\n[@mathk]: https://github.com/mathk\n[@nastevens]: https://github.com/nastevens\n[@nchong-at-aws]: https://github.com/nchong-at-aws\n[@paoloteti]: https://github.com/paoloteti\n[@parched]: https://github.com/parched\n[@pftbest]: https://github.com/pftbest\n[@posborne]: https://github.com/posborne\n[@raw-bin]: https://github.com/raw-bin\n[@reitermarkus]: https://github.com/reitermarkus\n[@romancardenas]: https://github.com/romancardenas\n[@ryankurte]: https://github.com/ryankurte\n[@sekineh]: https://github.com/sekineh\n[@sirhcel]: https://github.com/sirhcel\n[@thalesfragoso]: https://github.com/thalesfragoso\n[@thejpster]: https://github.com/thejpster\n[@jonathanpallant]: https://github.com/jonathanpallant\n[@therealprof]: https://github.com/therealprof\n[@v-thakkar]: https://github.com/v-thakkar\n[@wizofe]: https://github.com/wizofe\n[@dkhayes117]: https://github.com/dkhayes117\n[@YuhanLiin]: https://github.com/YuhanLiin\n[@newAM]: https://github.com/newAM\n[@hdoordt]: https://github.com/hdoordt\n[@rmsyn]: https://github.com/rmsyn\n[@berkus]: https://github.com/berkus\n\n[@rustembedded twitter]: https://twitter.com/rustembedded\n[Awesome embedded Rust]: https://github.com/rust-embedded/awesome-embedded-rust\n[The Discovery book]: https://github.com/rust-embedded/discovery\n[The embedded Rust book]: https://github.com/rust-embedded/book\n[The embedonomicon]: https://github.com/rust-embedded/embedonomicon\n[`embedded-alloc`]: https://github.com/rust-embedded/embedded-alloc\n[`arm-dcc`]: https://github.com/rust-embedded/arm-dcc\n[`cargo-binutils`]: https://github.com/rust-embedded/cargo-binutils\n[`aarch64-cpu`]: https://github.com/rust-embedded/aarch64-cpu\n[`cortex-m-quickstart`]: https://github.com/rust-embedded/cortex-m-quickstart\n[`cortex-m-rt`]: https://github.com/rust-embedded/cortex-m/tree/master/cortex-m-rt\n[`cortex-m-semihosting`]: https://github.com/rust-embedded/cortex-m/tree/master/cortex-m-semihosting\n[`cortex-m`]: https://github.com/rust-embedded/cortex-m\n[`cortex-ar`]: https://github.com/rust-embedded/cortex-ar\n[`embedded-hal`]: https://github.com/rust-embedded/embedded-hal\n[`gpio-cdev`]: https://github.com/rust-embedded/gpio-cdev\n[`gpio-utils`]: https://github.com/rust-embedded/gpio-utils\n[`heapless`]: https://github.com/rust-embedded/heapless\n[`i2cdev`]: https://github.com/rust-embedded/rust-i2cdev\n[`itm`]: https://github.com/rust-embedded/itm\n[`linux-embedded-hal`]: https://github.com/rust-embedded/linux-embedded-hal\n[`meta-rust-bin`]: https://github.com/rust-embedded/meta-rust-bin\n[`msp430-quickstart`]: https://github.com/pftbest/msp430-quickstart\n[`msp430-rt`]: https://github.com/pftbest/msp430-rt\n[`msp430`]: https://github.com/pftbest/msp430\n[`nb`]: https://github.com/rust-embedded/nb\n[`panic-dcc`]: https://github.com/rust-embedded/arm-dcc/tree/master/panic\n[`panic-itm`]: https://github.com/rust-embedded/cortex-m/tree/master/panic-itm\n[`panic-semihosting`]: https://github.com/rust-embedded/cortex-m/tree/master/panic-semihosting\n[`qemu-exit`]: https://github.com/rust-embedded/qemu-exit\n[`riscv-pac`]: https://github.com/rust-embedded/riscv/tree/master/riscv-pac\n[`riscv-rt`]: https://github.com/rust-embedded/riscv/tree/master/riscv-rt\n[`riscv-semihosting`]: https://github.com/rust-embedded/riscv/tree/master/riscv-semihosting\n[`riscv-rust-quickstart`]: https://github.com/riscv-rust/riscv-rust-quickstart\n[`riscv`]: https://github.com/rust-embedded/riscv/tree/master/riscv\n[`rust-embedded-provisioning`]: https://github.com/rust-embedded/rust-embedded-provisioning\n[`rust-raspberrypi-OS-tutorials`]: https://github.com/rust-embedded/rust-raspberrypi-OS-tutorials\n[`spidev`]:https://github.com/rust-embedded/rust-spidev\n[`svd-parser`]: https://github.com/rust-embedded/svd\n[`svd2rust`]: https://github.com/rust-embedded/svd2rust\n[`sysfs-gpio`]: https://github.com/rust-embedded/rust-sysfs-gpio\n[`sysfs-pwm`]: https://github.com/rust-embedded/rust-sysfs-pwm\n[`volatile-register`]: https://github.com/rust-embedded/volatile-register\n[`embedded-dma`]: https://github.com/rust-embedded/embedded-dma\n[`critical-section`]: https://github.com/rust-embedded/critical-section\n\n## Other projects\n\nThese are other projects you may be interested in but that (currently) are not owned by the WG.\n\n- [AVR fork of Rust](https://github.com/avr-rust/)\n- [Xtensa fork of Rust (for Espressif chips)](https://github.com/esp-rs/rust)\n\n## Ongoing community efforts\n\n### Device specific communities\n\nSeveral device specific communities exist that are not part of the working group.\nThese communities maintain crates for peripheral access, hardware abstraction,\nexamples, and more that are specific to a particular family of devices.\nThe list below is not exhaustive and will be updated as device support increases.\n\n- [nrf-rs](https://github.com/nrf-rs): Nordic nRF series of microcontrollers\n- [stm32-rs](https://github.com/stm32-rs): STM32 microcontrollers\n- [lpc-rs](https://github.com/lpc-rs): NXP LPC microcontrollers\n- [imxrt-rs](https://github.com/imxrt-rs): NXP i.MX RT microcontrollers\n- [esp-rs](https://github.com/esp-rs): Espressif Systems microcontrollers\n- [rp-rs](https://github.com/rp-rs): Raspberry Pi microcontrollers including the RP2040\n\n### [`embedded-hal`]\n\n[`embedded-hal`]: https://github.com/rust-embedded/embedded-hal\n\n`embedded-hal` is a project that aims to build a standard set of traits (interfaces) for I/O\nfunctionality common in embedded devices: Serial, I2C, etc. with the goal of serving as a base for\nbuilding reusable driver crates, crates to interface with external components like sensors.\n\nThere are plenty of traits that still need to be designed, in particular ones that involve async\nI/O. Join the discussion and help us design the missing traits so that they'll fulfill your needs.\n\n### [The weekly driver initiative][wd]\n\nTo put the `embedded-hal` to test and to expand the embedded crates.io ecosystem we are running the\nweekly driver initiative. The goal is to release a new `no_std`, generic, `embedded-hal` driver\ncrate every one or two weeks.\n\nThere's lots of cool devices that would be great to have drivers for. Join the initiative and help\nus grow the embedded crates.io ecosystem!\n\n[wd]: https://github.com/rust-lang-nursery/embedded-wg/issues/39\n\n### [Awesome embedded Rust](https://github.com/rust-embedded/awesome-embedded-rust)\n\nThe community is building a curated list of crates useful for embedded development. In this list\nyou'll find driver crates, board support crates and general purpose no-std crates. Help us improve\nthis list by adding your crate via PR or by tackling any of our [help wanted][aer-hw] issues.\n\n[aer-hw]: https://github.com/rust-embedded/awesome-embedded-rust/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22\n\n### [Embedded category in the user forum][ef]\n\nAs an experiment the [Rust lang user forum][urlo] has gained a new `embedded` category.\n\nThis is meant as a friendly exchange for anyone interested in embedded topics with Rust.\n\nSo if you want to discuss ideas, problems or solutions please feel free to chime in on existing topics or create a new one!\n\n[urlo]: https://users.rust-lang.org\n[ef]: https://users.rust-lang.org/c/embedded\n\n## RFCs\n\nWhen the team deems it necessary the RFC process may be used to make decisions or to design\nprocesses, user interfaces, APIs, etc.\n\nLearn more about the Rust's RFC process (which is the same as our own) [here][rust-rfc].\n\n[rust-rfc]: https://rust-lang.github.io/rfcs/\n\nTo create an RFC, simply:\n- clone this repo to your own personal one\n- copy `0000-template.md` to `text/0000-my-feature.md` (where \"my-feature\" is\n  descriptive. Don't assign an RFC number yet)\n- fill in the details of your RFC in that file\n- Open an pull request with this repository\n","funding_links":[],"categories":["Community","Others"],"sub_categories":[],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Frust-embedded%2Fwg","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Frust-embedded%2Fwg","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Frust-embedded%2Fwg/lists"}