>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3265096. --> Reported by: [drumm](https://www.drupal.org/user/3064) >>> <h2>Roadmap to migrating Drupal.org issues to git.drupalcode.org</h2> <ol> <li>GitLab CI is now enabled for all projects on Drupal.org</li> <li><span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-8"><a href="https://www.drupal.org/project/infrastructure/issues/3338978" title="Status: Needs review">#3338978: Replace Bakery with KeyCloak SSO &amp; social sign on</a></span> <ul> <li>We review and deploy our new SSO solution, allowing us to cross-authenticate between D7/D10</li> <li>Solution is built, some early migration tests have been done - needs review</li> </ul> </li> <li>We deploy the new credit record/fork management in D10 - setting up CDN/paths for access <ul> <li>New content types for each are built</li> </ul> </li> <li>We migrate existing credit to the new content type <ul> <li>Migration code is written</li> </ul> </li> <li><span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/drupalorg/-/work_items/3409678" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/drupalorg/-/work_items/3409678</a></span> - We add an opt-in issue migration tool to projects, allowing the maintainer to migrate issues <ul> <li>Possibly we just do the first project or two manually without a ui button</li> <li>The actual migration button needs to be built</li> <li>But the migration code itself is written</li> </ul> </li> <li>We then need to support this with documentation, in concert with the first users.</li> </ol> > Related issue: [Issue #3250923](https://www.drupal.org/node/3250923) > Related issue: [Issue #3338978](https://www.drupal.org/node/3338978) > Related issue: [Issue #3409678](https://www.drupal.org/node/3409678) > Related issue: [Issue #3227737](https://www.drupal.org/node/3227737)