Add documentation about the libs teams and membership. #28
Conversation
| - Objections are ideally shared with the entire team, but may also be shared privately with the team lead or the moderation team. | ||
| - Objections ideally include examples showing behavior not in line with the expectations described under step 1 | ||
| (or the code of conduct). | ||
| 3. The team lead reaches out to the moderation team to ask if they are aware of any objections. |
There was a problem hiding this comment.
@rust-lang/mods How do you feel about this? This is not something we did in the past, but I think it'd be good if we do.
There was a problem hiding this comment.
I personally really like the underlying idea: making it clear to existing members they are encouraged to report issues, rather than have them sulk, be curt, or quit.
In general we'd appreciate if people reported inter-personal issues and let us help them solve them -- at any time, really. Having an explicit reminder they are encouraged to from time to time is an excellent way of "normalizing" this, and having this on the check-list before "forcing" confrontations between individuals is a good "last resort" check, I think.
I'll check with the other mods, but I don't foresee any big issue, and have no wording tweak to suggest at present.
Co-authored-by: Jane Lusby <[email protected]>
Co-authored-by: Jane Lusby <[email protected]>
Co-authored-by: Jane Lusby <[email protected]>
Co-authored-by: Josh Stone <[email protected]>
|
@rfcbot merge |
This comment has been minimized.
This comment has been minimized.
|
Team member @m-ou-se 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. |
|
🔔 This is now entering its final comment period, as per the review above. 🔔 psst @m-ou-se, I wasn't able to add the |
|
The final comment period, with a disposition to merge, as per the review above, is now complete. As the automated representative of the governance process, I would like to thank the author for their work and everyone else who contributed. This will be merged soon. psst @m-ou-se, I wasn't able to add the |
generated from commit c9fe0ff
Hey @rust-lang/libs @rust-lang/libs-api!
I wrote some stuff about our team that I think we should add to the std-dev-guide. (We should probably add more over time. But it's a start.)
Part of it was already discussed as part of the charter or is just describing things we already do, so there should be no surprises there.
What is new are some details in
src/membership.md, about how and when people are invited to the Library Contributors and to the Libs (API) Teams. I'd like to hear your feedback and whether you agree with what I wrote there. Feel free to give any feedback in private too if you prefer.