AI Related Stage/Group Changes
Why is this change being made?
Changes in bold
Review app: https://ai-powered-stage.about.gitlab-review.app/handbook/product/categories/#data-science-section
- Data Science Section sectiondata-science
- AI-powered Stage - split and new stage from ModelOps devopsai-powered
- AI Model Validation group - renamed from 'AI Assisted' groupai model validation
- AI Evaluation category - Newly created Category:AI Evaluation
- AI Research category - Future focus Category:AI Research
- AI Framework group - formerly AI Enablement groupai framework
- AI Abstraction Layer category category:AI Abstraction Layer
- Duo Chat group - promoted from category groupduo chat
- Duo Chat category Category:Duo Chat
- AI Model Validation group - renamed from 'AI Assisted' groupai model validation
- ModelOps Stage devopsmodelops
- MLOps group groupmlops
- DataOps group groupdataops
- AI-powered Stage - split and new stage from ModelOps devopsai-powered
- Dev Section sectiondev
- Create Stage devopscreate
- Editor Extensions group - promoted from category groupeditor extensions
- Editor Extensions category - moved from Code Review group Category:Editor Extensions
- Code Creation group - newly created groupcode creation
- Code Suggestions category - newly moved Category:Code Suggestions
- Editor Extensions group - promoted from category groupeditor extensions
- Create Stage devopscreate
Approvals
-
Chief Product Officer @david -
The Director of Product relevant to the affected Section(s) -
The Director of Engineering relevant to the affected Section(s) -
Director of Product Design @vkarnes
Awareness
- Chief Technology Officer @joergheilig
- VP of Development @clefelhocz1
- Infrastructure & Quality @meks @marin @vincywilson @dcroft
- Engineering Productivity @gl-quality/eng-prod
- The Product Marketing Manager relevant to the stage group(s) @laurenaalves
- Director, Technical Writing @susantacker
Process for Stage Changes
https://about.gitlab.com/handbook/product/categories/#changes
-
Add notifications for relevant folks -
Label changes -
Team Link and slack channel changes -
@mention
group updates -
Triage bot changes
Author Checklist
-
Provided a concise title for this Merge Request (MR) -
Added a description to this MR explaining the reasons for the proposed change, per say why, not just what - Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
-
Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI) - If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
Maintained by
section on the page being edited - If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
- The when to get approval handbook section explains the workflow in more detail
- If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR - If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.
Edited by Taylor McCaslin