Transition: ~group::access to Evan Read
Last day for @mjang1 = May 3
- Stage/group being transitioned: devopsmanage ~"group::"
- Current technical writer: @mjang1
- Incoming technical writer: @eread
- Reassignment milestone:
Tasks for current technical writer
-
Invite the incoming TW to the stage and group Slack channels. - Channel list: s_manage, g_manage_access
-
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. -
PM: @mushakov
(in transition to another group) -
EM: @lmcandrew
@dennis
-
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. - Meeting list:
-
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 (Listed above) -
Group Engineering Manager (Listed above) -
Some group frontend and backend team members - Suggestions:
@dblessing
@serenafang
@peterhegman
@manojmj
- Suggestions:
-
UX designer associated with the group (@dmoraBerlin ) -
Key support engineer ( @cynthia
is essentially an SME for much of ~"group::access" )
-
- In the
www-gitlab-com
repository, update:-
data/stages.yml
, with your new assignment.
-
- In the
gitlab
repository, update as needed:-
.gitlab/CODEOWNERS
- For guidance, see the doc links below
- Note: I have not updated CODEOWNERS, in most cases. Others have, based on doc metadata.
-
-
Read the product documentation associated with your group (as identified by the group attribute in documentation pages' metadata).
Notes from Mike
-
Read the Documentation and Direction pages linked in the handbook section for each group. - https://about.gitlab.com/direction/manage/auth/
- Go to
https://about.gitlab.com/features/#group
and follow the Documentation links.
- Roadmap: https://about.gitlab.com/direction/manage/auth/
-
Key docs: -
SSH (most popular): https://docs.gitlab.com/ee/ssh/ -
SAML SSO for GitLab.com groups: https://docs.gitlab.com/ee/user/group/saml_sso/, including subpages -
Permissions - Related open issue. Automation should be possible, as we know the code source for most of the permissions
-
-
Specifications. Several specs form the foundation of ~"group::access" , including -
OAuth 2: https://oauth.net/2/ -
OpenID Connect (TLDR: adds ID tokens to OAuth 2): https://openid.net/specs/openid-connect-core-1_0.html -
SCIM: http://www.simplecloud.info/ -
(less needed) SAML: http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html In some cases, you may need to set up links to relevant portions of each spec.
-
Issues to transfer:
Edited by Evan Read