We're the Foundations team and we are part of the Manage Stage.
This page is the shared team page for our Engineers, Product Designers, and Product Manager!
We hope it's a good entry point to learn more about who we are and what we do.
|Christen Dybenko||Senior Product Manager, Manage:Foundations|
|Sam Beckham||Engineering Manager, Manage:Foundations|
|Lukas Eipert||Senior Frontend Engineer, Manage:Foundations|
|Mark Florian||Staff Frontend Engineer, Manage:Foundations|
|Olena HK.||Senior Frontend Engineer, Manage:Foundations|
|Paul Gascou-Vaillancourt||Senior Frontend Engineer, Manage:Foundations|
|Scott de Jonge||Senior Frontend Engineer, Manage:Foundations|
|Thomas Hutterer||Senior Backend Engineer, Manage:Foundations|
Design System (Direction Page)
We are currently focused on integrating our design system, Pajamas, into the GitLab product.
We perform an accessibility audit on each component and make sure that our implementations in GitLab UI and GitLab match the desired user experience, guidelines, and visual design.
The Foundations team does the preparation work necessary so that other Engineers at GitLab and members from the wider community can help out with these efforts.
Do you want to contribute? Please see this issue for a good entry point.
To get in touch with the Foundations team,
it's best to create an issue in the relevant project (typically GitLab, Pajamas or GitLab UI) and
~"group::foundations" label, along with any other appropriate labels.
Then, feel free to ping the relevant Product Manager and/or Engineering Manager.
For more urgent items or if you are unsure who to ask, ping
@gitlab-org/manage/foundations or use #g_manage_foundations on Slack (internal only).
In general, we use the standard GitLab Product Development Flow. Here are some specific workflows we use:
Next Upby the PM
workflow::planning breakdownbut could appear in other workflows if weighting is a topic of conversation
twice a release), engineers review unweighted
workflow::ready for development, and set its milestone to a specific release, or
We use a Fibonacci scale and in terms of complexity, we use this table from Practical Fibonacci.
Foundations weighting scale:
Here are some resources team members can use for employee development:
(Sisense↗) We also track our backlog of issues, including past due security and infradev issues, and total open System Usability Scale (SUS) impacting issues and bugs.
(Sisense↗) MR Type labels help us report what we're working on to industry analysts in a way that's consistent across the engineering department. The dashboard below shows the trend of MR Types over time and a list of merged MRs.