[RFC] lead -> core team #328
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ryankurte
approved these changes
Mar 5, 2019
jamesmunns
approved these changes
Mar 5, 2019
korken89
approved these changes
Mar 5, 2019
Disasm
approved these changes
Mar 5, 2019
thejpster
approved these changes
Mar 5, 2019
hannobraun
approved these changes
Mar 5, 2019
andre-richter
approved these changes
Mar 5, 2019
posborne
approved these changes
Mar 6, 2019
paoloteti
approved these changes
Mar 6, 2019
bors bot
added a commit
that referenced
this pull request
Mar 7, 2019
329: temporarily remove japaric from some teams r=japaric a=japaric As I mentioned in #328 I'll be busier and busier during the next few months so I'll be temporarily removing myself from some teams. For the next few months I'll limit my duties to /core, /cortex-r (can't have a one-person team!) and /ecosystem (when it's formed). cc @rust-embedded/cortex-m @rust-embedded/embedded-linux @rust-embedded/hal @rust-embedded/tools @rust-embedded/triage I will remove myself from the highfive rotation so don't assign new PRs to me (This doesn't need voting just notifying the affected teams and a single approval.) Co-authored-by: Jorge Aparicio <[email protected]>
mathk
approved these changes
Mar 8, 2019
adamgreig
approved these changes
Mar 8, 2019
cr1901
approved these changes
Mar 12, 2019
nastevens
approved these changes
Mar 12, 2019
|
This RFC has reached the required voting majority of 33%+1 (13/10) and has been approved. 🎉 bors r+ |
bors bot
added a commit
that referenced
this pull request
Mar 12, 2019
328: [RFC] lead -> core team r=japaric a=japaric ## Summary This RFC proposes that we replace the position of the "lead" with a core team. ## Motivation I (@japaric) will be busy working on my thesis for the next ~3 months and won't be able to be as active in the WG as I have been. Instead of having a single not so active lead for months I propose that we have a small core team that takes over the functions of the lead. ## Design The core team will inherit the functions of the lead, namely what's already in the README: - Representing the WG in meetings with other Rust teams / WG. - Communicating the needs of the embedded Rust community to the Rust teams. - Giving the casting vote on intra-WG decisions where no voting majority can be achieved. - Driving and moderating the weekly meetings. Additionally, we'll: - Add the members of the core team to the rust-embedded/core GitHub team (to make `cc @rust-embedded/core` work) and give them admin privileges in the rust-embedded org (so they can create and modify GH teams). - Set up an e-mail alias for the core team: [email protected]. ## Implementation I propose that we start the core team with these members: - [x] @jamesmunns - [x] @japaric - [x] @therealprof (Of course the people above have to accept first.) I have chosen these people because they have been consistently active in the WG and have interacted with members of the Rust teams in the past. Also 3 is the smallest odd number that's not 1. ## Alternatives As an extension we *could* leave some (all?) decisions on cross cutting issues, today labeled as `T-all`, to the core team, which would let us make much quicker decisions but this proposal leaves that up to a different RFC (if we want to do it at all). --- r? @rust-embedded/all Co-authored-by: Jorge Aparicio <[email protected]>
Build succeeded |
|
The GH changes have been made effective. 👋 @rust-embedded/core @rust-embedded/infrastructure could you set up the mailing list? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This RFC proposes that we replace the position of the "lead" with a core team.
Motivation
I (@japaric) will be busy working on my thesis for the next ~3 months and won't
be able to be as active in the WG as I have been. Instead of having a single
not so active lead for months I propose that we have a small core team that
takes over the functions of the lead.
Design
The core team will inherit the functions of the lead, namely what's already in
the README:
Representing the WG in meetings with other Rust teams / WG.
Communicating the needs of the embedded Rust community to the Rust teams.
Giving the casting vote on intra-WG decisions where no voting majority can be
achieved.
Driving and moderating the weekly meetings.
Additionally, we'll:
Add the members of the core team to the rust-embedded/core GitHub team (to
make
cc @rust-embedded/corework) and give them admin privileges in therust-embedded org (so they can create and modify GH teams).
Set up an e-mail alias for the core team: [email protected].
Implementation
I propose that we start the core team with these members:
(Of course the people above have to accept first.)
I have chosen these people because they have been consistently active in the WG
and have interacted with members of the Rust teams in the past. Also 3 is the
smallest odd number that's not 1.
Alternatives
As an extension we could leave some (all?) decisions on cross cutting issues,
today labeled as
T-all, to the core team, which would let us make much quickerdecisions but this proposal leaves that up to a different RFC (if we want to do
it at all).
r? @rust-embedded/all