>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3552887. --> Reported by: [marcus_johansson](https://www.drupal.org/user/385947) Related to !1014 >>> <p>--- AI TRACKER METADATA ---<br> Update Summary: Move out AI Translate<br> Check-in Date: MM/DD/YYYY (US format) [When we should see progress/get an update]<br> Due Date: MM/DD/YYYY (US format) [When the issue should be fully completed]<br> Blocked by: [#XXXXXX] (New issues on new lines)<br> Additional Collaborators: @username1, @username2<br> AI Tracker found here: <a href="https://www.drupalstarforge.ai/">https://www.drupalstarforge.ai/</a><br> --- END METADATA ---</p> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>We are moving out AI Translate for 2.0. More TBA.</p> <h3 id="summary-problem-motivation">What to think about</h3> <p>General for all modules:</p> <ol> <li>Register the namespace</li> <li>Make sure to handle update hooks inside the new module. If we can not solve this without stubs, we should have a 1.3.0 release in between. 2.0.0 should not have any folders needed.</li> <li>Make sure to transfer the whole git history for the submodule folder into the AI Translate, and the do the move into root. You can cherry pick out any commits for a submodule.</li> </ol> <p>For AI Translate:</p> <ol> <li>Keep the part that is the LLM Proxy Translate Operation Type.</li> </ol> > Related issue: [Issue #3554535](https://www.drupal.org/node/3554535) > Related issue: [Issue #3560984](https://www.drupal.org/node/3560984)