Support the seamless integration between GitLab and 3rd party products and services, expanding GitLab's market opportunities by empowering developers to contribute.
The Ecosystem team is responsible for designing, building, and maintaining:
More information about the Ecosystem Backend Team can be found on the Ecosystem Backend Team page.
|Matt Nohr||Backend Engineering Manager, Ecosystem|
|Luke Duncalfe||Backend Engineer, Ecosystem|
|Alex Kalderimis||Senior Backend Engineer, Ecosystem|
|Markus Koller||Backend Engineer, Ecosystem|
|Arturo Herrero||Senior Backend Engineer, Ecosystem|
|Andy Soiron||Senior Backend Engineer, Ecosystem|
The following members of other functional teams are our stable counterparts:
|Patrick Deuley||Senior Product Manager, Ecosystem|
|Libor Vanc||Senior Product Designer, Ecosystem:Integrations|
|Amy Qualls||Senior Technical Writer, Create (Source Code, Code Review, Editor, Ecosystem), Growth (Activation, Adoption, Conversion, Expansion, Product Intelligence)|
|Mike Greiling||Senior Frontend Engineer, Ecosystem|
|Lukas Eipert||Engineering Manager, Ecosystem|
|Ash McKenzie||Staff Backend Engineer, Ecosystem|
|Justin Ho||Senior Frontend Engineer, Ecosystem|
|Tom Quirk||Frontend Engineer, Ecosystem:Integrations|
Whenever possible, we prefer to communicate asynchronously using issues, merge requests, and Slack. However, face-to-face meetings are useful to establish personal connection and to address items that would be more efficiently discussed synchronously such as blockers.
The Ecosystem group participates in async daily standups in the #g_create_ecosystem-standup slack channel. The purpose is to give every team member insight into what others are working on so that we can identify ways to collaborate as well as foster relationships within the team. We use the geekbot slack plugin to automate our async standup, following the guidelines outlined in the Geekbot commands guide.
Participation is optional but encouraged.
We currently ask questions depending on the day of the week:
The random questions come from Geekbot's "Pizza Topping" category. This is a list of almost 200 questions that will be randomly picked each week. Geekbot provided the initial list, but we could add/remove questions as well. The questions include fun/social topics such as:
We use the following issue boards to prioritize and track our work.
As an engineering organization, we have defined a default ratio for the number of Staff Engineers per team. While this makes sense for most teams, the Create:Ecosystem team has a slightly different ratio due to the nature of the team.
Exception Ratio: 3 Staff Engineers per Team
Justification: The Ecosystem team is focused on many very distinct areas and needs expertise in each. This is closely aligned to the default gearing ratio with the addition of one staff engineer to focus on the GDK. The main staff-level focus areas would be on: