Veethika's UX transition and onboarding to `Pipeline Security`
🧩 Context
This issue is dedicated to the seamless transition of responsibilities for Veethika from Pipeline Execution
to Pipeline Security
:
- Onboard to 3 new categories
- Off-board and park
Pipeline Execution
design tasks/initiatives
MR confirming change gitlab-com/www-gitlab-com!120184 (merged)
⌚ ️ Timeline for the transition
By 15.10
- 20th feb 2023, assume new role in Pipeline Security and start the onboarding process.
📦 Boxing Pipeline Execution design initiatives
Pipeline Execution ⚙️
Off-board the categories in Category | Category direction page | Figma files |
---|---|---|
Merge trains | Youtube Link | |
Solution validation: CI/CD quota for projects | Usertesting link |
🚗 Parked tasks - only the design tasks will be parked, not development
Issue/Epic | Category | Notes | Development scheduled? |
---|---|---|---|
Merge train research | Merge train | this research would inform the changes that's to be made to gitlab#280777 | Not yet |
Solution validation: project CI/CD limits | Continuous Integration | Critical to making improvements to the proposal in gitlab#384874 | This is to be taken up by community members. Is in backlog. |
Display one date selector for CI/CD Quota page | Continuous Integration | Requires a proposal. Nothing worked on yet. | %15.11 |
Add additional permission to allow retrying of jobs on protected tags | Continuous Integration | No proposal yet. | Backlog |
MVC: Consider adding the duration of each job in the pipeline graph | Continuous Integration | can potentially be a Pipeline Authoring feature | Backlog |
cc @jheimbuck_gl ^
🗄 ️ Admin tasks
-
Clear 1:1 with PE PM -
Remove Veethika from PE Quad meetings -
Remove Veethika from PE technical meetings -
Remove Veethika from stand-ups, other geekbot
activities @carolinesimpson
🚀 Onboard to Pipeline security
📚 Learn about new categories in Pipeline Security 🔐
(Discussions in threads in this issue)
Category | Previous DRI | Category direction page | In maintenance? | Figma directory |
---|---|---|---|---|
Secrets Management | @Sunjung |
Link | No | Link |
CI variables | @Sunjung |
Link(TBD) | No | Link (After 15.9), Link (Before 15.9) |
Build Artifacts | @gdoyle |
Link | Yes | Link |
CI_JOB_TOKEN | @veethika |
Link(TBD) | No | Link |
🗄 ️ Admin tasks
-
Get added to weeklies in PS -
Regular 1:1 with PM -
Schedule coffee chats with team members -
Get added to stand-up in PS (@shampton ) -
get added to the group PS -
Please update your Zoom, Slack, GitLab profiles, as necessary - e.g. rename Verify:Pipeline Execution
toVerify:Pipeline Security
:
👩 🏫 Learning related tasks - Updated as discussion in threads progress
-
Secrets management: Read up research reports shared by Erika -
Secrets management: Understand the competitive landscape -
Secrets management: Read articles and visions(current) -
CI_JOB_TOKEN: -
CI Variables: Read previous research outcomes and category direction -
CI Variables: catch up to speed with issues in progress -
Build artifacts:
📚 Handbook changes
-
Update Jobs to be Done (JTBD) handbook page: Pipeline security JTBDs -
Deprecate Pipeline Execution UX page -
Add a Pipeline Security UX page (make changes to Pipeline Insights and customize)
💅🏽 Final checklist
The below tasks should be completed before finalizing the transition and closing this issue.
Click to expand
-
Update the title of this issue to: UX Transition for _ STAGE GROUP, GROUP, CATEGORY OR FEATURE_
. -
Assign the transition issue to yourself and your Manager. -
Optionally, add a link to the MR confirming the transition ADD LINK
-
-
Fill out the sections below with the relevant content for the stage, group, or category. -
Inform relevant counterparts, such as Product Managers and Engineering Managers, of the UX transition by pinging them in this issue. -
Optionally, schedule a sync meeting with the newly assigned DRI, their Manager, and other strategic counterparts. You can also opt for recording a walkthrough video to share with the relevant team.
-
-
Optionally, if a category or feature is being moved, transfer the JTBDs to the relevant team by updating them in the handbook. -
Communicate the change with the stage groups on Slack by sharing a link to this issue. -
*Newly Assigned DRI: When you feel comfortable, unassign the previous DRI and close this issue.