Q2: do 200 component migrations
Development has an OKR (ally TBA) to migrate 200 outdated components to Pajamas. We had a similar OKR last quarter (see: https://gitlab.com/gitlab-org/ecosystem-stage/team-tasks/-/issues/110).
TL;DR for Engineers
We are continuing with the open issues that carried over from last quarter and are continously creating new issues
Pick up any of these issues today! Don't delay, they're going fast!
You can grab any issue from the link above. They are ready to be implemented, more issues are going to be ready over time. Feel free to assign yourself or team mates to any of them.
We are also looking to update labels on issues so that they have the corresponding group labels, but everyone should be able to chime in on any issue! Older parts of the code base are going to be disproportionately affected.
Information for Product Managers
If you are a PM, you might not have heard and/or participated in this effort yet. You might have questions like "how do I schedule these" or "how do I track the work"?
A single component migration is rather small and should not take too much time. Migration issues are prepared by the Foundations team and their epics contain well-written instructions (example) Most of the time is often spent tracking down the component in the code base and creating screenshots.
The migration issues disproportionally affect older parts of the code base and/or features like admin settings that are not necessarily owned by one team. In order to distribute the work, we we are asking every team to chip in proportionally to the amount of Frontend Engineers they have. For this reason, some of the teams that don't have many Frontend Engineers, were grouped together on the stage or section level.
Usually Engineers pick these issues up themselves. Most issues are labeled with groupfoundations. Please communicate with your Engineering Managers and Frontend Engineers on whether you want to re-label issues with your group / stage in order to track it directly in issue boards, etc.
You can use this Dashboard to see the status quo of your teams/sections/groups contributions: https://gitlab-org.gitlab.io/frontend/epic-burndown-charts/fy23-q2/#group-stats.
If you have any questions, please open up a discussion in this issue and tag @leipert.
If you want to participate yourself, please contribute, for example on the next Pajamas Migration Day
Information for Engineering Managers
Most Engineering Managers with Frontend Engineers should know this OKR from last quarter.
We have reduced the amount of components from 300 to 200 this quarter, in order to give the Foundations team a little more breathing room for research and improving tooling in order to make future migrations even more efficient.
There is a second OKR around severity1 and severity2 SUS issues. In order to not overwhelm teams with a lot of those, some magic calculation has happened to identify how many issues each team should do and y'all have been pinged in discussions below.
How did we arrive at the component numbers per team:
f = Number of Frontend Engineers in a team
s1 = Number of SUS issues per team
s2 = Number of SUS issues per team
IPE = 6 issues per engineer
migration_count = (f * 6 issues per engineer) - (s1 * 6) - (s2 * 4)
example: 5 Engineers, 2 SUS S1 issues and 1 SUS S2 issues
migration_count= (5 engineers * 6 issues per engineer) - (2 * 6) - (1 * 4) = 14 issues
This seems fair, as SUS issues are likely to have some Backend component to them as well.
You can always check your teams progress here: https://gitlab-org.gitlab.io/frontend/epic-burndown-charts/fy23-q2/#group-stats.
Status quo of components
Expand here
Ping any of the folks below if you have questions regarding one of the specific components
DRI | Component | Status | Progress |
---|---|---|---|
@leipert | All below | --- | |
@markrian | Tabs (gitlab-org&988) | Ready for migration | |
@markrian | Badges (gitlab-org&983 (closed)) | Ready for migration | |
@ohoral | Modals (gitlab-org&1096) | Ready for migration | |
@mikegreiling / @markrian / @ohoral | Dropdowns (gitlab-org&1059) | Research partly done | |
@leipert | Segmented Controls (gitlab-org&1054) | Research done | |
TBA | Alerts (gitlab-org&996) | Research pending | |
TBA | Spinner (gitlab-org&1030) | Research pending | |
TBA | Accordion (gitlab-org&1172) | Research pending | |
TBA | Avatars (gitlab-org&1034) | Research pending |