FY23-Q2 Shared OKR Tracking Issue: Pajamas migrations of 200 components
This issue serves as an MVC to have one SSOT for tracking of work needed to complete Pajamas migrations related shared OKRs between Product and Engineering. Please share any feedback you have in FY23-Q2 feedback issue
Related KRs / Links
- Engineering KR in Ally
- UX/Design KR in Ally
- Product KR in Ally
- Progress dashboard: https://gitlab-org.gitlab.io/frontend/epic-burndown-charts/fy23-q2/
- Entry point for ICs / contributors: https://gitlab.com/gitlab-org/ecosystem-stage/team-tasks/-/issues/140
- Google Sheet determining issue counts: https://docs.google.com/spreadsheets/d/1L42ecYRY39_wNkAon7_1xgEgq9S1TWnG_qWQbFimelY/edit#gid=623540269
How to engage with this issue:
-
Product management: If you have been tagged below, it's because there's an ask for your group to be aware of Q2 Pajamas migrations as part of a Shared OKR between Product and Engineering teams. For context, please review Q2: do 200 component migrations, paying close attention to information for product managers.
- Then, please review the Q2 Pajamas migrations tracking dashboard to see all the proposed Q2 work, statuses, and issues your team's front-end engineers will pick up as tech debt as time allow.
- After reviewing issues assigned to your team, check off PM aware. Please note there is no specific actions required from you to prioritize, as their work has been assigned based on front-end engineering capacity and meant to be picked up by engineers as time allows throughout the quarter
- If you are not aligned with the work identified, please start a discussion thread in this issue to resolve by recommending another issue, solution, etc. mentioning
@leipert
- If you and your team decide you will not be prioritizing the work, please insert "not doing" in front of PM aware and leave it unchecked. It is recommended you also start a comment thread, tagging in your manager and
@leipert
for awareness and alignment. - If at any time you have to de-prioritize or block the Engineering team from working on these issues, please ping
@fseifoddini
with an update and collaborate to determine if it affects the PM contribution to the KR.
- UX/Design: Please collaborate on any discussions as needed in this issue
-
Development: If you have been tagged below, it's because Frontend Engineers on your team are asked to contribute to the Q2 Pajamas migration effort. For context review, please review Q2: do 200 component migrations, paying close attention to information for Engineering managers.
- After reviewing this info, please check off the corresponding EM aware checkbox and raise the component migration efforts in your 1:1 with Engineers, so that they consider picking some up.
- If you are not aligned with the work identified, please start a discussion thread in this issue to resolve by recommending another issue, solution, etc. mentioning
@leipert
sectiondev)
Dev (-
@ogolowinski
PM aware -
@mushakov
PM aware
Create:Code Review/Source Code
- Component migration target: 16
-
groupcode review groupsource code (Note: Grouped together,
because all Frontend Engineers report to
@andr3
) -
PM aware @phikai
-
PM aware @tlinz
-
EM aware @andr3
Create:Editor
- Component migration target: 10
- ~"group::editor"
-
PM aware @ericschurter
-
EM aware @oregand
Ecosystem:Foundations
- Component migration target: 18
- groupfoundations
-
PM aware @cdybenko
-
EM aware @leipert
Ecosystem:Integrations
- Component migration target: 12
- ~"group::integrations"
-
PM aware @g.hickman
-
EM aware @dsatcher
Manage
- Component migration target: 24
- ~"group::authentication and authorization", groupcompliance, ~"group::import", groupoptimize and ~"group::workspace" grouped together, because we grouped it last quarter as well.
-
PM aware @hsutor
-
PM aware @stkerr
-
PM aware @iganbaruch
-
PM aware @hsnir1
-
EM aware @m_gill
-
EM aware @mksionek
-
EM aware @dennis
-
EM aware @jarka
-
EM aware @wortschi
-
EM aware @blabuschagne
Plan
- Component migration target: 10
- groupproduct planning groupproject management
-
PM aware @gweaver
-
PM aware @mushakov
-
EM aware @donaldcook
sectionenablement)
Enablement (- Component migration target: 2
- groupgeo groupglobal search (grouped together as we don't have many enablement Engineers)
-
PM aware @sranasinghe
-
PM aware @JohnMcGuire
-
EM aware @mkozono
-
EM aware @changzhengliu
sectionfulfillment
Fulfillment- Component migration target: 56
- ~"group::fulfillment" groupprovision ~"group::purchase" grouputilization (grouped together because we also did group last quarter)
-
PM aware @tgolubeva
-
PM aware @ofernandez2
-
PM aware @doniquesmit
-
EM aware @rhardarson
-
EM aware @jameslopez
-
EM aware @csouthard
sectionops)
Ops (-
EM aware @sgoldstein
-
EM aware @cheryl.li
Rest of Ops / Configure
- Component migration target: 6
- ~"group::configure" / ~"group::package" ~"group::release"
- Note: Just pinging configure, as Package and Release have a lot of ~SUS issues to take care of this quarter
-
PM aware @nagyv-gitlab
-
EM aware @nmezzopera
Verify
- Component migration target: 4
- grouppipeline authoring / grouppipeline execution grouprunner ~"group::pipeline insights"
- Note: Just pinging pipeline authoring, as Package and Release have a lot of ~SUS issues to take care of this quarter
-
PM aware @dhershkovitch
-
EM aware @samdbeckham
sectionsec)
Sec (-
EM aware @whaber
Sec: Threat Insights and Container Security
- Component migration target: 32
- ~"group::container security" groupthreat insights
- Note: Last quarter we had a shared OKR for all of Secure / Growth / ModelOps, but I was asked to split this out to have better accountability.
-
not doing PM aware @sam.white
-
PM aware @matt_wilson
-
EM aware @nmccorrison
Secure: Analyzer Groups
- Component migration target: 24
- groupcomposition analysis groupdynamic analysis groupstatic analysis
- Note: Last quarter we had a shared OKR for all of Secure / Growth / ModelOps. Chose to combine the analysis groups because of the number of Engineers
-
PM aware @connorgilbert
-
PM aware @sam.white
-
PM aware @derekferguson
-
EM aware @twoodham
-
EM aware @sethgitlab
-
EM aware @gonzoyumo
sectiongrowth
ModelOps ~"section::modelops" & GrowthGiven that there are not enough Frontend Engineers in these teams, we are not defining any targets
Edited by Torsten Linz