The Configure frontend team works on the following Configure stage groups & GitLab projects:
The following people are permanent members of the Configure Frontend Team:
|Jean du Plessis||Frontend Engineering Manager, Configure|
|Mike Greiling||Senior Frontend Engineer, Configure|
|Jacques Erasmus||Frontend Engineer, Configure|
|Enrique Alcántara||Senior Frontend Engineer, Configure|
The following members of other functional teams are our stable counterparts:
|Grzegorz Bizon||Staff Backend Engineer, Serverless|
|Taurie Davis||Staff Product Designer, Configure|
|Ahmad Sherif||Site Reliability Engineer, Manage, Monitor & Configure|
|New Vacancy - Seth Engelhard (Interim)||Engineering Manager, Configure Orchestration|
|Nicholas Klick||Engineering Manager, Serverless|
|Daniel Gruesso||Product Manager, Configure:Orchestration|
|Dan Davison||Senior Test Automation Engineer, Configure|
|Evan Read||Senior Technical Writer, Manage, Verify, Configure, Growth|
|Thong Kuah||Senior Backend Engineer, Configure|
|James Fargher||Senior Backend Engineer, Configure|
|Hordur Freyr Yngvason||Backend Engineer, Configure|
|João Cunha||Backend Engineer, Configure|
|Tiger Watson||Senior Backend Engineer, Configure|
|Matt Kasa||Senior Backend Engineer, Serverless|
|Alishan 'Ali' Ladhani||Backend Engineer, Serverless|
|Alex Ives||Senior Backend Engineer, Serverless|
|Magdalena F.||Backend Engineer, Serverless|
|Viktor Nagy||Senior Product Manager, Configure:Serverless Group|
|Maria Vrachni||Senior Product Designer, Configure|
We work with both the
group::system backend engineering teams and to facilitate focus and priortization our team members are assigned to one of the two groups.
Being assigned to a group doesn't mean you will exclusively work on that groups' work.
The intention is to allow the frontend engineers to focus on a smaller part of the product and optimize their learning and time spent in meetings. We also plan to rotate team members between the groups every few months.
Current group focus:
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.
UX Ready, is it ready for frontend development.
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.
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.
The team joins the weekly Configure and Serverless team meetings, to stay informed around the issue priority and knowing when specific issues are ready for development.
Once a team member completed their assigned issues, they are expected to go to the Configure or Serverless issue boards and assign themselves to the next unassigned issue in the list that has the
workflow:ready for development labels.
The issues on the board are prioritized based on importance (the higher they are on the list, the higher the priority).
If all issues are assigned for the milestone, team members are expected to identifying the next available issue to work on based on the team's work prioritization (see below).
While backstage work is important, in the absence of prioritization the team will have a bias towards working on
feature categorized issues.
The manager will also bring to the team's attention any work that is considered important/urgent to ensure appropriate attention is given to it.
If stakeholders from the Docs or Pajamas Design System projects want an issue priortized above other work they should reach out to the manager who will in consultation with the PM make a determination as to when the work can be accommodated.