Define new team-member invitation and onboarding process
Invitation criteria & process:
I don't think it's worth formalizing any criteria for the moment.
Vote on whether to extend an invitation in team meetings.
- Invite the new person to the team
- Give new member developer permissions on snowdrift organization here
- Add new member to the team group on the forum here
- Give the new team member moderator privileges on the forum, from their profile.
- Add new member to +snowdrift:matrix.org (if they use matrix)
- Right now only @iko can do this, since Matrix/element does not yet have the ability to add multiple admins or transfer ownership.
- Add new member to
!folksfpbot command if they're not already on it
- fpbot command:
!set channels.#snowdrift.folks <comma,separated,list,of,names>
- fpbot command:
- Ask the new member to update their meeting availability and add their contact info.
- Ask the new member to subscribe to the shared calendar (linked from availability topic), if they use a digital calendar.
- Conduct a low/no-stakes "interview" where the new member explains Snowdrift.coop to us as if we'd never heard of it.
- Why: It's extra confusing if a team member spreads misinformation about how the platform works. While we can't prevent misunderstandings, we can at least make sure that team members don't have any misconceptions they might inadvertently spread.
- This is just an opportunity to correct any misunderstandings — the new member isn't being graded/assessed.
- Walk the new member through the private places they now have access to.
- Private gitlab repos
- Private forum categories
- If the new member would like, create a blog account for them. link
- Requires asking for an email
A bunch of discussion to pull from is at https://community.snowdrift.coop/t/when-and-how-to-invite-new-team-members/1457
also this one older proposal: https://community.snowdrift.coop/t/proposal-for-bringing-on-new-volunteers-and-team-members/1084