You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need one written checklist of everything the team has to do when someone joins, so that
onboarding does not depend on whichever lead happens to pick it up remembering all of it. A
checklist exists for onboarding a CoP lead and one exists on the incubator side for team
members, but there is nothing for a general DevOps CoP member, and neither of the existing two
is on the wiki where a lead would look for it.
Action Items
Draft the checklist. At minimum it must cover:
Adding them to the right GitHub teams. Note the org has five: devops-read, devops-write, devops-merge, devops-maintain, devops-admin. Say which ones a new
member gets by default and who can grant them.
Getting them onto the roster — the existing incubator checklist splits this into "send",
"team member adds themselves", "check for public", which is worth copying because the
middle step is the one that gets forgotten.
Pointing them at their onboarding issue, and being explicit about which one.
Slack #ops, the Google Calendar invite, Google Drive, and 1Password — copy the
structure from the lead checklist rather than inventing a new one.
Confirm each step against reality before writing it down. Do not copy a step from the lead
checklist without checking it still works — at least one link in that checklist is already
dead (see the sibling issue on the 404 team link).
Decide where the canonical copy lives: a new wiki page, or an addition to Onboarding Process for Project Team Leads.
That page is currently incubator-flavoured, points at a closed issue, and has an empty
"Project's GitHub team URL" field, so it needs attention either way.
Publish it on the wiki and link it from Home under "Joining the DevOps team".
After it is published, ask a lead who did not write it to read it and confirm they could
onboard someone from it alone.
Overview
We need one written checklist of everything the team has to do when someone joins, so that
onboarding does not depend on whichever lead happens to pick it up remembering all of it. A
checklist exists for onboarding a CoP lead and one exists on the incubator side for team
members, but there is nothing for a general DevOps CoP member, and neither of the existing two
is on the wiki where a lead would look for it.
Action Items
devops-read,devops-write,devops-merge,devops-maintain,devops-admin. Say which ones a newmember gets by default and who can grant them.
"team member adds themselves", "check for public", which is worth copying because the
middle step is the one that gets forgotten.
#ops, the Google Calendar invite, Google Drive, and 1Password — copy thestructure from the lead checklist rather than inventing a new one.
checklist without checking it still works — at least one link in that checklist is already
dead (see the sibling issue on the 404 team link).
Onboarding Process for Project Team Leads.
That page is currently incubator-flavoured, points at a closed issue, and has an empty
"Project's GitHub team URL" field, so it needs attention either way.
Homeunder "Joining the DevOps team".onboard someone from it alone.
Resources/Instructions
(leads only) and the checklist in the body of Onboard / Offboard: CoP leads #30
recurring issues that get a new comment per person; changing their bodies is separate work.