-
Notifications
You must be signed in to change notification settings - Fork 101
[RFC] Bootstrap the Cortex-M team #143
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
Conversation
I would indeed be very interested! |
I am generally interested, but my time is limited, and I'm currently prioritizing embedded-hal over the Cortex-M crates. If a certain level of activity is expected of members at all times, I should refrain from joining right now. On the other hand, if it's okay with the other members that I won't be very active for the time being, I'd be happy to be a part of this team, and I'll pitch in as I can. |
Not sure if you're looking for volunteers at this stage but I'd be interested in being a part of this team and am happy to commit time to these crates. |
@korken89 @adamgreig Awesome! Thanks, you've been added to the team. @hannobraun Thanks for considering joining. If we seem to be short staffed after the initial team is formed we'll reach out to you. |
Count me in. |
@therealprof welcome! |
Hi, I'd be interested to be part of this :) |
As per RFC #136 this PR kickstarts the Cortex-M team
Note that the team composition is not final. The team is expected to grow over time. The mechanism
for joining a team is specified in RFC #136.
This is the team with most crates so it should have a large team to cope with the maintenance load.
active Cortex-M developers off the top of my head: would you be interested in helping maintain
these crates? @hannobraun @thejpster @therealprof @korken89