Enable developers to reliably manage infrastructure, services, and applications in production environments.
We are focused on one of the major themes of GitLab's one year product plan:
Compete in Ops: Enable today's modern best-practices in operations without the burden of specialized teams, multiple tools and heavy workflows.
We will focus on driving dogfooding of Monitoring and Configuration features within GitLab teams in order to accelerate feedback and demonstrate our capabilities can be relied on for critical production use cases such as running gitlab.com.
More details about Ops Section direction and plans:
The following people are members of the Ops Section:
|Joanna Shih||Quality Engineering Manager, Ops & CI/CD|
|Sam Goldstein||Director of Engineering, Ops|
|Kenny Johnston||Sr. Director of Product Management, Ops|
|Jason Yavorska||Director of Product Management, CI/CD|
|Chrissie Buchanan||Content Marketing Manager, Ops|
|Lorie Whitaker||Senior UX Researcher, Release and Verify & Enablement|
|Andrej Kiripolský||UX Researcher, Ops and Package|
|Saumya Upadhyaya||Sr Product Marketing Manager|
|Kevin Chu||Group Manager of Product Management, Configure & Monitor|
Groups within the Ops Sub-department follow an async planning process to coordinate planning and discussion between members of the group. This process is related to the general GitLab Product Development Timeline process and adds additional practices we've found useful.
The goals of this process are to ensure we:
Teams can customize this process to meet needs specific to their team as long as the customizations are documented on their team handbook page.
Planning issue templates follow a format similar to this. Teams can add additional headings specific to their team.
### <Section> Planning Board <!-- link to your sections planning board --> ### Goals for the milestone: <!-- Replace with the high-level goals to be achieved by the end of the milestone --> * Goal 1... * Goal 2... ### Scope of Work for Engineering <!-- List of issues in priority order go in this table Use :white_check_mark: for Frontend and/or Backend if there is work for that team --> | Priority | Issue | Category | Notes | Frontend | Backend | |----------|-------|----------|-------|----------|---------| | 1 | | | | | | | 2 | | | | | | ### Scope of Work for Engineering Debt <!-- What work of Engineering Debt from the past will Engineering be focused on? - Should be at least 1 Issue per Milestone - The more we can handle the better... balance --> | Issue | When it should be ready | |-------|-------------------------| | | | ### Scope of New Work for UX <!-- What new work will UX be focused on? - Design based on research in previous Milestones - Research to help inform designs for future Milestones - Research to validate previously designed UI --> | Issue | When it should be ready | |-------|-------------------------| | | | ### Scope of Work for UX Debt <!-- What work of UX Debt from the past will UX be focused on? - Should be at least 1 Issue per Milestone - The more we can handle the better... balance --> | Issue | When it should be ready | |-------|-------------------------| | | | ### Scope of Work for Software Engineers in Test <!-- What work will Testing be focused on? --> | Issue | Investigates/Tests | Due on | |-------|--------------------|--------| | | | | /label <!-- add section label here --> ~"Planning Issue"
Team Planning Issue Templates:
All the planning issues are viewable on the Ops Section - Issue Planning (Issue Board)
The Ops Sub-department is holding a Virtual Pizza Party to celebrate our collective achievements in May. Specifically these include:
These are impressive results and we will take a moment to celebrate everyone's hard work contributing to them.
Members of the Ops Sub-department and their stable counterparts can expense up to $25 in the month of June for pizza (or food items of your choice). We will also hold several Pizza Party meetings where team members can (optionally) enjoy their pizza with their colleagues and a slack channel where team members can (optionally) share photos of themselves celebrating. Expenses must be incurred in the month of June 2020 and should be submitted through the normal expense process, with a description of June 2020 Ops Sub-department Virtual Pizza Party.
The slack channel #ops-virtual-pizza-party-celebration is created for you to (optionally) share photos with your teammates of you celebrating May's accomplishments.
Pizza Party meetings where team members can (optionally) enjoy their pizza with their collegues.