Commit e4e017ff authored by Tim Zallmann's avatar Tim Zallmann

Refined Frontend OKR's fixed the indenting

parent 483326d6
Pipeline #43119732 passed with stages
in 13 minutes and 13 seconds
......@@ -83,18 +83,17 @@ Note: This is the first quarter where we [shift our fiscal year](https://about.g
1. [Philippe Lafoucrière](https://about.gitlab.com/company/team/#plafoucriere): Handover to new Secure Engineering Manager.
1. [Philippe Lafoucrière](https://about.gitlab.com/company/team/#plafoucriere): [CISSP](https://www.isc2.org/Certifications/CISSP) certification.
1. [Philippe Lafoucrière](https://about.gitlab.com/company/team/#plafoucriere): Benchmark 3 new security tools for integration in the [Security Products](https://about.gitlab.com/handbook/engineering/ops-backend/secure/#security_products).
1. Ops Backend: Define additional data to complement throughput: Implement a prototype for team pulse and define a path to implement it in GitLab product.
1. Dev Frontend + Backend: GA of GraphQL to increase throughput for BE and FE. Resolve general topics like performance, abuse prevention and enjoyable development experience. Endpoints for Create and Plan relevant models. Implement new frontend features in Create and Plan only with GraphQL.
1. Ops Backend: Define additional data to complement throughput: Implement a prototype for team pulse and define a path to implement it in GitLab product.
1. Dev Frontend & Backend (post re-org): GA of GraphQL to increase throughput for BE and FE. Resolve general topics like performance, abuse prevention and enjoyable development experience. Endpoints for Create and Plan relevant models. Implement new frontend features in Create and Plan only with GraphQL.
1. Verify: Formulate approach to utilize GraphQL in areas where data is requested across multiple endpoints or custom datasets would increase performance.
1. Release: Formulate approach to utilize GraphQL in areas where data is requested across multiple endpoints or custom datasets would increase performance.
1. Frontend: Increase throughput and reduce implementation time of Frontend features by 20%. By having at least 50 gitlab-ui components at the end of Q1. Increase velocity of CSS adaptions. Improve tooling in GitLab itself for JS engineering (webpack map, visual diffing, etc.).
1. Monitor: Create and start plan for removing css bloat and replacing GitLab components with components that match the design system.
1. Verify: Reduce implementation time by building on top of gitlab-ui components; increase throughput by building/improving upon JS and Frontend specific tooling.
1. Release: Reduce implementation time by building on top of gitlab-ui components; increase throughput by building/improving upon JS and Frontend specific tooling.
1. Manage: Increase throughput via proper backlog grooming, improved estimation, and proper issue planning. Also utilize gitlab-ui components to reduce implementation time.
1. Frontend: Improve Performance of JS computation that is done on every page by 10%. Improve Initialisation execution by 20%. Reduce main bundle size by 20%.
1. Configure: ES2015+ bundles for modern browsers & transpiled ES5 for older ones should reduce bundle size and parsing time
1. Manage: Fully integrate Sentry into the FE org workflow by updating the library, optimize and repair (loading order, configuration, sourcemap support), and determine process for fully utilizing it as an org. Also explore using it in dev, canary, and/or small percentage of production via A/B flipper.
1. Frontend: Increase velocity for frontend implementations. Increase throughput by 20%. Have at least 50 gitlab-ui components at the end of Q1. Improve tooling in GitLab itself for JS engineering (webpack map, visual diffing, etc.) by adding 3 new tools to our workflow.
1. Frontend Monitor: Remove 5% of our whole css bloat and implement styling for 4 gitlab-ui components.
1. Frontend Verify & Release: Reduce implementation time by building on top of gitlab-ui components; increase throughput by building/improving upon JS and Frontend specific tooling by doing product discovery for 2 new tools.
1. Frontend Manage: Increase throughput via proper backlog grooming, improved estimation, and proper issue planning. Also utilize all existing gitlab-ui components for Manage code.
1. Frontend: Improve [Performance of JS computation that is done on every page](https://gitlab.com/groups/gitlab-org/-/epics/716). Improve Initialisation execution by 20%. Reduce main bundle size by 20%.
1. Frontend Configure: Implement ES2015+ bundles for modern browsers & transpiled ES5 for older ones should reduce bundle size and parsing time
1. Frontend Manage: Fully integrate Sentry into the FE org workflow by updating the library, optimize and repair (loading order, configuration, sourcemap support), and determine process for fully utilizing it as an org. Also explore using it in dev, canary, and/or small percentage of production via A/B flipper.
1. Infrastructure: Make all user-visible services ready for mission-critical workloads while seamlessly supporting delivery of new product functionality and integrating infrastructure solutions in GitLab. [Availability] Definition and tracking of GitLab.com metrics for SLAs, [Product] Deliver OKR Infrastructure workflow and tooling using GitLab, [Introspective] Achieve a 10% cost reduction on GitLab.com spending.
1. Reliability[AS]: Support SRE-at-large MTBF and MTTR objectives. [Availability] Reduce spin-up time for provisioning auto-scaled servers to <3.5min, [Product] Automate error budgets as a GitLab feature, [Introspective] Deliver new testing environment.
1. Reliability[DS]: Drive all user-visible services' MTBF to Infinity. [Availability] Deliver improvements to GitLab.com reliability on two foundational subsystems (ZFS on storage, Kubernetes + Charts), [Product] Take full operational ownership of CI/CD (take oncall from tomscz), [Introspective] Operationalize Vault and Consul.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment