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
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.
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):
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:
/hereaccess in Slack)As well as automating the workflow for new members/reps, we could also automate a workflow for dormant and abandoned users:
Having an automated end to the workflow would help reduce the risk we have from long-dormant accounts with special user permissions.