Create a repeatable onboarding and access-provisioning process

[jcklpe]

Problem

Onboarding is currently manual and inconsistent. Volunteers may attend an orientation or meeting, get added to Slack, and receive other access only when someone remembers or a need becomes urgent.

Automation should follow a defined workflow rather than substitute for one.

Two connected lanes

Human onboarding: orientation, Civic Tech 101, understanding Open Austin, finding a participation path, and establishing a human point of contact. This primarily belongs with Engagement and Education.

Technical provisioning: baseline system access, role-specific access, GitHub Teams, approval, tracking, and offboarding. This primarily belongs with Infrastructure.

Tasks

• Review the prior YAML onboarding template linked below.
• Define the baseline onboarding checklist.
• Define triggers for specialized Team or Product Team access.
• Connect provisioning decisions to Define organization-wide security, access, and permissions strategy #498.
• Coordinate the human workflow with iterate on onboarding #474 and Civic Tech 101.
• Decide how completion and current participation state are recorded through Explore a lightweight way to track members and contributors #506.
• Identify which steps can safely be automated.

Related work

• Define Infrastructure starter backlog and GitHub org onboarding process #484 — Infrastructure starter backlog
• Define organization-wide security, access, and permissions strategy #498 — security and permissions strategy
• Explore a lightweight way to track members and contributors #506 — volunteer/member information model
• iterate on onboarding #474 — human onboarding iteration
• Reorg github teams #427 — GitHub Teams

Definition of done

• Human and technical responsibilities are separated and connected.
• Baseline and specialized onboarding paths are documented.
• Approval and escalation paths are clear.
• One general-volunteer path and one specialized-access path can be piloted.
• Automation candidates are identified after the workflow is agreed upon.

[jcklpe]

The original YAML template is: https://github.com/open-austin/org/blob/b88c30f9248e120a0e04d713a6af496ec48738ab/.github/ISSUE_TEMPLATE/onboarding.md

[jcklpe]

Relevant work: #498

[jcklpe]

#427