Skip to content

[UX] Custom Models Beta to GA contingency flows

Problem

Integrating the proposed Custom models designs into the unified GitLab Duo page is challenging and risky within the 17.5 milestone timeframe. There are several MRs in flight (please see #472637 (comment 2125508493) for a breakdown of ongoing work). Now that we are getting close to the 17.5 cutoff, we should explore an alternative approach for moving forward with Custom models functionality that is feasible before the end of the milestone as we officially move into Beta. Its also important to note that Custom models will remain in Beta for at least another milestone before GA.

Proposals

Option 1: Dedicated Custom Models Page

Option 2: Rename and Repurpose Existing Group

image.png

image.png
  • Remove the "AI-powered features" group in the admin nav menu.
  • Create a new dedicated "Custom models" page.
  • This new page would house all Custom model functionality, similar to what would have been on the unified page.
  • Rename the "AI-powered features" group in the admin nav menu to "Custom models"
  • Maintain separate pages for self-hosted models and AI-powered features.1

My recommendation is Option 1. We already have an MR in flight to handle this Vue tabbed approach, and it is the cleaner of the two options. This is only a recommendation, and I'm open to feedback from all.

2024/09/09 –– Update

It was decided that we should pursue Option 1 within %17.5

Edited by Tim Noah