Commit cfe35007 authored by Oleksandr Pysaryuk's avatar Oleksandr Pysaryuk
Browse files

Remove named team and iteration process sections from L10n engineering HB page

parent 658eb14b

content/handbook/marketing/localization/engineering.md

+2 −17
Original line number Diff line number Diff line
@@ -7,12 +7,6 @@ Technical overview of GitLab's localization infrastructure and engineering proce 


For the full localization technology stack, see [Localization Technology Management at GitLab](/handbook/marketing/localization/localization_technology/). For product documentation localization architecture and workflows, see [GitLab Product Documentation Localization](/handbook/marketing/localization/tech_docs_localization/).



## Team



- [Rasam Hossain](https://gitlab.com/rasamhossain), Senior Fullstack Engineer

- [Lauren Barker](https://gitlab.com/laurenbarker), Staff Fullstack Engineer

- [Oleksandr Pysaryuk](https://gitlab.com/opysaryuk), Senior Manager, Globalization Technology



### Communication channels



- `#localization-engineering`: localization engineering team working channel
@@ -22,7 +16,7 @@ For the full localization technology stack, see [Localization Technology Managem 


For the full list of localization Slack channels, see the [Localization handbook](/handbook/marketing/localization/#contact-us).



## Scope

### Scope



The Localization Engineering team owns and maintains the infrastructure that enables GitLab content and product to be delivered in multiple languages.
@@ -33,16 +27,7 @@ The Localization Engineering team owns and maintains the infrastructure that ena 
- **Marketing website** (about.gitlab.com): continuous localization across 6 languages through GDATP for net new pages and high-profile content, and the Argo-Phrase pipeline for volume and async updates.

- **Product UI**: community-driven translation through [Crowdin](https://docs.gitlab.com/development/i18n/), supported by the [GitLab String Search](https://gitlab.com/gitlab-com/localization/gitlab-string-search) tool and [Crowdin Automation](https://gitlab.com/gitlab-com/localization/crowdin-automation) scripts.



## Iteration process



We start our iteration on a Tuesday. We release throughout the iteration. Iterations are 2 weeks long. See our [Localization engineering iterations here](https://gitlab.com/groups/gitlab-com/localization/-/cadences/).



We use two boards to track engineering work:



- [By Assignee](https://gitlab.com/groups/gitlab-com/localization/-/boards/9140637): shows all work items with `~"L10n-engineering"` label, grouped by team member

- [By Status](https://gitlab.com/groups/gitlab-com/localization/-/boards/11195951): shows workflow progression through Refinement -> Ready for development -> In dev -> In review -> Complete



## Review workflow

### Review workflow



The process of reviewing merge requests by the Localization Engineering team aligns with the GitLab [Code Review Guidelines](https://docs.gitlab.com/development/code_review/).