hackforla / hackforla/guides

Offboarding and Team Members Cleanup

Open
#91 20 comments 0 reactions 1 assignee Claimed by @ExperimentsInHonesty View on GitHub
feature: administrative feature: offboarding feature: weekly tasks role: Product size: 1pt
Dominant language
No language data
Stars
12
Forks
0
PR merge metrics
No merged PRs in 30d

Description

### Overview
We need to maintain a cycle of offboarding and team members cleanup so that we can remove formers Guides Team members who left the team officially and team members who are inactive.

### Action Items
- Do a one time audit of all team members to clean up the resources (roster/GitHub/google drive, etc.)
- Add members that need to be removed to the comments on this issue
- remove #92 from icebox and remove dependency label and put into prioritized backlog
- Review all issues assigned to members
- Check for members who are inactive on their issue
- communicate with them using the message below for the appropriate week
- After 4 weeks
- Remove former members using the onboarding and offboarding issue (currently, we use the product issue for everyone)
- Mark as Inactive on roster

### Resources/Instructions
- https://github.com/hackforla/guides/issues/92

#### Messages

##### Week 1
- Issue message
```
@[insert github handle] Please provide update using these guidelines
1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (if necessary): "Add any pictures that will help illustrate what you are working on."
```

##### Week 2
- Issue message
```
We did not hear from you last week after we reached out, please provide the following update in this issue.
1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (if necessary): "Add any pictures that will help illustrate what you are working on."

If we do not hear from you in the next week, you will be removed from the project, until you are ready to come back.
```

- Slack message
```
@[insert slack handle] If you want to remain on the team, please provide an update on your issue [insert issue link]
```

##### Week 3
- Issue Message
```
We have not heard from you via this issue or slack for 3 full weeks. We are going to remove you from the team resources You are welcome to come back, when you are ready, you can message us in the [#guide](https://hackforla.slack.com/archives/C028T9XU9S5) Slack channel to be re-added.
```

- Slack message
```
@[insert slack handle] [insert link to issue comment]
```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.