>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3577731. --> Reported by: [breidert](https://www.drupal.org/user/135619) >>> <p>[Tracker]<br> <strong>Update Summary: </strong>[One-line status update for stakeholders]<br> <strong>Check-in Date: </strong>MM/DD/YYYY<br> <strong>Additional Collaborators: </strong><br> <em>Metadata is used by the <a href="https://www.drupalstarforge.ai/" title="AI Tracker">AI Tracker.</a> Docs and additional fields <a href="https://www.drupalstarforge.ai/ai-dashboard/docs" title="AI Issue Tracker Documentation">here</a>.</em><br> [/Tracker]</p> <h2>Summary</h2> <p>This meta issue tracks the preparation and execution of migrating the AI Initiative projects from Drupal.org's legacy issue queue to GitLab. The goal is to align workflows, prepare projects, and coordinate the migration with all project managers &mdash; ideally completing preparation within the current sprint and executing the migration around DrupalCon Chicago.</p> <h2>Background</h2> <p>A planning meeting was held with the Drupal.org infrastructure team to review the migration process in detail. The process was walked through end-to-end, existing migrated projects were examined as reference points (e.g. <a href="https://git.drupalcode.org/project/gitlab_templates/-/issues">https://git.drupalcode.org/project/gitlab_templates/-/issues</a>), and no blockers were identified. The migration can proceed once timing is agreed upon.</p> <h3>Migration process</h3> <p>Migrating a project to GitLab is straightforward: it is triggered by running a single Drush command and takes approximately <strong>1 hour per project</strong>. Once migrated, the project's issues and merge requests are managed entirely within GitLab.</p> <h3>Contribution credits</h3> <p>Drupal.org contribution credits continue to work after migration. A bot monitors GitLab issues and automatically posts comments linking back to Drupal.org contribution records, so attribution can be assigned in the usual way. Example: <a href="https://git.drupalcode.org/project/gitlab_templates/-/issues/3572376#note_710310">https://git.drupalcode.org/project/gitlab_templates/-/issues/3572376#note_710310</a></p> <h3>Issue management</h3> <p>Issues can be viewed both at the <strong>individual project level</strong> and at the <strong>group level</strong>, which provides a unified view across all projects in the AI Initiative. This makes it possible to manage sprints, filter by label, and track work across modules in a single board &mdash; without leaving GitLab. Full GitLab project management functionality is available, including milestones, labels, issue boards, epics, and merge request workflows. Example group-level view: <a href="https://git.drupalcode.org/groups/project/-/issues?sort=created_date&amp;state=opened&amp;label_name%5B%5D=state%3A%3Artbc&amp;first_page_size=20">https://git.drupalcode.org/groups/project/-/issues?sort=created_date&amp;state=opened&amp;label_name%5B%5D=state%3A%3Artbc&amp;first_page_size=20</a></p> <p>Timing is dependent on Drupal.org infrastructure team availability to respond quickly if anything requires attention post-migration. The earliest realistic target is <strong>DrupalCon Chicago</strong>.</p> <h2>Projects to migrate</h2> <ul> <li><a href="https://www.drupal.org/project/ai">https://www.drupal.org/project/ai</a></li> <li><a href="https://www.drupal.org/project/ai_initiative">https://www.drupal.org/project/ai_initiative</a></li> <li><a href="https://www.drupal.org/project/ai_dasboard">https://www.drupal.org/project/ai_dasboard</a></li> <li><a href="https://www.drupal.org/project/ai_recipe_image_classification">https://www.drupal.org/project/ai_recipe_image_classification</a></li> <li><a href="https://www.drupal.org/project/ai_recipe_content_classification">https://www.drupal.org/project/ai_recipe_content_classification</a></li> <li><a href="https://www.drupal.org/project/tool">https://www.drupal.org/project/tool</a></li> <li><a href="https://www.drupal.org/project/field_widget_actions">https://www.drupal.org/project/field_widget_actions</a></li> <li><a href="https://www.drupal.org/project/ai_agents">https://www.drupal.org/project/ai_agents</a></li> <li><a href="https://www.drupal.org/project/ai_context">https://www.drupal.org/project/ai_context</a></li> <li><a href="https://www.drupal.org/project/canvas">https://www.drupal.org/project/canvas</a></li> <li><a href="https://www.drupal.org/project/flowdrop_ui_agents">https://www.drupal.org/project/flowdrop_ui_agents</a></li> </ul> <h2>Preparation tasks</h2> <h3>1. Project selection &amp; timing</h3> <ul> <li>Confirm final list of projects to migrate in this round</li> <li>Agree on migration window (target: DrupalCon Chicago or shortly before)</li> <li>Coordinate with Drupal.org infrastructure team to confirm availability during migration</li> </ul> <h3>2. Project manager communication</h3> <ul> <li>Notify all project managers of affected projects</li> <li>Align on expectations: workflows, issue management, MR templates</li> <li>Get sign-off from all stakeholders</li> </ul> <h3>3. Prepare each project</h3> <ul> <li>Audit and remove unnecessary labels from existing issue queues</li> <li>Prepare issue templates (bug report, feature request, etc.)</li> <li>Prepare merge request (MR) templates</li> </ul> <h3>4. Define new workflows</h3> <ul> <li>Set up issue boards (sprint view, backlog, etc.)</li> <li>Align on label taxonomy across projects</li> <li>Define milestone/sprint conventions</li> </ul> <h3>5. Documentation</h3> <ul> <li>Document the migration process and new workflows</li> <li>Suggested location: <strong>AI Initiative project GitLab Documentation</strong> section</li> <li>Include onboarding notes for contributors unfamiliar with GitLab issue queues</li> </ul> <h3>6. Execute migration</h3> <ul> <li>Run Drush migration command per project (~1 hour each)</li> <li>Verify contribution credit bot is active on each migrated project</li> <li>Confirm group-level issue views are working correctly</li> </ul> <h2>Proposed next steps</h2> <ol> <li><strong>Workshop</strong> (~2 hours) with Drupal AI project managers to align, divide tasks, and finalize preparation plan</li> <li>Complete all preparation tasks within the <strong>current sprint</strong></li> <li>Align with remaining stakeholders after the workshop</li> <li>Execute migration around <strong>DrupalCon Chicago</strong></li> </ol> <h3 id="summary-ai-usage">AI usage (if applicable)</h3> <p>[ ] AI Assisted Issue<br> This issue was generated with AI assistance, but was reviewed and refined by the creator.</p> <p>[ ] AI Assisted Code<br> This code was mainly generated by a human, with AI autocompleting or parts AI generated, but under full human supervision.</p> <p>[ ] AI Generated Code<br> This code was mainly generated by an AI with human guidance, and reviewed, tested, and refined by a human.</p> <p>[ ] Vibe Coded<br> This code was generated by an AI and has only been functionally tested.</p>