Transition: ~group::optimize to Marcin
- Stage/group being transitioned:
- Current technical writer: @mjang1
- Incoming technical writer: @msedlakjakubowski
- Reassignment milestone:
Tasks for current technical writer
Invite the incoming TW to the stage and group Slack channels.
- Channel list: s_manage, g_manage_optimize
- Post in Slack about the changeover. Communicate the timeline and how MRs will be handled.
Reach out to the Product Manager and Engineering Manager to communicate the change.
Be sure to provide any additional useful information about working with the group, including how they prefer to communicate in issues/MRs regarding reviews.
Tasks for EMs and PMs
- Add the incoming TW to team meetings and any group aliases.
- Remove the outgoing TW from team meetings and any group aliases.
- Determine the resources needed by the incoming TW to learn the stage / group features, similar to an engineer's onboarding, see Notes from Mike
Tasks for incoming technical writer
Set up coffee chats with:
- Group Product Manager (see above)
- Group Engineering Manager (see above)
Some group frontend and backend team members
@pshutsin @ahegyi @m_frankiewicz @blabuschagne @ekigbo
UX designer associated with the group:
- In the
data/stages.yml, with your new assignment.
- In the
gitlabrepository, update as needed:
- For guidance, see the doc links below
- Read the product documentation associated with your group (as identified by the group attribute in documentation pages' metadata).
Notes from Mike
- TLDR: Optimize measures customer productivity with GitLab
- Possible key future feature of GitLab. Part of Value Stream Management Consortium
- Visit the group handbook section
Read the Documentation and Direction pages linked in the handbook section for each group.
- Go to
https://about.gitlab.com/features/#groupand follow the Documentation links.
- Go to
- Key docs:
@djensendrafts a majority of docs
- Monthly: watch s_manage for the return of the monthly Kickoff video (I don't think there'll be one for 13.12)