Currently, we need to modify the CODEOWNERS file every time a **\*\*translator** needs repository access. This creates unnecessary overhead and maintenance burden. > **_\*\*translator_**_ == anyone at GitLab or external / continent worker who can approve and merge marketing translations._ This issue was the result of a DEX/Spartan Weekly meeting, [Bookmark here](https://docs.google.com/document/d/1fR5ZoKU7RnaQCkTy0uMe7gOF28Y-bBcO_MOlRAIajGA/edit?tab=t.0#bookmark=id.6ucyd0y92zht) **Proposal:** Create a dedicated GitLab group for translators (similar to the existing [Tech Docs Maintainers group](https://gitlab.com/gitlab-com/localization/maintainers)) to streamline access management. **Specific requirements** (based on @mjsibanez 's feedback here https://gitlab.com/gitlab-com/localization/localization-team/-/issues/477#note_2739188768): 1. **Blog + The Source:** * Create a `blog-localization` group * All Localization specialists and Content Managers should have merging rights * Members include: Emi, Noriko, Patrick, Laura, Maud, Megumi, Hendrik 2. **Marketing Website:** * Localization specialists (Emi, Noriko, Laura, Patrick) should be able to add commits to MRs but without merging rights * Content Managers (Hendrik, Megumi, Maud) should have merge rights * Special consideration: Homepage and pricing page changes should be reviewed by DEX team before merging **Benefits:** * Eliminates need to update CODEOWNERS for each new translator * Centralizes translator access management * Reduces administrative overhead **Reference:** * Example implementation: https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/-/merge_requests/1805 * Previous attempt: https://gitlab.com/gitlab-com/localization/international-content-managers