Skip to content
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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[RFC] create the ecosystem team #317

wants to merge 1 commit into from

Conversation

japaric
Copy link
Member

@japaric japaric commented Feb 17, 2019

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

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

@japaric japaric added the RFC label Feb 17, 2019
@japaric japaric requested review from dylanmckay, jcsoo and a team as code owners February 17, 2019 22:17
@jamesmunns
Copy link
Member

I'd be interested to hear how you think this differs/overlaps with the Resources team.

@japaric
Copy link
Member Author

japaric commented Feb 27, 2019

In my mind the ecosystem team is focused on doing code reviews and writing
coding guidelines whereas the resources team manages (writes, curates) resources
(docs, lists) in general.

If in practice the ecosystem team ends up being a subset of the resources team
that seems OK-ish to me, but what I don't to want to happen is that:

  • Everyone on the resources team feel like they have to do code reviews.
    Coordinating 8 people to review a crate would be tricky (e.g. people could end
    up with nothing to do, etc.). Plus the resources team already has plenty of
    things to look over.

  • The people on the ecosystem team get distracted reviewing PRs to the book,
    blog, etc. They can help if they have the spare cycles but they should
    focus on reviewing code and writing the guidelines.

@thejpster
Copy link
Contributor

SGTM

@japaric
Copy link
Member Author

japaric commented Mar 12, 2019

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.

@japaric japaric added decision-accepted We voted on this proposal and accepted it S-blocked labels Mar 12, 2019
@mathk
Copy link

mathk commented Mar 18, 2019

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.

@MabezDev
Copy link
Member

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.

@adamgreig adamgreig mentioned this pull request Oct 16, 2023
25 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
decision-accepted We voted on this proposal and accepted it RFC S-blocked
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet