#### Context As part of baseline term extraction (#916+), the 11 remaining `get_started/` files were scanned for terminology candidates. This issue presents the extracted **regular terms** (excluding product names) as an interim list for review before any TBX entries are created. Each candidate was evaluated against the extraction criteria in [`terminology_artifacts/term-brief.md`](https://gitlab.com/gitlab-com/localization/docs-site-localization/-/blob/main/terminology_artifacts/term-brief.md): conceptual scope, no UI labels, no third-party or GitLab product names, no generic words, and - the key test - does the term create a real translation risk that a translator cannot resolve from context alone? We also cross-referenced each candidate against the Quickterm export (I got it from @KaterinaGasova here in this long comment https://gitlab.com/gitlab-com/localization/docs-site-localization/-/work_items/908#note_3271621665). The table shows: the term, which file(s) it appears in, how many times, whether it is in Quickterm, the current FR form, and any situation worth flagging. Note: `repository`, `branch`, `commit`, `merge request`, `CI/CD pipeline`, and several other code management terms are already covered in the pilot TBX (from `get_started_managing_code.md`) and are not repeated here. @maud-L , before we proceed to writing TBX briefs and entries, your guidance is needed on: 1. Which terms should be included vs. skipped 2. Whether the flagged Quickterm situations should be resolved first, or whether we proceed with our own brief #### How to review 1. **Read the table** 2. **Work through the checklist at the bottom** - check the box to include a term in the TBX, leave it unchecked to skip it. 3. **Add an inline comment on a checklist line** if you have a question, a different FR suggestion, or a reason for skipping. 4. **For flagged items** in the Notes column (e.g. unusual FR forms, missing FR in Quickterm, token/jeton inconsistency, fork noun vs verb) - either resolve them in a comment in the table directly, or start a thread on the current issue, OR if you feel it's worth it, create yet a new issue, like this for example --\> https://gitlab.com/gitlab-com/localization/docs-site-localization/-/work_items/922+. #### Extracted terms <table> <tr> <th>Term</th> <th>File(s)</th> <th>Count</th> <th>In Quickterm</th> <th>FR (from Quickterm)</th> <th>Notes</th> </tr> <tr> <td>executor</td> <td>get_started_runner.md</td> <td>15</td> <td>Yes</td> <td>exécuteur (Preferred)</td> <td></td> </tr> <tr> <td>instance runner</td> <td>get_started_runner.md</td> <td>2</td> <td>Yes</td> <td>runner d'instance (Preferred)</td> <td></td> </tr> <tr> <td>group runner</td> <td>get_started_runner.md</td> <td>2</td> <td>Yes</td> <td>runner pour un groupe (Preferred)</td> <td></td> </tr> <tr> <td>project runner</td> <td>get_started_runner.md</td> <td>2</td> <td>Yes</td> <td>runner pour un projet (Preferred)</td> <td></td> </tr> <tr> <td>runner fleet</td> <td>get_started_runner.md</td> <td>4</td> <td>Yes</td> <td>flotte de runners (Preferred)</td> <td></td> </tr> <tr> <td>autoscaling</td> <td>get_started_runner.md</td> <td>4</td> <td>Yes</td> <td>mise à l'échelle automatique (Preferred)</td> <td></td> </tr> <tr> <td>job</td> <td>get_started_runner.md</td> <td>25</td> <td>Yes</td> <td>job (Preferred, DNT)</td> <td>A translator unfamiliar with GitLab conventions might render this as "tâche" or "travail"</td> </tr> <tr> <td>scope</td> <td>get_started_runner.md</td> <td>6</td> <td>Yes</td> <td>portée (Preferred)</td> <td>In this file, "scope" refers specifically to runner access level (instance/group/project), which is not obvious from the word alone</td> </tr> <tr> <td>container registry</td> <td>get_started_deploy_release.md</td> <td>2</td> <td>Yes</td> <td>registre de conteneurs (Preferred)</td> <td></td> </tr> <tr> <td>package registry</td> <td>get_started_deploy_release.md</td> <td>2</td> <td>Yes</td> <td>registre de paquets (Preferred)</td> <td></td> </tr> <tr> <td>review app</td> <td>get_started_deploy_release.md</td> <td>2</td> <td>Yes</td> <td>version temporaire d'application (Preferred)</td> <td>FR form is long — worth validating</td> </tr> <tr> <td>feature flag</td> <td>get_started_deploy_release.md</td> <td>5</td> <td>Yes</td> <td>feature flag (Preferred, DNT)</td> <td>Abbreviation FF also in Quickterm (Admitted)</td> </tr> <tr> <td>incremental rollout</td> <td>get_started_deploy_release.md</td> <td>3</td> <td>No</td> <td></td> <td>Not in Quickterm</td> </tr> <tr> <td>protected environment</td> <td>get_started_deploy_release.md</td> <td>3</td> <td>Yes</td> <td>environnement protégé (Preferred)</td> <td></td> </tr> <tr> <td>deployment approval</td> <td>get_started_deploy_release.md</td> <td>2</td> <td>No</td> <td></td> <td>Not in Quickterm</td> </tr> <tr> <td>release</td> <td>get_started_agent_platform.md, get_started_runner.md, get_started_deploy_release.md, get_started_managing_infrastructure.md, get_started_planning_work.md, get_started_admin.md</td> <td>1, 1, 13, 1, 5, 1</td> <td>Yes</td> <td> ~~multiple forms, unclear which applies~~ release </td> <td> ~~Tracked separately in #922~~ `release` (feminine, Preferred) - confirmed by @maud-L in #922 </td> </tr> <tr> <td>Infrastructure as Code</td> <td>get_started_managing_infrastructure.md</td> <td>2</td> <td>Yes</td> <td>Infrastructure as Code (Admitted only)</td> <td> No Preferred FR translation exists; `infrastructure en tant que code` is Forbidden </td> </tr> <tr> <td>runbook</td> <td>get_started_managing_infrastructure.md, get_started_monitoring.md</td> <td>8, 3</td> <td>Yes</td> <td>runbook (Preferred, DNT)</td> <td></td> </tr> <tr> <td>error tracking</td> <td>get_started_monitoring.md</td> <td>4</td> <td>No</td> <td></td> <td>Not in Quickterm</td> </tr> <tr> <td>epic</td> <td>get_started_planning_work.md</td> <td>6</td> <td>Yes</td> <td>epic (Preferred); épopée (Forbidden)</td> <td> Forbidden form appears under the entry `GitLab epic` </td> </tr> <tr> <td>issue</td> <td>get_started_planning_work.md, get_started_projects.md, get_started_admin.md, get_started_managing_infrastructure.md, get_started_monitoring.md, get_started_agent_platform.md, getting_started_gitlab_duo.md, get_started_extending.md</td> <td>20, 5, 3, 3, 2, 2, 2, 1</td> <td>Yes</td> <td>ticket (Preferred)</td> <td>Known translation decision — worth having in TBX for consistency signal</td> </tr> <tr> <td>milestone</td> <td>get_started_planning_work.md</td> <td>10</td> <td>Yes</td> <td>jalon (Preferred)</td> <td></td> </tr> <tr> <td>iteration</td> <td>get_started_planning_work.md</td> <td>5</td> <td>Yes</td> <td>itération (Preferred)</td> <td></td> </tr> <tr> <td>issue board</td> <td>get_started_planning_work.md</td> <td>3</td> <td>Yes</td> <td>tableaux des tickets (Preferred)</td> <td> Quickterm has plural form `issue boards` </td> </tr> <tr> <td>label</td> <td>get_started_planning_work.md</td> <td>6</td> <td>Yes</td> <td>label (Preferred, DNT)</td> <td>étiquette is Forbidden</td> </tr> <tr> <td>roadmap</td> <td>get_started_planning_work.md</td> <td>4</td> <td>Yes</td> <td>roadmap (Preferred, DNT)</td> <td>feuille de route is Forbidden</td> </tr> <tr> <td>OKR</td> <td>get_started_planning_work.md</td> <td>3</td> <td>Yes</td> <td>OKR (Admitted); Objectives and Key Results (Preferred EN)</td> <td>Abbreviation — needs full form in brief</td> </tr> <tr> <td>time tracking</td> <td>get_started_planning_work.md</td> <td>3</td> <td>Yes</td> <td>suivi du temps (Preferred)</td> <td></td> </tr> <tr> <td>deploy key</td> <td>get_started_projects.md</td> <td>2</td> <td>Yes</td> <td>clé de déploiement (Preferred)</td> <td></td> </tr> <tr> <td>deploy token</td> <td>get_started_projects.md</td> <td>2</td> <td>Yes</td> <td>token de déploiement (Preferred)</td> <td> Uses `token` (not `jeton`) </td> </tr> <tr> <td>project access token</td> <td>get_started_projects.md</td> <td>2</td> <td>Yes</td> <td>token d'accès au projet (Preferred)</td> <td> Uses `token` (not `jeton`) </td> </tr> <tr> <td>personal access token</td> <td>get_started_admin.md, get_started_extending.md</td> <td>1, 1</td> <td>Yes</td> <td>jeton d'accès personnel (Preferred)</td> <td> Uses `jeton` — inconsistent with deploy token and project access token above </td> </tr> <tr> <td>namespace</td> <td>get_started_projects.md, get_started_git.md</td> <td>2, 1</td> <td>Yes</td> <td>espace de nommage (Preferred)</td> <td></td> </tr> <tr> <td>subgroup</td> <td>get_started_runner.md, get_started_projects.md, get_started_admin.md</td> <td>1, 3, 8</td> <td>Yes (no FR)</td> <td></td> <td>Entry exists in Quickterm but FR is empty</td> </tr> <tr> <td>fork</td> <td>get_started_git.md</td> <td>3</td> <td>Yes</td> <td>bifurquer (Preferred, verb); bifurcation (Preferred, noun)</td> <td> Three approaches in the wild: Quickterm says `bifurcation`/`bifurquer`; Microsoft Terminology (GitHub/Visual Studio context) uses `duplication (fork)`/`dupliquer (fork)` with EN as a gloss; community practice in French dev contexts is to keep `fork` untranslated. Guidance needed on which direction GitLab takes. </td> </tr> <tr> <td>webhook</td> <td>get_started_extending.md, get_started_admin.md</td> <td>11, 2</td> <td>Yes</td> <td>webhook (Preferred, DNT)</td> <td></td> </tr> <tr> <td>REST API</td> <td>get_started_extending.md</td> <td>3</td> <td>Yes</td> <td>API REST (Preferred)</td> <td>Word order inverted — standard in FR</td> </tr> <tr> <td>two-factor authentication</td> <td>get_started_admin.md</td> <td>3</td> <td>Yes</td> <td>authentification à deux facteurs (Preferred)</td> <td>Also 2FA (Admitted)</td> </tr> <tr> <td>repository mirroring</td> <td>get_started_admin.md</td> <td>1</td> <td>Yes</td> <td>fonctionnalité « miroir de dépôt » (Preferred)</td> <td>FR form is unusual — worth validating</td> </tr> </table> #### Terms excluded after applying [extraction criteria](https://gitlab.com/gitlab-com/office-of-the-ceo/ai-at-gitlab/ai-at-gitlab-usecases/-/work_items/47) The following candidates were considered but excluded because they do not create a real translation risk that a translator cannot resolve from context alone: - `artifact` — `artefact` is a direct cognate; no ambiguity - `incident` — same word in French; translates naturally as "incident" - `SSH key` — SSH is a third-party protocol; `clé SSH` is natural and unambiguous - `LDAP` — third-party protocol; clearly DNT - `GraphQL` — third-party technology; DNT - `visibility level` — generic compound; "niveau de visibilité" is natural - `session` (agent context) — still translates as "session" in French; no translation risk specific to GitLab - `deployment` — translates straightforwardly as "déploiement" - `environment` — translates straightforwardly as "environnement" - `working directory` — standard git term, translates straightforwardly - `wiki` — same word across most languages - `pipeline` — already covered in the pilot TBX as "CI/CD pipeline" - `group`, `tag`, `integration`, `agent`, `flow`, `topic`, `badge`, `snippet` — too generic, no translation risk specific to GitLab #### Review checklist <!--For each term: check the box to include in TBX, leave unchecked to skip. Add an inline comment on the line if you have a note.--> - [x] executor - [x] instance runner - [ ] group runner --> Replace by "runner de groupe" in Quickterm. - [ ] project runner --> Replace by "runner de projet" in Quickterm. - [x] runner fleet - [x] autoscaling - [x] job - [x] scope - [x] container registry - [x] package registry - [ ] review app --> Replace by "environnement éphémère" in Quickterm. - [x] feature flag - [ ] incremental rollout --> Add to QuickTerm "déploiement progressif". - [x] protected environment - [ ] deployment approval (Skip) - [x] release _~~(pending #922)~~_ - [x] Infrastructure as Code - [x] runbook - [ ] error tracking (Skip) - [x] epic - [x] issue - [x] milestone - [x] iteration - [ ] issue board --> Replace by "tableau des tickets" (moved to singular) in Quickterm. - [x] label - [x] roadmap - [x] OKR - [ ] time tracking (Skip) - [x] deploy key - [ ] deploy token --> Replace by "jeton de déploiement" in Quickterm. - [ ] project access token --> Replace by "jeton d'accès au projet" in Quickterm. - [x] personal access token - [x] namespace - [ ] subgroup (Skip) - [ ] fork --> Replace by "dupliquer" for the verb, and "duplication" for the noun in Quickterm. - [x] webhook - [x] REST API - [x] two-factor authentication - [ ] repository mirroring