-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RFC] create the ecosystem team #317
base: master
Are you sure you want to change the base?
Conversation
I'd be interested to hear how you think this differs/overlaps with the Resources team. |
In my mind the ecosystem team is focused on doing code reviews and writing If in practice the ecosystem team ends up being a subset of the resources team
|
SGTM |
This RFC has reached the required voting majority of 33%+1 (11/10) and has been approved. 🎉 We still need more members though so let's hold off merging this until then. |
I would be interested in giving some help here but I would certainly need mentoring. The good part is that I tend to already have a look at a lot of PR since I am part of the triage team. The down side is that I am still learning embedded development. |
I'd be interested in helping out. I've written a few driver crates and a HAL for my dissertation so I've got some experience with api design. |
Summary
Create a team dedicated to growing the embedded crate ecosystem.
Team tasks
This team will
Develop guidelines for library design and application development
Review, and in some cases aid in the design of, foundational libraries.
Review projects submitted to the showcase.
This team will be in charge of the Embedded Rust "libs blitz". See #316
Member qualifications / tasks
Members of this team are expected to
Have experience with Rust API design, Rust code reviews and / or writing,
auditing and reasoning about unsafe code.
Write guidelines and review reports.
Study https://rust-lang-nursery.github.io/api-guidelines/ and similar material
Why also include application development?
Embedded application development is sufficiently different from command line
application development that a different set of guidelines is required -- the
patterns and best practices are totally different.
Unresolved questions
Bikeshed team name
Needs more members