This meeting record transcript covers various topics related to the secure and govern growth and data science teams at GitLab. It discusses organizational changes, such as the renaming of the Model Ops section to Data Science, which will include the existing Model Ops groups and the Anti-Abuse group. Updates on talent assessment, FedRAMP compliance, and approval rules are also provided. The meeting touches on improving the merge request (MR) rate, celebrating team achievements, and gathering feedback on the development vision and mission. Additionally, there is a discussion about maintainers and the use of the review-or-roulette tool. Lastly, the team celebrates the birth of a new family member.
【チャプター】
00:02:24 Organizational Changes
The meeting discusses several organizational changes within GitLab. The Model Ops section is being renamed to Data Science, which will include the existing Model Ops groups (Applied ML Ops and Data Ops) and the Anti-Abuse group. There are plans to split the Anti-Abuse group into two groups in the future. Additionally, the secure and govern growth team is considering a name change to 'Enrichment' to better reflect their role in enhancing other areas.
00:04:41 Talent Assessment and FedRAMP Compliance
Updates are provided on the upcoming talent assessment process, which will be conducted through Workday between mid-October and December. The team is advised to continue using the existing Google Docs for self-evaluations and manager work until Workday access is available. Regarding FedRAMP compliance, any security issues with a CVE (Common Vulnerabilities and Exposures) associated with them must have a remediation plan, even if they are false positives. This has led to discussions about how to handle security findings in the commercial versions of the analyzer.
00:17:31 Approval Rules and Merge Request (MR) Rate
The team discusses the impact of the new approval rules on segregation of duties. Anecdotally, some team members have realized the need for additional approvals, but it does not seem to be slowing down the process significantly. The meeting also covers efforts to improve the MR rate, such as implementing weekly refinement meetings, breaking down work into smaller pieces, and using the 'Looking Forward' section in the planning feature for refinement.
00:20:21 Team Celebrations and Development Vision
The team discusses the idea of adding announcements for work anniversaries and new hires to the meeting template, as well as a section for thanks and praise. This is seen as a way to celebrate wins and improve team cohesion. Additionally, the team is encouraged to provide feedback on the development vision and mission being brainstormed within the development department.
00:25:42 Maintainers and Review-or-Roulette Tool
There is a discussion around the use of the review-or-roulette tool, which is intended to track if there are enough maintainers for a given project. The team members share their perspectives on why they may not have set up maintainers in the tool, as some projects have a small number of dedicated engineers working on them. The team acknowledges the need to ensure that maintainer information is accurately reflected in the appropriate sources.
【行動項目】
00:20:21 Consider adding announcements for work anniversaries and new hires to the meeting template, as well as a section for thanks and praise, to celebrate wins and improve team cohesion.
00:25:08 Provide feedback on the development vision and mission being brainstormed within the development department.
00:27:50 Ensure that maintainer information for projects is accurately reflected in the appropriate sources, such as the engineering projects page and individual team members' YAML files in the handbook.
