Skip to content

ops: hibernating #324

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Apr 2, 2019
Merged

ops: hibernating #324

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 24 additions & 0 deletions ops/hibernating.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,24 @@
# Hibernating

A member that will be absent or busy for an extended period of time and not able
to participate in the WG during that time should put themselves in "hibernation"
state. During this hibernation period:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The problem is they will not be able to put themselves in "hibernation" state if they are absent or busy. The only way to enforce this is to automate the process of hibernation or at least to send a reminder time to time.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's possible to be able to (barely) keep up, while at the same time being too busy to really participate. This is my current situation, and if this PR is accepted before that situation changes, I'm going to use this mechanism to retire myself.

It's already possible to remove team members without their participation: https://github.com/rust-embedded/wg/blob/master/rfcs/0136-teams.md#removing-members

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The problem is they will not be able to put themselves in "hibernation" state if they are absent or busy

Sure, but the proposal says that members that will be busy or absent (in the future) should put themselves into hibernation (now). This proposal is for them. And as @hannobraun said people currently busy may still be able to hibernate themselves.

The only way to enforce this is to automate the process of hibernation

I don't think we should do this. Hibernation should be voluntary.

at least to send a reminder time to time.

I don't think we should do this either. Sending an e-mail (once) to /all when / if this (or any other significant change) occurs seems fine, though.


- The member will be removed from the highfive rotation. New PRs will *not* be
assigned to them by the highfive bot.

- The member will be removed from their GitHub teams'. `cc @rust-embedded/$team`
will *not* cc them.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will the member stay part of @rust-embedded/all? Would be nice to be able to keep up with internal discussions while you're away (although those happen rarely anyway).

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this can be achieved with tuning your notifications. We have "watch" button on each team page. So you can subscribe to /all and unsubscribe from everything else without any membership modifications.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@hannobraun no, /all is included in "their GitHub teams". We will not modify the member repository subscriptions, but IDK if removing someone from a team has any effects on their repository subscriptions.


- The member name will be removed from the list of teams in the rust-embedded/wg
README, but they will be listed under the 'Hibernating' section of that
README.

- The member will not be counted when computing the number of votes required to
reach majority on matters that concern the teams they are a member of. This
includes PRs labeled `T-all` that need a decision.

To enter or leave the hibernation state the member will:

- Notify their teams (e.g. `cc @rust-embedded/$team`) and send a PR to
rust-embedded/wg updating the README to reflect their hibernation state.