Skip to content
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.

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

Default workflow for team membership lifecycle? #194

Open
tellyworth opened this issue May 13, 2022 · 0 comments
Open

Default workflow for team membership lifecycle? #194

tellyworth opened this issue May 13, 2022 · 0 comments

Comments

@tellyworth
Copy link

This is an idea intended for discussion, not a definite proposal.

The Marketing team handbook has a nice clear workflow for new team members and new team reps:

https://make.wordpress.org/marketing/handbook/getting-involved/new-contributor-orientation/
https://make.wordpress.org/marketing/handbook/getting-involved/teamrep-handover/

Should we consider implementing some simple automation/prompts for a subset of these, to reduce human work required (and scope for errors and delays), and to help out teams that don't have their own process?

For example, we could have a few basic steps that happen when a new team member is onboarded (whether they're a 5ftf pledge or not):

  • The new member is sent a link to the handbook to read (and perhaps confirms that they've done so)
  • The new member is possibly given special user caps on a site (such as author role on a team p2, for example)
  • The new member must link their GH account to their w.org profile
  • They must have a Slack account
  • They join the team's Slack channel
  • An existing team member (or a bot) sends them a welcome message
  • They get a profile badge
  • They get added to the team group

We could have some conditional code that checks those steps, automatically grants access/badges etc at the appropriate times, and pings a channel when someone gets stuck for a long period ("user xyz joined team #meta a week ago but hasn't created their slack account yet" for example).

The onboarding process might begin with an invitation from existing team members, or by the new member clicking a "join this team" button (in the handbook?).

There could be a similar process for promoting someone to a Team Rep:

  • Additional access is granted (eg editor role on a team p2, /here access in Slack)
  • The new team rep is sent some additional docs/handbook info to read
  • They may need to follow some password hygiene steps or enable 2FA on Slack

As well as automating the workflow for new members/reps, we could also automate a workflow for dormant and abandoned users:

  • If a team member/rep hasn't logged on or had profile activity for > 12mo, then email them a prompt
  • If they still haven't logged on after a while, automatically downgrade their special user caps
  • Ping the team with a message: "team member xyz hasn't responded in more than a year, remove them from the list?"

Having an automated end to the workflow would help reduce the risk we have from long-dormant accounts with special user permissions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants