Enablement Sub-department

1. You are here:
2. Engineering
3. Development Department
4. Enablement Sub-department

Maintained by:

Chun Du

@cdu1

On this page

• Vision
• Mission
• Fiscal Year 2022 Direction
• Sub-department Members
• All Team Members
  • Database
  • Distribution
  • Geo
  • Memory
  • Global Search
• Business Continuity - Coverage and Escalation
• Stable Counterparts
• How We Work
  • Professional Development
  • Combined Team
  • Dogfood Roadmap in Planning
  • Long Standing Merge Requests
  • Increasing Efficiency through Documenting Decisions
• Software Subscriptions
• Common Links

Vision

Offer enterprise-grade operational experience of GitLab products from streamlined deployment and maintenance, disaster recovery, secure search and discoverability, to high availability, scalability, and performance.

Mission

Enablement focuses on improving our capabilities and metrics in the following areas:

• Database
• Distribution
• Geo
• Memory
• Global Search
• Sharding

Fiscal Year 2022 Direction

• Grow feature maturity to improve enterprise experience and readiness
• Build and enhance features and integrations to expand market opportunities
• Solidify foundation for smooth operations, high availability, and high scalability of SaaS offerings

For more details, refer to the Enablement Sub-department Direction.

Sub-department Members

The following people are permanent members of the Enablement Sub-department:

All Team Members

The following people are permanent members of teams that belong to the Enablement Sub-department:

Database

Distribution

Geo

Memory

Global Search

Business Continuity - Coverage and Escalation

The following table shows who will provide cover if one or more of the Enablement Engineering management team are unable to work for any reason.

If an Engineer is unavailable the person providing Issues/MRs coverage will reassign open issues and merge requests to another engineer, preferably in the same group.

Some people management functions may require escalation or delegation, such as BambooHR and Expensify.

This can be used as the basis for a BCP Communication Plan and Role Assignments, as well as a general guide to Enablement Engineering continuity in the event of one or more team members being unavailable for any reason.

Stable Counterparts

The following members of other functional teams are our stable counterparts:

How We Work

Professional Development

1. Conference, meetup, and training: To request budget for these career development events, please refer to budget application for professional development.
2. Career development plan: It is recommended that the manager and the individual collaboratively develop a career development plan and discuss progress via career talks regularly. Here is an Enablement sub-department career development plan template.
3. Promotion: An individual is ready for promotion when both the individual and the manager reach consensus that the individual is performing job competencies at the next level of career ladder according to the Engineering Career Framework.
   • Managers, when proposing a promotion for your team member use the PeopleOps promotion document template.

Combined Team

Based on the scale of frontend engineering in Enablement sub-department, the Combined Team model is being experimented where both Frontend and Backend Engineers report to a single Engineering Manager. It's believed that the combined team model enables higher efficiency for the situation of Enablement and the experiment is subject to continuous review. The team will return to functional model by establishing a dedicated frontend engineering team when the frontend engineering team reaches the manager to individual contributor ratio guideline.

Dogfood Roadmap in Planning

To enhance the overview of team direction, all Enablement development teams use Epics to organize projects and dogfood the Roadmap feature to communicate short- and mid-term product development roadmap, although each team customizes their usage such as applying specific labels. Examples:

• Advanced Search roadmap
• Geo roadmap
• Memory roadmap
• Database roadmap

Long Standing Merge Requests

• Engineering managers and team members will periodically review the long standing MRs and decide appropriate actions for MRs lasting more than 30 days.
• From time to time, MRs are created without intention to merge, such as research spikes, novel ideas, etc. In this case, always prefix the MR subject line with WIP. These MRs exempt from the above review.

Increasing Efficiency through Documenting Decisions

Documenting development decisions is another way to increase efficiency. These decisions can be either in an issue explicitly stating that we will not work on this issue, the product category page for your group or a more formal decision log in your group's section of the handbook. Whatever your chosen desitination, each group should try to maintain a single source of truth for the decisions. A recent example (without mentioning specific product name) had a development team researching an open source product to accelerate development time only to find out later that this research had been previously completed and the product was eliminated from consideration. If this decision had been discoverable via documentation or issue it would have saved precious development time.

We have started creating decision logs to benefit our internal development team as well as our greater GitLab community. It is up to each group to determine the best location for decision logs to be discoverable. For example, the Database team has a decision log for Sharding GitLab with CitusDB in the Enablement/Database section of the handbook and a decision log for the Sharding Working Group in the working group section of the handbook.

For issues, a clear decision is when an issue is successfully closed. However, if an issue is closed because we "won't do it" it may not be immediately clear. We are adopting the ~won't do label for those issues. Often the pattern is to just stash these issues in the ~backlog. This can be misleading to those watching the issue and frustrating to the original author, especially if they are a community contributor. When we apply a won't do label to an issue, we are making a clear decision. If there is no pushback on the won't do label then we made the right decision. If there is pushback and we need to reprioritize the issue, then that is a good outcome as well.

Software Subscriptions

The Enablement teams leverage the following software or SaaS services to deliver our products. For general information of procurement, checkout the procurement team page. For procurement questions, bring to #procurement. To make new Purchase Order (PO), create a new procurement issue.

Common Links

• Issue Boards
  • Database Milestone Board
  • Distribution - Deliverable Board
  • Geo Kanban Board
  • Memory Milestone Board
  • Global Search Milestone Board
• Slack Channels
  • Enablement Sub-department #s_enablement
  • Database team #g_database
  • Distribution team #g_distribution
  • Geo team #g_geo
  • Memory team #g_memory
  • Global Search team #g_global_search