Document membership criteria and expectations #174
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
|
Also, I'd like to discuss leadership succession. @joshtriplett and I both agree that there should be some kind of regular check-in to decide how to proceed. I'm still happy leading the team, but I'm also interested in discussing with folks what it would look like for someone else to takeover and when that might make sense! |
|
@rfcbot fcp merge I think this is largely documenting existing practice, but I've also made a few changes (e.g., suggesting a brief write-up for a proposed new member). I'd like to get people to review and agree to the plans formally. |
|
Team member @nikomatsakis has proposed to merge this. The next step is review by the rest of the tagged team members: No concerns currently listed. Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up! See this document for info about what commands tagged team members can give me. |
rfcbot
added
proposed-final-comment-period
disposition-merge
nikomatsakis
force-pushed
the
path-to-membership
branch
from
98ec543 to
92d799a
Compare
rfcbot
added
the
final-comment-period
|
🔔 This is now entering its final comment period, as per the review above. 🔔 |
|
LGTM, thanks for incorporating all the feedback. |
|
Looks great, thanks @nikomatsakis @rfcbot reviewed |
Co-authored-by: Josh Triplett <josh@joshtriplett.org>
nikomatsakis
force-pushed
the
path-to-membership
branch
from
40ea1fd to
76c1385
Compare
rfcbot
added
finished-final-comment-period
to-announce
This PR documents membership criteria and expectations, and discusses a simple pattern for selecting new leads.