For an understanding of where this team is going take a look at the product vision.
As a member of the Ops Section you may also like to understand our overall vision.
The Configure Orchestration group is responsible for developing Ops focused features of GitLab that relate to the "Configuration" and "Operations" stages of the DevOps lifecycle. These refer to the configuration of infrastructure as well as running applications that are deployed via GitLab.
This team is currently building out more features for our Kubernetes integration including the Auto DevOps feature set and making it easier for GitLab users to make the most of Kubernetes and DevOps best practices.
As per the product categories this team is responsible for building out new feature sets that will allow GitLab users to easily make use of the following modern DevOps practices:
We work collaboratively and transparently and we will contribute as much of our work as possible back to the open source community.
|New Vacancy - Nicholas Klick (Interim)||Engineering Manager, Configure:Orchestration|
|Thong Kuah||Senior Backend Engineer, Configure:Orchestration|
|James Fargher||Senior Backend Engineer, Configure:Orchestration|
|Hordur Freyr Yngvason||Backend Engineer, Configure:Orchestration|
|João Cunha||Backend Engineer, Configure:Orchestration|
|Tiger Watson||Senior Backend Engineer, Configure:Orchestration|
|New Vacancy - Clement Ho (Interim)||Frontend Engineering Manager, Configure|
|Mike Greiling||Senior Frontend Engineer, Configure|
|Jacques Erasmus||Senior Frontend Engineer, Configure|
|Enrique Alcántara||Senior Frontend Engineer, Configure|
|Emily Ring||Frontend Engineer, Configure|
The following members of other functional teams are our stable counterparts:
|Taurie Davis||Staff Product Designer, Configure|
|Daniel Gruesso||Product Manager, Configure:Orchestration|
|Dan Davison||Senior Software Engineer in Test, Configure:Orchestration|
|Evan Read||Senior Technical Writer, Manage, Verify, Configure, Growth|
|Viktor Nagy||Senior Product Manager, Configure:System Group|
|Maria Vrachni||Senior Product Designer, Configure|
We use planning issues to work out the planning for the next milestone asynchronously.
Example planning issue: https://gitlab.com/gitlab-org/configure/general/issues/6
Our goal is to move towards a continuous delivery model such that the team completes tasks regularly and keeps working off of a prioritized backlog of issues and as such we default to team members self-scheduling their work:
workflow:ready for developmentcolumn.
workflow:ready for developmentissue.
In addition to the self-scheduling of feature development, the manager will from time-to-time assign bugs, or other work deemed important, directly to a team member.
Team members should use their best judgment to determine whether to assign the first review of an MR based on the DangerBot's suggestion or to someone else on the team. Some factors in making this decision may be:
Our team follows the GitLab workflow guidelines for working in teams.
Given a reasonable sized issue, that requires UX, frontend and backend work, the preferred way to collaborate on the issue is as follow:
workflow::ready for development, backend is usually able to start working on the issue.
The above is a guideline and clear communication should be preferred over process to ensure the best collaboration strategy on an issue. For example on smaller issues, or where the frontend component of the work is minor, it may be feasible to work on the same branch.
Read our specific GDK instructions on how to develop features for Auto DevOps.