.gitlab/CODEOWNERS

@@ -114,6 +114,7 @@ sites/uncategorized/source/company/culture/inclusion/tmrg-gitlab-latinx/ @pmejia
 /sites/handbook/source/handbook/engineering/development/ops/release/ @nicolewilliams
 /sites/handbook/source/handbook/engineering/development/database/ @craig-gomes @abrandl
 /sites/handbook/source/handbook/engineering/development/dev/ @timzallmann
+/sites/handbook/source/handbook/engineering/development/dev/training/ic-to-manager/ @dsatcher
 /sites/handbook/source/handbook/engineering/development/dev/create/ @dsatcher
 /sites/handbook/source/handbook/engineering/development/dev/create-editor/ @oregand
 /sites/handbook/source/handbook/engineering/development/dev/create/ecosystem/ @arturoherrero @leipert
@@ -423,7 +424,6 @@ sites/handbook/source/handbook/people-group/sustainability/ @wspillane @wendybar
 /source/direction/manage/internationalization/ @gl-product-leadership @adawar @david @hdelalic
 /source/direction/manage/devops-reports/ @gl-product-leadership @adawar @david @ljlane
 /source/direction/manage/code-analytics/ @gl-product-leadership @adawar @david @ljlane
-/source/direction/manage/planning-analytics/ @gl-product-leadership @adawar @david @ljlane
 /source/direction/manage/value_stream_management/ @gl-product-leadership @adawar @david @ljlane
 /source/direction/plan/issue_tracking/ @gl-product-leadership @adawar @david @gweaver
 /source/direction/plan/boards/ @gl-product-leadership @adawar @david @gweaver
@@ -434,19 +434,23 @@ sites/handbook/source/handbook/people-group/sustainability/ @wspillane @wendybar
 /source/direction/plan/quality_management/ @gl-product-leadership @adawar @david @mjwood
 /source/direction/plan/requirements_management/ @gl-product-leadership @adawar @david @mjwood
 /source/direction/plan/service_desk/ @gl-product-leadership @adawar @david @mjwood
+/source/direction/plan/planning-analytics/ @gl-product-leadership @adawar @david @gweaver
 /source/direction/create/source_code_management/ @gl-product-leadership @adawar @david
 /source/direction/create/code_review/ @gl-product-leadership @adawar @david @phikai
-/source/direction/create/web_ide/ @gl-product-leadership @adawar @david @ericschurter
-/source/direction/create/snippets/ @gl-product-leadership @adawar @david @ericschurter
-/source/direction/create/live_preview/ @gl-product-leadership @adawar @david @ericschurter
+/source/direction/create/editor/web_ide/ @gl-product-leadership @adawar @david @ericschurter
+/source/direction/create/editor/snippets/ @gl-product-leadership @adawar @david @ericschurter
+/source/direction/create/editor/live_preview/ @gl-product-leadership @adawar @david @ericschurter
 /source/direction/create/editor_extension/ @gl-product-leadership @adawar @david @phikai
 /source/direction/create/gitaly/ @gl-product-leadership @adawar @david @mjwood
-/source/direction/create/wiki/ @gl-product-leadership @adawar @david @ericschurter
-/source/direction/create/static_site_editor/ @gl-product-leadership @adawar @david @ericschurter
+/source/direction/create/editor/wiki/ @gl-product-leadership @adawar @david @ericschurter
+/source/direction/create/editor/static_site_editor/ @gl-product-leadership @adawar @david @ericschurter
+/source/direction/create/editor/source_editor/ @gl-product-leadership @adawar @david @ericschurter
+/source/direction/create/editor/content_editor/ @gl-product-leadership @adawar @david @ericschurter
 /source/direction/create/gitlab_handbook/ @gl-product-leadership @adawar @david @ericschurter
-/source/direction/create/gitlab_docs/ @gl-product-leadership @adawar @david @ericschurter
+/source/direction/create/editor/gitlab_docs/ @gl-product-leadership @adawar @david @ericschurter
 /source/direction/create/gitter/ @gl-product-leadership @adawar @david @ericschurter
-/source/direction/create/ecosystem/ @gl-product-leadership @adawar @david
+/source/direction/create/editor/navigation_settings/ @gl-product-leadership @adawar @david @ericschurter
+/source/direction/ecosystem/ @gl-product-leadership @adawar @david
 # Product Section - Ops
 /source/direction/ops/ @kencjohnston

data/applications.yml

@@ -804,6 +804,13 @@
          title: Logz.io
        - url: https://logz.io/blog/monitoring-gitlab-elk-stack/
          title: Integration instructions
+    - title: Analytics & Reports by Screenful
+      content: Get actionable insights from your GitLab task data. Track your teams' velocity, lead & cycle times, current bottlenecks, and get a high-level view across all projects. Get a quick overview of your progress without configuring anything. Select charts and reports from time-tested templates or create your own custom setups — filter based on any property, see correlations, and analyze trends. Share insights with public and private links. Send them via email or Slack on a custom schedule.
+      links:
+        - url: https://screenful.com/reports-for-gitlab
+          title: Analytics & Reports for GitLab
+        - url: https://screenful.com/gitlab/getting-started
+          title: Getting started guide
     - title: Dashboards by Screenful
       content: See the current status of your projects as well as longer term trends in a visual dashboard created from your GitLab data. Gain insight to things like team velocity, lead & cycle times, and what types of tasks team is spending time on. Use with any of your devices or rotate on the office TV.
       links:
@@ -811,13 +818,6 @@
           title: Dashboard for GitLab
         - url: https://screenful.com/gitlab/getting-started
           title: Getting started guide
-    - title: Reports by Screenful
-      content: The Reports by Screenful make it easy to build reports from your GitLab task data and share them with your colleagues. Track all of your projects, see correlations and analyze trends. Track multiple metrics at once with the dual axis line chart or the multi-bar chart. Easily share reports vial email or Slack.
-      links:
-        - url: https://screenful.com/reports-for-gitlab
-          title: Reports for GitLab
-        - url: https://screenful.com/gitlab/getting-started
-          title: Getting started guide
     - title: Waydev
       content: Enable GitLab users and teams to make data driven decisions. Waydev analyzes your codebase in GitLab to provide actionable metrics, crystal-clear visibility and better productivity.
       links:

data/case_studies/university-of-surrey.yml

+title: University of Surrey 
+cover_image: '/images/university_of_surrey_cover_image.jpg'
+cover_title: |
+  The University of Surrey achieves top marks for collaboration and workflow management with GitLab
+cover_description: |
+  Learn how GitLab's stable code repository fosters collaboration and visibility at the University of Surrey
+
+
+customer_logo: '/images/case_study_logos/logo_uni_surrey.png'
+customer_logo_css_class: brand-logo-tall
+customer_industry: Education
+customer_location: UK
+customer_solution: GitLab Ultimate
+customer_employees: 4,000
+customer_overview: |
+  The University of Surrey is a leading research university dedicated to providing exceptional teaching and practical learning to over 17K students.
+customer_challenge: |
+  The University of Surrey sought a reliable, collaborative code repository. It used Subversion, but struggled with the lack of a single interface.
+
+key_benefits:
+  - |
+    Increased collaboration and visibility
+  - |
+    Single user interface
+  - |
+    Successful workflow implementation
+  - |
+    Improved testing capabilities
+
+customer_stats:
+  - stat: 67 
+    label: Runners serving jobs from 150 projects 
+  - stat: 2300+
+    label: GitLab projects on its platform 
+  - stat: 110K  
+    label: Builds created by 830 active users
+
+customer_study_content:
+  - title: the customer
+    subtitle: A global community dedicated to education and research
+    content:
+      - |
+        The University of Surrey is a leading research university in England, UK focused on practice-based education. Founded in 1966, The University specializes in engineering, science, and sociology. [The University of Surrey](https://www.surrey.ac.uk) teaches over 17,000 students from around the world and strives to empower its student body for personal and professional success. 
+      
+  - title: the challenge
+    subtitle:  Inefficient file storage and lacking visibility
+    content:
+      - |
+       The Information Technology department at the University of Surrey faced a myriad of challenges in supporting researchers to store code in an on-premise [version control system](/topics/version-control/). The team had to balance the needs of academics who asked for an enhanced version control tool coupled with their own need to collaborate and iterate in a more efficient, modern way. A growing team accompanied a more complex infrastructure, and the previous method of using Subversion or storing files in folders or on storage locations did not support the IT team or academics.  
+      - |
+        “We were at a point where we had to collaborate and start doing DevOps the modern way. We had automation tools, infrastructure as code, quick cycles, and testing, but we had a growing team and collaboration wasn’t easy to do,” explains Kosta Polyzos, Senior System Administrator. Compounding the difficulties was the lack of an interface to easily provide visibility into work. It was becoming increasingly difficult for colleagues to keep track of progress and make informed contributions at the right place, to the right effect. Committed to increasing collaboration, the team set out to find a solution that offered reliability and a seamless single interface to coordinate work.
+    
+  - blockquote: We like that GitLab is a platform that provides a one-point solution for many things. It’s not just a repository; it has many features, including Wiki, Pages, analytics, a web interface, merge requests, CI/CD, and issue comments. You can collaborate in issues and merge requests. It’s a nice package overall.
+    attribution: Kosta Polyzos 
+    attribution_title: Senior Systems Administrator
+
+  - title: the solution
+    subtitle: A stable, reliable code repository facilitates collaboration
+    content:
+      - |
+       Determining a solution required factoring in several unique considerations. The main request from all stakeholders was to have a stable code repository that enabled rapid collaboration. Because the University of Surrey has strict regulations regarding data, the team also needed an on-premise solution to ensure full compliance. Academics may not have strong Git skills, so the solution also needed to have a low barrier to entry for people to collaborate and support quick adoption.
+      - |
+        Considering these factors, the team identified GitLab as the solution to increase collaboration and iteration across teams regardless of role. By starting on a free tier, the team was able to try out features, and when GitLab provided [free, unlimited licenses for academic institutions](/solutions/education/), every feature became available to them. “This was very good news for us, because we have access to every GitLab feature. It doesn’t mean that everyone will use all the extra features, but they’re available to solve specific problems if someone needs a solution. I think it’s a good thing for universities and their research communities,” Polyzos said.
+      - |
+        GitLab has satisfied academics as well. As Polyzos explained, “GitLab’s GUI helps people understand what is going on by visualizing all things Git. I’m not sure people were particularly familiar with Git, but learning it through GitLab made it very easy to get people on board.” As Oscar Mendez Maldonado, Research Fellow, explained, “Having a university-hosted repository is crucial to ensuring access, safety, and reliability.” With GitLab, the team increased collaboration and was able to implement a streamlined workflow, bringing together contributors and breaking down silos. 
+
+  - blockquote: GitLab does a really good job of visualizing the branch structure of a given Git repository, allowing me to quickly refer back to a previous version of code rather than checking out individual branches/hashes at a time.
+    attribution: Matthew Shere 
+    attribution_title: Postgraduate research student
+
+  - title: the results
+    subtitle: A modern, flexible workflow
+    content:
+      - |
+        The University of Surrey has over 2,300 projects and 110,000 builds. These efforts are made possible by implementing a seamless workflow in which users create personal branches from issues and test solutions before merging into the main branch and deploying to the production line. This workflow has improved the way the team delivers their service and simplified their growing infrastructure. “When it comes to operations, we wouldn’t have been able to cope. GitLab’s code repository and CI are the two main things that have enabled this for us,” Polyzos said. 
+      - |
+        GitLab has helped the IT team write more and better code and create a DevOps model. “This modern world of IT is not a single problem with a single solution. You need many tools in your toolchain. GitLab is a core tool with a central place in our toolchain. It has enabled us to further explore other tools and combine them,” Polyzos shared. “GitLab helped us implement the workflow architecturally, and we can iterate and go through the workflow again and again to improve. It has also helped us better integrate testing into the workflow. Protected branches and merge approvals provide control over the flow of new code before CI/CD pushes out the changes. Basic syntax and linting errors have essentially disappeared, and logical errors are caught earlier in the workflow.”  
+      - |
+        While the IT team has made use of GitLab’s branching, testing, and coding capabilities, academics have incorporated GitLab in the teaching environment due to its GUI, which provides a simple code visualization to identify changes and authors. In a group assignment, professors find it useful to understand which students committed specific changes. “Users appreciate the seamless interface - from setting up SSH keys to navigation - so that every little detail makes the user experience really enjoyable and effortless. Someone with no Git experience whatsoever doesn’t feel intimidated by it,” Polyzos said.
+      - |
+        As the IT team and academics tinkered with GitLab to discover the features that meet their needs, the usefulness of GitLab’s applications development features has slowly spread throughout the University of Surrey. "GitLab is a reliable tool and code repository first and foremost. It lubricates workflows in various ways and allows for collaboration internally as well as externally," Polyzos added.
+      - | 
+        Some users have built custom Docker images by uploading files and setting GitLab runners to build the images for them, while others who require a website now use GitLab Pages. As Dean Roe, System Administrator Team Leader, said “We are continually impressed at the rate at which GitLab expands its feature set in useful ways. The blog posts on gitlab.com do an excellent job of telling us and our users what fixes and new features we can expect in each new release. The process of bringing in updates is effortless too.
+      - |
+        By using GitLab, the University of Surrey has increased collaboration, while developing higher quality code through a robust solution to deliver better software faster. “We like GitLab, and the users like it. It’s stable and trustworthy, and we’re definitely going to continue using it.”       
+   
+      - |
+        ## Learn more about GitLab for education
+      - |
+        [Dublin City empowers students for the IT industry](/customers/dublin-city-university/)
+      - |
+        [Increasing development speed at EAB](/customers/EAB/)
+      - |
+        [How the University of Washington improved project management](/customers/uw/)

data/categories.yml

@@ -200,9 +200,9 @@ importers:
 planning_analytics:
   name: "Planning Analytics"
-  stage: manage
+  stage: plan
   documentation: https://docs.gitlab.com/ee/user/group/issues_analytics/
-  direction: /direction/manage/planning-analytics/
+  direction: /direction/plan/planning-analytics/
   description: "Gather insights about how your organization is planning and prioritizing across projects and groups."
   roi: false
   available: 2018-11-22
@@ -259,21 +259,6 @@ value_stream_management:
   ux_scorecard_link: https://gitlab.com/groups/gitlab-org/-/epics/1454
   ux_scorecard_score: C
-insights:
-  name: "Insights"
-  stage: manage
-  documentation: https://docs.gitlab.com/ee/user/group/insights/
-  roi: false
-  available: 2019-05-22
-  viable: 2019-06-22
-  complete:
-  lovable:
-  dogfooding_status: Active
-  dogfooding_issue: N/A
-  ux_scorecard_score: '-'
-  maturity: viable
-  marketing: true
-
 # Plan
 issue_tracking:
@@ -506,7 +491,7 @@ navigation:
   stage: create
   description: "How users easily discover and configure product features."
   documentation:
-  direction: /direction/create/navigation_settings/
+  direction: /direction/create/editor/navigation_settings/
   marketing: false
   roi:
   priority_level:
@@ -632,7 +617,7 @@ wiki:
   name: "Wiki"
   stage: create
   documentation: https://docs.gitlab.com/ee/user/project/wiki/
-  direction: /direction/create/wiki/
+  direction: /direction/create/editor/wiki/
   description: "Share documentation and organization information with a built in wiki."
   roi: false
   available: 2017-10-15
@@ -650,7 +635,7 @@ static_site_editor:
   name: "Static Site Editor"
   stage: create
   documentation: https://docs.gitlab.com/ee/user/project/static_site_editor/
-  direction: /direction/create/static_site_editor/
+  direction: /direction/create/editor/static_site_editor/
   description: "Focused on building an amazing experience for editing and building static sites."
   roi: true
   available: 2020-04-22
@@ -685,7 +670,7 @@ gitlab_docs:
     - gitlab docs
   documentation: 'https://docs.gitlab.com/ee/development/documentation/site_architecture/'
   description: "Improve and maintain the features, style, and build process for the GitLab Documentation website."
-  direction: /direction/create/gitlab_docs/
+  direction: /direction/create/editor/gitlab_docs/
   roi: false
   marketing: false
   dogfooding_status: Active
@@ -699,7 +684,7 @@ web_ide:
   feature_labels:
     - web edit
   documentation: https://docs.gitlab.com/ee/user/project/web_ide/index.html
-  direction: /direction/create/web_ide/
+  direction: /direction/create/editor/web_ide/
   description: "A full featured Integrated Development Environment (IDE) built into GitLab so you can start contributing on day one with no need to spend days getting all the right packages installed into your local dev environment."
   roi: true
   available: 2018-01-01
@@ -734,7 +719,7 @@ live_preview:
   name: "Live Preview"
   stage: create
   documentation: https://docs.gitlab.com/ee/user/project/web_ide/index.html#live-preview
-  direction: /direction/create/live_preview/
+  direction: /direction/create/editor/live_preview/
   description: "Preview your simple JavaScript apps and static sites in the Web IDE, viewing your changes in real time, right next to the code."
   roi: false
   available: 2018-08-22
@@ -752,7 +737,7 @@ snippets:
   name: "Snippets"
   stage: create
   documentation: https://docs.gitlab.com/ee/user/snippets.html
-  direction: /direction/create/snippets/
+  direction: /direction/create/editor/snippets/
   description: "Store and share bits of code and text with other users."
   roi: false
   available: 2017-01-01
@@ -785,10 +770,10 @@ gitaly:
 integrations:
   name: Integrations
-  stage: create
+  stage: ecosystem
   feature_labels:
     - Category:Integrations
-  direction: /direction/create/ecosystem/integrations/
+  direction: /direction/ecosystem/integrations/
   documentation: https://docs.gitlab.com/ee/integration/
   description: "Integrations are places where the GitLab product connects to features and services from other products. These integrations seek to offer our customers a seamless experience between these products, and range from lightweight features like Slack notifications for projects, to deep and complex integrations with Atlassian JIRA that connect a wide array of functionality throughout the GitLab product."
   roi: false
@@ -799,27 +784,11 @@ integrations:
   complete:
   lovable:
-api:
-  name: API
-  stage: create
-  documentation: https://docs.gitlab.com/ee/user/project/integrations/
-  direction: /direction/create/ecosystem/api/
-  description: "The GitLab API enables other products and services the ability to integrate with the GitLab product."
-  roi: false
-  feature_labels:
-    - Category:API
-  marketing: false
-  maturity: viable
-  available: 2017-01-01
-  viable: 2018-01-01
-  complete: 2022-12-22
-  lovable: 2023-12-22
-
 gdk:
   name: GDK
-  stage: create
+  stage: ecosystem
   documentation: https://gitlab.com/gitlab-org/gitlab-development-kit
-  direction: /direction/create/ecosystem/gdk/
+  direction: /direction/ecosystem/gdk/
   description: "GitLab Development Kit (GDK) provides a collection of scripts and other resources to install and manage a GitLab installation for development purposes."
   feature_labels:
     - Category:GDK
@@ -832,10 +801,10 @@ gdk:
   lovable: 2022-12-22
 foundations:
-  name: FE/UX Foundations
-  stage: create
+  name: Foundations
+  stage: ecosystem
   documentation: https://design.gitlab.com
-  direction: /direction/create/ecosystem/frontend-ux-foundations/
+  direction: /direction/ecosystem/foundations/
   description: "GitLab's design system ([Pajamas](https://design.gitlab.com/)) and our frontend architecture: webpack, [PWA](https://developers.google.com/web/progressive-web-apps) needs for improved mobile support, and more."
   feature_labels:
     - Category:FE/FUX Foundations
@@ -847,24 +816,6 @@ foundations:
   complete: 2021-06-22
   lovable: 2021-12-22
-jira_importer:
-  name: "Jira Importer"
-  stage: create
-  documentation: https://docs.gitlab.com/ee/user/project/import/jira.html#import-your-jira-project-issues-to-gitlab
-  marketing_page:
-  direction: /direction/create/ecosystem/jira_importer/
-  description: "Allow users to import from Jira without losing required data"
-  feature_labels:
-    - Category:Jira Importer
-  roi: false
-  maturity: minimal
-  available: 2020-04-22
-  viable: 2021-12-22
-  complete:
-  lovable:
-  marketing: false
-  priority_level: high
-
 # Verify
 continuous_integration:
@@ -1144,6 +1095,29 @@ merge_trains:
   dogfooding_issue: https://gitlab.com/gitlab-org/quality/team-tasks/-/issues/195#known-issues-improvements
   dogfooding_group: Quality
+review_apps:
+  name: "Review Apps"
+  stage: verify
+  marketing_page: /stages-devops-lifecycle/review-apps/
+  documentation: https://docs.gitlab.com/ee/ci/review_apps/
+  direction: /direction/release/review_apps/
+  description: "Get a fully functional pre-production environment for every merge request that updates on each commit. See code running, and enable user acceptance testing and automated smoke tests before you merge."
+  roi: true
+  available: 2017-01-01
+  viable: 2017-01-01
+  complete: 2017-01-01
+  lovable: 2023-11-18
+  maturity: complete
+  marketing: true
+  priority_level: low
+  dogfooding_status: Exclusive
+  dogfooding_issue: N/A
+  dogfooding_group: Development, All
+  ux_scorecard_link:
+  ux_scorecard_score:
+  label: "Category:Review Apps" 
+
+
 # Package
 package_registry:
@@ -1241,23 +1215,6 @@ dependency_firewall:
   dogfooding_issue: Not Applicable (Planned)
   dogfooding_group: Not Applicable (Planned)
-release_evidence:
-  name: "Release Evidence"
-  stage: package
-  direction: /direction/package/#release-evidence
-  documentation: https://docs.gitlab.com/ee/user/project/releases/#release-evidence
-  description: "Release Evidence includes all the assurances and evidence collection that are necessary for you to trust the changes you're delivering."
-  roi: false
-  available: 2020-01-22
-  viable: 2021-12-22
-  complete: 2022-06-22
-  lovable: 2023-06-22
-  maturity: minimal
-  marketing: true
-  dogfooding_status: Exclusive
-  dogfooding_issue: N/A
-  dogfooding_group: Delivery
-
 git_lfs:
   name: "Git LFS"
   stage: package
@@ -1617,6 +1574,9 @@ continuous_delivery:
   dogfooding_status: limited
   dogfooding_issue: TBD
   dogfooding_group: Development, All
+  ux_scorecard_link: https://gitlab.com/gitlab-org/gitlab-design/-/issues/1664
+  ux_scorecard_score: 
+  label: "Category:Continuous Delivery"
 pages:
   name: "Pages"
@@ -1638,25 +1598,8 @@ pages:
   dogfooding_group: All
   ux_scorecard_link: https://gitlab.com/gitlab-org/gitlab-design/-/issues/412
   ux_scorecard_score: C
-review_apps:
-  name: "Review Apps"
-  stage: release
-  marketing_page: /stages-devops-lifecycle/review-apps/
-  documentation: https://docs.gitlab.com/ee/ci/review_apps/
-  direction: /direction/release/review_apps/
-  description: "Get a full production like environment for every merge request that updates on each commit. See code running and enable user acceptance testing before you merge."
-  roi: true
-  available: 2017-01-01
-  viable: 2017-01-01
-  complete: 2017-01-01
-  lovable: 2023-11-18
-  maturity: complete
-  marketing: true
-  priority_level: low
-  dogfooding_status: Exclusive
-  dogfooding_issue: N/A
-  dogfooding_group: Development, All
+  label: "Category:Pages" 
 advanced_deployments:
   name: "Advanced Deployments"
@@ -1675,6 +1618,9 @@ advanced_deployments:
   dogfooding_status: limited
   dogfooding_issue: TBD
   dogfooding_group: Delivery
+  ux_scorecard_link:
+  ux_scorecard_score:
+  label: "Category:Advanced Deployments"
 feature_flags:
   name: "Feature Flags"
@@ -1693,6 +1639,27 @@ feature_flags:
   dogfooding_status: limited
   dogfooding_issue: TBD
   dogfooding_group: Development
+  ux_scorecard_link:
+  ux_scorecard_score:
+  label: "Category:Feature Flags"
+
+
+release_evidence:
+  name: "Release Evidence"
+  stage: release
+  direction: /direction/package/#release-evidence
+  documentation: https://docs.gitlab.com/ee/user/project/releases/#release-evidence
+  description: "Release Evidence includes all the assurances and evidence collection that are necessary for you to trust the changes you're delivering."
+  roi: false
+  available: 2020-01-22
+  viable: 2021-12-22
+  complete: 2022-06-22
+  lovable: 2023-06-22
+  maturity: minimal
+  marketing: true
+  dogfooding_status: Exclusive
+  dogfooding_issue: N/A
+  dogfooding_group: Delivery
 release_orchestration:
   name: "Release Orchestration"
@@ -1714,6 +1681,7 @@ release_orchestration:
   dogfooding_group: Delivery
   ux_scorecard_link: https://gitlab.com/gitlab-org/gitlab-design/-/issues/516
   ux_scorecard_score: F
+  label: "Category:Release Orchestration"
 # Configure
@@ -1875,6 +1843,9 @@ runbooks:
   dogfooding_status: Not Planned
   dogfooding_issue: N/A
   dogfooding_group: Infrastructure
+  ux_scorecard_link:
+  ux_scorecard_score:
+  label: "Category:Runbooks"
 metrics:
   name: "Metrics"
@@ -1893,6 +1864,9 @@ metrics:
   dogfooding_status: limited
   dogfooding_issue: TBD
   dogfooding_group: Infrastructure
+  ux_scorecard_link:
+  ux_scorecard_score:
+  label: "Category:Metrics"
 incident_management:
   name: "Incident Management"
@@ -1913,6 +1887,7 @@ incident_management:
   dogfooding_group: Infrastructure
   ux_scorecard_link: https://gitlab.com/gitlab-org/gitlab/-/issues/11713
   ux_scorecard_score: C
+  label: "Category:Incident Management"
 on_call_schedule_management:
   name: "On-call Schedule Management"
@@ -1931,6 +1906,9 @@ on_call_schedule_management:
   dogfooding_status: limited
   dogfooding_issue: https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/322
   dogfooding_group: Infrastructure
+  ux_scorecard_link:
+  ux_scorecard_score:
+  label: "Category:On-call Schedule Management"
 logging:
   name: "Logging"
@@ -1949,6 +1927,9 @@ logging:
   dogfooding_status: Not Planned
   dogfooding_issue: N/A
   dogfooding_group: Infrastructure
+  ux_scorecard_link:
+  ux_scorecard_score:
+  label: "Category:Logging"
 tracing:
   name: "Tracing"
@@ -1967,6 +1948,9 @@ tracing:
   dogfooding_status: Not Planned
   dogfooding_issue: N/A
   dogfooding_group: Infrastructure
+  ux_scorecard_link:
+  ux_scorecard_score:
+  label: "Category:Tracing"
 self_monitoring:
   name: "GitLab Self-Monitoring"
@@ -1999,6 +1983,9 @@ error_tracking:
   dogfooding_status: limited
   dogfooding_issue: TBD
   dogfooding_group: Infrastructure
+  ux_scorecard_link:
+  ux_scorecard_score:
+  label: "Category:Error Tracking"
 synthetic_monitoring:
   name: "Synthetic Monitoring"
@@ -2237,6 +2224,11 @@ product_analytics:
   maturity: minimal
   marketing: true
   priority_level: medium
+  ux_scorecard_link:
+  ux_scorecard_score:
+  dogfooding_issue:
+  dogfooding_status:
+  label: "Category:Product Analytics"
 usage_ping:
   name: "Usage Ping"

data/features.yml

@@ -306,9 +306,6 @@ devops_tools:
     logo: '/images/devops-tools/subversion-logo.png'
     category:
       - source_code_management
-  saas:
-    name: 'SaaS'
-    logo: 'null'
   gitlab_issue_boards:
     name: 'GitLab Issue Boards'
     logo: '/images/devops-tools/gitlab-logo.svg'

data/inclusiveness_check.yml

@@ -25,6 +25,7 @@ skipped:
   - source/job-families/sales/business-systems-architect/index.html.md 
   - source/job-families/fellow-of-initial-delight/index.html.md
   - source/job-families/alliances/alliances-manager/index.html.md
+  - source/job-families/marketing/director-sales-development/index.html.md
   - source/job-families/sales/technical-enablement-program-manager/index.html.md
   - source/job-families/people-ops/talent-brand-and-talent-acquisition-enablement/index.html.md
   - source/job-families/alliances/director-partnerships/index.html.md

data/people_group/job_families.yml

@@ -224,6 +224,8 @@
   description: "/job-families/product/product-manager/"
 - title: Director, Product Management
   description: "/job-families/product/product-management-leadership/"
+- title: Product Manager - Marketing
+  description: "/job-families/marketing/product-manager-marketing/"
 - title: Product Marketing Manager
   description: "/job-families/marketing/product-marketing-manager/"
 - title: Product Marketing Manager, Public Sector

data/performance_indicators/dev_section.yml

@@ -1105,7 +1105,7 @@
     embed: v2
   urls:
   - https://app.periscopedata.com/app/gitlab/684213/WIP-Static-Site-Editor-Usage-Metrics
-  - https://about.gitlab.com/direction/create/static_site_editor/
+  - https://about.gitlab.com/direction/create/editor/static_site_editor/
 - name: Create:Editor - AMAU - Uniques users of Wiki
   base_path: "/handbook/product/performance-indicators/"

data/performance_indicators/ops_section.yml

@@ -118,12 +118,11 @@
   health:
     level: 2
     reasons:
-    - Insight - In July, we exceeded the budget by 8 hours (2 hours less than June), which can be attributed to `GET /api/projects/:id/jobs/:job_id/trace` and the improvements made to reduce latency related to `POST /api/projects/:id/pipeline` as well as `Projects::JobsController` end points.
-    - July availability improved from 98.60% to 98.80%, +.20% 
-    - Insight - In our Sentry Bug tracking, we have seen continued issues around some API end points and will continue making improvements
-     - Improvement - We have a spike via [gitlab#331656](https://gitlab.com/gitlab-org/gitlab/-/issues/331565) in 14.3 that will help us optimize these queries further once we reduce the load on them. 
-    - Improvement - We have sceduled [gitlab#276192](https://gitlab.com/gitlab-org/gitlab/-/issues/276192) for 14.2 which will add build log size limits helping to mitigate errors with large log sizes. 
-    - Improvement - Lastly, we have noticed several endpoints related to other groups and will work to get those reassigned in [gitlab#334556](https://gitlab.com/gitlab-org/gitlab/-/issues/334556)
+    - Insight - In the past 28 days, we exceeded the budget by 7 hours (1 hours less than July), which shows we are making some improvement to stabilizing the availability of our endpoints. The APIs with most errors are GET /api/projects/:id/pipelines, GET /api/projects/:id/pipelines/:pipeline_id, and GET /api/projects/:id/jobs - which have been prioritized for further investigation and correction in 14.3. The controllers with higher errors are Projects::JobsController#show.json and Projects::JobsController#trace.json, which have infradev issues also prioritized in 14.3 or 14.4. 
+    - August availability improved from 98.80% to 98.94%, +.14% 
+    - Improvement - We have a spike via [gitlab#331656](https://gitlab.com/gitlab-org/gitlab/-/issues/331565) in 14.3 that will help us optimize these queries further once we reduce the load on them. 
+    - Improvement - We completed the effort for [gitlab#276192](https://gitlab.com/gitlab-org/gitlab/-/issues/276192) in 14.2 which will add build log size limits helping to mitigate errors with large log sizes and should be rolling the work out. On GitLab.com this impacted 160 projects. 
+    - Improvement - We are conducting a second audit of endpoints via [verify-stage#101](https://gitlab.com/gitlab-org/verify-stage/-/issues/101), which will help us reassign some of the ownership of the endpoints currently in Pipeline Execution to the right stage like Project Management or Pipeline Authoring.
   sisense_data:
     chart: 12190829
     dashboard: 892433
@@ -434,8 +433,8 @@
     - The [dashboards are located in grafana](https://dashboards.gitlab.net/d/stage-groups-runner/stage-groups-group-dashboard-verify-runner)
   lessons:
     learned:
-      - Insights - The error budget spend for June came in at 4.5 hours, a significant improvement compared to the previous months. The spend for the week ending July 2nd is 38.69 mins. These trends indicate that we are improving our service delivery capabilities. However, there continue to be times when there is service degradation. The overall rate of spend and loss of confidence by customers in the reliability of GitLab SaaS CI runners means that in Q3, we will continue to allocate at least 30% of the runner team's engineering budget to work on improving our deployment capabilities and CI Runners on .com stability and performance.
-      - Insights - For the week ending 2021-07-23, there is a slight uptick in the error budget spend of 0.23 hours. Even with the slight uptick, the trends over the past two weeks still point to the improved scalability and reliability of the CI runners on GitLab SaaS.
+      - Insights - The error budget spend for July came in at 1.8 hours, a significant improvement compared to the previous month (June 2021) of 4.5 hours. These trends indicate that we are improving our service delivery capabilities. However, there continue to be times when there is service degradation. The overall rate of spend and loss of confidence by customers in the reliability of GitLab SaaS CI runners means that in Q3, we will continue to allocate at least 30% of the runner team's engineering budget to work on improving our deployment capabilities and CI Runners on .com stability and performance.
+      - Insights - For the week ending 2021-07-30, there is a slight uptick in the error budget spend of 0.30 hours. Even with the slight uptick, the trends over the past three weeks still point to the improved scalability and reliability of the CI runners on GitLab SaaS. In addition, analysis of the performance of the runners under periods of high job load indicates that the CI runners Linux fleet is now able to manage the current typical demand profile and spikes in demand consistently.
   sisense_data:
     chart: 12190827
     dashboard: 892433
@@ -466,7 +465,7 @@
     status: Target
   lessons:
     learned:
-      - Insights - The average CI runners availability attained this week is 99.81%, which is .0.10% down from the previous week score of 99.91%.
+      - Insights - For the week ending 2021-07-30, the average CI runners' availability is 99.72%, which is 0.09%, down from the previous week's score of 99.81%. Over the past two weeks, the downward trend highlights the importance of continued focus and investment in Q3 on improving scalability and reliability for GitLab SaaS. On a positive note, the three-week moving average remains positive.  Finally, the average availability for Q3 is at 98.66%, a significant improvement over Q3, where the average CI runner availability was 90.91%.
       - Improvement - The [goal](https://gitlab.com/groups/gitlab-org/-/epics/6315) for the second half of this fiscal year is to achieve and maintain a weekly average SLO score of 99.95%.
   metric_name: gitlab-saas-ci-runners-slo-trends
   sisense_data:
@@ -987,7 +986,7 @@
 - name: Release:Release - Error Budget for GitLab.com
   base_path: "/handbook/product/performance-indicators/"
-  definition: The error budget provides a clear, objective metric that determines how unreliable the service is allowed to be within a single quarter. Spent budget is the time (in minutes) during which user facing services have experienced a percentage of errors below the specified threshold and latency is above the specified objectives for the service.
+  definition: The error budget provides a clear, objective metric that determines how unreliable the service is allowed to be within a single quarter. Spent budget is the time (in minutes) during which user facing services have experienced a percentage of errors below the specified threshold and latency is above the specified objectives for the service. The [dashboards are located in grafana](https://dashboards.gitlab.net/d/stage-groups-release/stage-groups-group-dashboard-release-release)
   target: 99.95% availability, allowed unavailability window is 20 minutes per month
   org: Product
   public: true
@@ -995,9 +994,9 @@
   health:
     level: 1
     reasons:
-    - 2021-06-19 - 99.57% Budget already spent
-    - This is a new PI and is a shared PI with [Infrastructure availability targets](/handbook/engineering/infrastructure/performance-indicators/#gitlabcom-availability)
-    - The [dashboards are located in grafana](https://dashboards.gitlab.net/d/stage-groups-release/stage-groups-group-dashboard-release-release)
+    - We are currently over our error budget
+      - 2021-06 - 99.57% 
+      - 2021-07 - 99.63%
   sisense_data:
     chart: 12191016
     dashboard: 892446
@@ -1006,6 +1005,9 @@
     chart: 12191018
     dashboard: 892446
     embed: v2
+  lessons:
+    learned:
+    - The release group has developed a process for using the Error Budget dashboards - see https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/87342/diffs
 - name: Configure:Configure - SMAU, GMAU - MAU of GitLab Managed Terraform State
   base_path: "/handbook/product/performance-indicators/ops-section-performance-indicators/"

data/projects.yml

@@ -75,13 +75,13 @@ gitlab-orchestrator:
     GitLab Orchestrator automates the installation of GitLab multi-node deployments,
     High Availability deployments, and GitLab Geo deployments.
-gitlab-openshift:
-  name: GitLab OpenShift Operator
-  path: gitlab-org/gl-openshift/gitlab-openshift
-  link: https://gitlab.com/gitlab-org/gl-openshift/gitlab-operator
+gitlab-operator:
+  name: GitLab Operator
+  path: gitlab-org/cloud-native/gitlab-operator
+  link: https://gitlab.com/gitlab-org/cloud-native/gitlab-operator
   description: |
-    The GitLab operator aims to manage the full lifecycle of GitLab and GitLab Runner instances,
-    in Kubernetes or Openshift container platforms.
+    The GitLab Operator aims to manage the full lifecycle of cloud native GitLab
+    instances, in Kubernetes and OpenShift container platforms.
 cookbook-omnibus-gitlab:
   name: Cookbook Omnibus GitLab
@@ -834,11 +834,11 @@ status-page:
     With the GitLab Status page, you can create and deploy a static website to communicate efficiently with users during an incident.
 cng:
-  name: CNG
+  name: Cloud Native GitLab containers
   path: gitlab-org/build/CNG
   link: https://gitlab.com/gitlab-org/build/CNG
   description: |
-    Docker images per component needed to run GitLab
+    Cloud native container images per component of GitLab
 release-cli:
   name: Release CLI

data/redirects.yml

@@ -4386,4 +4386,8 @@
     - /events/commit/
   target: https://gitlabcommitvirtual2021.com
   comp_op: '='
-
+- sources:
+    - /job-families/marketing/director-of-sales-development
+    - /job-families/marketing/director-of-sales-development/
+  target: /job-families/marketing/sales-development-leadership/
+  comp_op: '='

data/release_managers.yml

@@ -3,6 +3,7 @@
   manager_americas:
     - Mayra Cabrera
   manager_apac_emea:
+    - Reuben Pereira
   appsec:
 - version: '14.3'
@@ -19,7 +20,6 @@
     - Robert Speicher
   manager_apac_emea:
     - Henri Philipps
-    - Amy Phillips
   appsec:

data/sections.yml

@@ -17,7 +17,7 @@ ops:
   name: "Ops"
   slack:
     channel: ops-section
-  handbook: /handbook/product/categories/ops/
+  handbook: product/categories/ops/
   pm_team_tag: Ops Product Leadership
   development_team_tag: Ops Development Leadership
   support_team_tag: Ops Support Stable Counterpart

data/stages.yml

@@ -70,6 +70,44 @@ stages:
             dri: TBD
         categories:
           - authentication_and_authorization
+        usage_driver_score: 5
+        asp_driver_score: 4
+        sam_driver_score: 1
+        group_link: product/product-categories#access-group
+
+      workspace:
+        name: Workspace
+        pm: Orit Golowinski
+        focus: Manage Workspace Paid GMAU
+        pmm: Cindy Blake
+        cm: Suri Patel
+        backend_engineering_manager: Liam McAndrew
+        frontend_engineering_manager: Dennis Tang
+        be_team_tag: Manage:Access BE Team
+        fe_team_tag: Manage:Access FE Team
+        support:
+          - Cynthia Ng (SaaS)
+          - TBD (SM)
+        sets:
+          - Sanad Liaquat
+        pdm:
+          - Marcel van Remmerden (Interim)
+        ux:
+          - Daniel Mora
+        uxr:
+          - Anne Lasch
+        tech_writer: Evan Read
+        tw_backup: Marcel Amirault
+        appsec_engineer: Rohit Shambhuni
+        cs_team_tag: Access Group CS Stable Counterpart
+        internal_customers:
+          - department: Customer Support Department
+            dri: TBD
+          - department: Security Department
+            dri: TBD
+          - department: Infrastructure Department
+            dri: TBD
+        categories:
           - subgroups
           - users
         usage_driver_score: 5
@@ -191,10 +229,8 @@ stages:
             dri: TBD
         categories:
           - devops_reports
-          - planning_analytics
           - code_analytics
           - value_stream_management
-          - insights
         usage_driver_score: 2
         asp_driver_score: 2
         sam_driver_score: 3
@@ -263,6 +299,7 @@ stages:
           - boards
           - time_tracking
           - projects
+          - planning_analytics
         usage_driver_score: 5
         asp_driver_score: 4
         sam_driver_score: 5
@@ -546,24 +583,35 @@ stages:
         sam_driver_score: 1
         group_link: product/categories/#gitaly-group
-      ecosystem:
-        name: Ecosystem
-        description: "Supports the Contributor Ecosystem with 3rd party integrations, APIs, and contributor tools such as GDK and Pajamas."
+  ecosystem:
+    display_name: "Ecosystem"
+    marketing: false
+    tw: true
+    image: "/images/solutions/solutions-create.png"
+    description: "Supports the ecosystem with 3rd party integrations, APIs, and contributor tools such as GDK and Pajamas."
+    established: 2018
+    lifecycle: 0
+    usage_driver_score: 5
+    asp_driver_score: 4
+    sam_driver_score: 5
+    handbook: engineering/development/dev/create/ecosystem/
+    section: dev
+    pm: Melissa Ushakov
+    groups:
+      integrations:
+        name: Integrations
         pm: Melissa Ushakov
-        focus: Create Ecosystem GMAU
+        focus: Ecosystem Integrations GMAU
         pmm: Brian Glanz
         backend_engineering_manager: Arturo Herrero (Acting)
         frontend_engineering_manager: Lukas Eipert
-        be_team_tag: Ecosystem BE Team
-        fe_team_tag: Ecosystem FE Team
+        be_team_tag: Ecosystem:Integrations BE Team
+        fe_team_tag: Ecosystem:Integrations FE Team
         support: TBD
         pdm:
           - Marcel van Remmerden
-          - Taurie Davis (FE/UX Foundations)
         ux:
-          - Libor Vanc (Integrations)
-          - Jarek Ostrowski (FE/UX Foundations)
-          - Jeremy Elder (FE/UX Foundations)
+          - Libor Vanc
         uxr:
           - TBD
         tech_writer: Amy Qualls
@@ -572,7 +620,6 @@ stages:
         slack:
           channel: g_ecosystem
         gitlab_group: gitlab-org/ecosystem-team
-        handbook: engineering/development/dev/create/ecosystem/
         qm: Ramya Authappan
         sets:
           - TBD
@@ -589,16 +636,92 @@ stages:
           - department: Engineering Department
             dri: TBD
         categories:
-          - api
           - integrations
-          - gdk
+        group_link: product/categories/#ecosystem-group
+        usage_driver_score: 5
+        asp_driver_score: 4
+        sam_driver_score: 1
+      foundations:
+        name: Foundations
+        pm: Melissa Ushakov
+        focus: Driving Pajamas adoption
+        frontend_engineering_manager: Lukas Eipert
+        fe_team_tag: Ecosystem:Foundations Team
+        support: TBD
+        pdm:
+          - Taurie Davis
+        ux:
+          - Jarek Ostrowski
+          - Jeremy Elder
+        uxr:
+          - TBD
+        tech_writer: Amy Qualls
+        tw_backup: Russell Dickenson
+        appsec_engineer: Michael Henriksen
+        slack:
+          channel: g_ecosystem
+        gitlab_group: gitlab-org/ecosystem-team
+        qm: Ramya Authappan
+        sets:
+          - TBD
+        cs_team_tag: Ecosystem Group CS Stable Counterpart
+        internal_customers:
+          - department: Alliances Department
+            dri: TBD
+          - department: Customer Success
+            dri: TBD
+          - department: Quality Department
+            dri: TBD
+          - department: Infrastructure Department
+            dri: TBD
+          - department: Engineering Department
+            dri: TBD
+        categories:
           - foundations
-          - jira_importer
+        group_link: product/categories/#ecosystem-group
         usage_driver_score: 5
         asp_driver_score: 4
-        sam_driver_score: 5
+        sam_driver_score: 1
+      contributor_experience:
+        name: Contributor Experience
+        pm: Melissa Ushakov
+        focus: Making it easy to contribute to GitLab
+        frontend_engineering_manager: Lukas Eipert
+        be_team_tag: Ecosystem:Contributor Experience Team
+        support: TBD
+        pdm:
+          - TBD
+        ux:
+          - TBD
+        uxr:
+          - TBD
+        tech_writer: TBD
+        tw_backup: TBD
+        appsec_engineer: TBD
+        slack:
+          channel: g_ecosystem
+        gitlab_group: gitlab-org/ecosystem-team
+        qm: TBD
+        sets:
+          - TBD
+        cs_team_tag: Ecosystem Group CS Stable Counterpart
+        internal_customers:
+          - department: Alliances Department
+            dri: TBD
+          - department: Customer Success
+            dri: TBD
+          - department: Quality Department
+            dri: TBD
+          - department: Infrastructure Department
+            dri: TBD
+          - department: Engineering Department
+            dri: TBD
+        categories:
+          - gdk
         group_link: product/categories/#ecosystem-group
-
+        usage_driver_score: 5
+        asp_driver_score: 4
+        sam_driver_score: 1
   verify:
     display_name: "Verify"
     marketing: true
@@ -801,6 +924,7 @@ stages:
           - usability_testing
           - accessibility_testing
           - build_artifacts
+          - review_apps
         usage_driver_score: 4
         asp_driver_score: 2
         sam_driver_score: 3
@@ -870,7 +994,6 @@ stages:
           - dependency_proxy
           - dependency_firewall
           - git_lfs
-          - release_evidence
         usage_driver_score: 3
         asp_driver_score: 2
         sam_driver_score: 4
@@ -1103,7 +1226,7 @@ stages:
     description: "GitLab's integrated CD solution allows you to ship code with zero-touch, be it on one or one thousand servers."
     body: |
       GitLab helps automate the release and delivery of applications, shortening the delivery lifecycle, streamlining manual processes, and accelerating team velocity. With zero-touch Continuous Delivery (CD) built right into the pipeline, deployments can be automated to multiple environments like staging and production, and the system just knows what to do without being told - even for more advanced patterns like canary deployments. With feature flags, built-in auditing/traceability, on-demand environments, and GitLab pages for static content delivery, you'll be able to deliver faster and with more confidence than ever before.
-    direction: /direction/release
+    direction: /direction/deployment
     roadmap: "https://gitlab.com/groups/gitlab-org/-/roadmap?label_name%5B%5D=devops%3Arelease&scope=all&sort=end_date_asc&state=opened&layout=QUARTERS"
     established: 2016
     lifecycle: 4
@@ -1161,14 +1284,16 @@ stages:
         categories:
           - continuous_delivery
           - advanced_deployments
-          - review_apps
           - feature_flags
           - release_orchestration
+          - release_evidence
           - pages
         usage_driver_score: 4
         asp_driver_score: 3
         sam_driver_score: 4
         group_link: product/categories/#release-group
+        pi_gmau: "https://app.periscopedata.com/app/gitlab/777879/Release-Stage-Dashboard?widget=10279394&udv=0"
+        pi_pgmau: "https://app.periscopedata.com/app/gitlab/777879/Release-Stage-Dashboard?widget=10279447&udv=0"
   configure:
     display_name: "Configure"
@@ -1236,9 +1361,9 @@ stages:
           - kubernetes_management
           - cluster_cost_management
           - serverless
-          - secrets_management
           - chatops
           - runbooks
+          - secrets_management
         usage_driver_score: 2
         asp_driver_score: 2
         sam_driver_score: 4
@@ -1323,7 +1448,9 @@ stages:
         asp_driver_score: 1
         sam_driver_score: 4
         group_link: product/categories/#monitor-group
-
+        pi_gmau: https://app.periscopedata.com/app/gitlab/769975/Monitor-Stage-Dashboard?widget=10132068&udv=1176579
+        pi_pgmau: https://app.periscopedata.com/app/gitlab/769975/Monitor-Stage-Dashboard?widget=10199363&udv=1176579
+        comp_comparison: 
   protect:
     display_name: "Protect"

data/team_members/person/a/alex-kalderimis.yml

@@ -3,8 +3,8 @@ name: Alex Kalderimis
 start_date: 2019-05-02
 locality: Cambridge
 country: UK
-role: <a href="/job-families/engineering/development/backend">Senior Backend Engineer,
-  Ecosystem</a>
+role: <a href="/job-families/engineering/development/backend">Senior Backend Engineer</a>,
+  Ecosystem:Integrations
 reports_to: arturo-herrero
 picture: alexkalderimis.jpg
 twitter: involans
@@ -14,7 +14,7 @@ departments:
 - Engineering Function
 - Development Department
 - Dev Section
-- Ecosystem BE Team
+- Ecosystem:Integrations BE Team
 projects:
   gitlab: maintainer backend
   gitlab-gollum-lib: reviewer backend

data/team_members/person/a/andysoiron.yml

@@ -3,8 +3,8 @@ name: Andy Soiron
 start_date: 2019-11-01
 locality: Aachen
 country: Germany
-role: <a href="/job-families/engineering/development/backend">Senior Backend Engineer,
-  Ecosystem</a>
+role: <a href="/job-families/engineering/development/backend">Senior Backend Engineer</a>,
+  Ecosystem:Integrations
 reports_to: arturo-herrero
 picture: asoiron.jpg
 twitter: andysoiron
@@ -20,7 +20,7 @@ departments:
 - Engineering Function
 - Development Department
 - Dev Section
-- Ecosystem BE Team
+- Ecosystem:Integrations BE Team
 projects:
   gitlab:
   - trainee_maintainer backend

data/team_members/person/a/antonio-m.yml

----
-name: Antonio Mimmo
-start_date: 2018-03-15
-locality: Bratislava
-country: Slovakia
-role: <a href="/job-families/marketing/field-marketing-manager/">Manager, Field Marketing</a>
-reports_to: dir-fld-mktg
-picture: antoniomimmo.jpeg
-twitter: av_mimmo
-gitlab: amimmo
-departments:
-- Marketing
-- Revenue Marketing
-- Field Marketing
-story: 'Antonio is a passionate marketer and is well known for his talent to connect
-  people with brands, products and services. In his free time he likes to learn something
-  new every day and to produce music.
-
-'

data/team_members/person/a/arturo-herrero.yml

@@ -4,7 +4,7 @@ start_date: 2019-09-02
 locality: London
 country: United Kingdom
 role: <a href="/job-families/engineering/development/backend/#backend-manager-engineering">Acting
-  Backend Engineering Manager</a>, Create:Ecosystem
+  Backend Engineering Manager</a>, Ecosystem:Integrations
 reports_to: dsatcher
 picture: arturo-herrero.jpg
 twitter: ArturoHerrero
@@ -13,7 +13,7 @@ departments:
 - Engineering Function
 - Development Department
 - Dev Section
-- Ecosystem BE Team
+- Ecosystem:Integrations BE Team
 domain_expertise:
 - integrations
 projects:

data/team_members/person/a/ash-m.yml

@@ -3,8 +3,8 @@ name: Ash McKenzie
 start_date: 2018-04-10
 locality: Geelong
 country: Australia
-role: <a href="/job-families/engineering/development/backend">Staff Backend Engineer,
-  Ecosystem</a>
+role: <a href="/job-families/engineering/development/backend">Staff Backend Engineer</a>,
+  Ecosystem:Contributor Experience
 reports_to: leipert
 picture: ash-mckenzie.png
 twitter: ashmckenzie
@@ -13,7 +13,7 @@ departments:
 - Engineering Function
 - Development Department
 - Dev Section
-- Ecosystem BE Team
+- Ecosystem:Contributor Experience Team
 projects:
   gitlab-development-kit: maintainer
   gitlab-shell: maintainer

data/team_members/person/b/brian-w.yml

@@ -3,8 +3,8 @@ name: Brian Wald
 start_date: 2018-04-30
 locality: Traverse City, MI
 country: USA
-role: <a href="/job-families/sales/solutions-architect/#manager-solutions-architects">Manager,
-  Solutions Architects - US East</a>
+role: <a href="/job-families/sales/solutions-architect/#director-solutions-architects-responsibilities">
+  Director, Solutions Architecture</a>
 picture: brianwald.jpg
 reports_to: jonathan-fullam
 twitter: brianwald