TW group change tasks for Govern / Anti-Abuse
- Stage/group being transitioned: devopsgovern groupanti-abuse
- Current technical writer:
@phillipwells
- Incoming technical writer: docs channel
- Reassignment milestone: 17.1
@phillipwells)
Tasks for current technical writer (-
Invite the incoming TW to the stage and group Slack channels. -
Post in Slack about the changeover. Communicate the timeline and how MRs will be handled. -
Reach out to the Product Manager, Engineering Manager, and Design Manager to communicate the change.Communication in https://gitlab.com/gitlab-org/technical-writing/-/issues/1019 - In the
www-gitlab-com
repository, update:-
data/stages.yml
, with your new assignment. If you're onboarding as a new Technical Writer, you can wait until you've completed a full release cycle as a trainee before doing this step and the next steps.
-
- In the
gitlab
repository, update as needed (in the following order, but can be done in the same MR):-
The metadata in all related markdown files (if the group name changed). -
Group assignments in lib/tasks/gitlab/tw/codeowners.rake
. -
.gitlab/CODEOWNERS
by running thetw:codeowners
Rake task to ensure no pages are missed.
-
@dianalogan)
Tasks for technical writing manager (-
Update google sheets used for team rebalancing planning. -
Check Workday for the Job Title Specialty (Multi-Select). If the specialty does not exist, create an issue in the People Group general project, and use the Workday: Job Title Specialty Request template. -
Update Workday with the new group assignments. Workday updates the group assignments in data/team_members/person
. Interim instructions during Workday rollout: Manager emailspeople-connect@gitlab.com
with details of changes.
Edited by Diana Logan