[RFC] Bootstrap the embedded Linux team #139
Conversation
|
Looks good to me! As I mentioned during the IRC meeting, I’m interested in helping out with embedded Linux efforts. :-) |
|
Mentioning @nerdyvaishali as she has expressed interest in this previously, and is currently assisting with the IRR embedded 2018 project. |
|
@japaric LGTM. Of course, we'll be looking for additional contributors to expand things further as well as projects that can be pulled in or developed. |
japaric
force-pushed
the
embedded-linux
branch
from
64d7f7f to
fc9e330
Compare
japaric
requested review from
dylanmckay,
jcsoo,
thejpster and
a team
as code owners
|
Awesome! I have created the @rust-embedded/embedded-linux team. Could any of you configure the repositories, Travis and bors as written down here. @levex @nerdyvaishali Please get in touch with @nastevens and @posborne to discuss how you collaborate with the embedded Linux team. @rust-embedded/all Any of you feel free to land this PR. |
|
+r |
|
r+ |
|
@japaric I tried =P |
|
@dvc94ch there's no bors here. The PR can be merged after it's been approved by someone other than the PR author. |
As per RFC #136 this PR kickstarts the embedded Linux 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.
r? @nastevens @posborne I need confirmation that you are on board with RFC #136 and the proposed
crate list. I will continue maintaining the
linux-embedded-halcrate as a collaborator.