Write the checklist of what the team does for a new member, and publish it on the wiki

### 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

- [ ] 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](https://github.com/hackforla/devops/wiki/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.

### Resources/Instructions

- Model to copy from: [onboard-ops-cop-lead.md](https://github.com/hackforla/devops/blob/master/.github/ISSUE_TEMPLATE/onboard-ops-cop-lead.md)
(leads only) and the checklist in the body of hackforla/devops#30
- The incubator equivalent, which has the roster steps: hackforla/incubator#27
- [Onboarding Process for Project Team Leads](https://github.com/hackforla/devops/wiki/Onboarding-Process-for-Project-Team-Leads)
- [DevOps CoP Roster](https://docs.google.com/spreadsheets/d/1j6l2cdyAEZ73NCXw0CwwMnh8tZda-oE7tu8usBwv4Bs)
- GitHub teams: https://github.com/orgs/hackforla/teams
- **Do not edit hackforla/devops#30 or hackforla/incubator#27 as part of this.** They are
recurring issues that get a new comment per person; changing their bodies is separate work.

Start by comparing .github/ISSUE_TEMPLATE/onboard-ops-cop-lead.md, hackforla/devops#30, hackforla/incubator#27, the existing team-lead wiki page, and the DevOps CoP Roster. Verify each onboarding step and link against current reality, then publish the validated member checklist on the chosen wiki page, link it from Home under “Joining the DevOps team,” and have an uninvolved lead confirm it is sufficient.

Rédigé par le modèle d'indexation à partir du texte de l'issue.