Datasets:

giseldo

/

neodataset

like 1

2020-12-28 20:37:17.610

Install and Setup Tailwind CSS on www.gitlab.com Repo for Production

We need to setup Tailwind CSS into our www.gitlab.com repo. Since we have already tested this framework and we are satisfied that its' the best direction, its imperative that we should start using it to develop our marketing pages. I have started the installation on this branch. https://gitlab.com/gitlab-com/www-gitlab-com/-/tree/tailwind-integrate-middleman

2020-12-28 17:43:40.854

Create "Continuous integration in Agile development" web article

<!-- This template is for requesting work related to the logged out [marketing website](https://about.gitlab.com/) and [company handbook](https://about.gitlab.com/handbook/). This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items. For information regarding working on the about website please visit the [Brand and Digital Handbook](https://about.gitlab.com/handbook/marketing/brand-and-digital-design/) You may link to this issue template using the following URL: https://gitlab.com/gitlab-com/www-gitlab-com/issues/new?issuable_template=-website-work-request --> #### What problem(s) are we trying to solve? What are the project goals? This will be a web article describing how to implement continuous integration that will be linked from the [CI/CD topics page](https://about.gitlab.com/topics/ci-cd/) #### Briefly describe your request Create a web article nested within the CI/CD topics page #### What is/are the relevant URL(s) https://about.gitlab.com/topics/ci-cd/continuous-integration-agile #### Please identify the directly responsible individual (DRI), stakeholders, and roles <!-- Who should we be asking for questions and reviews? Example in a markdown table: |Name|Role| |------|------| | `@cbuchanan` | DRI | | `tbd` | MPM | | `tbd` | PMM | | `tbd` | Design | --> #### Does this request require a form to capture registrations for a gated asset? - [x] No - [ ] Yes #### What are the project should-haves? This page should have the look and layout of other topics pages and sections at the bottom for listing other resources: eBooks, blogs, whitepapers, webcasts, etc #### What are the project could-haves? #### Where do you expect traffic to come from? * links from blogs * links from pdf assets * visitors searching for continuous integration topics online #### Please provide any related media files #### Will you need an opengraph image for social sharing? Not sure #### If applicable, please provide some example webpages for design guidance. Examples: * Pinterest implements recommendations well * Stripe has good payment UX * I like the aesthetics of nike.com * Animation examples, microinteractions, etc --> #### If applicable, do you have any user journeys, prototypes, content/data? #### Please create a checklist of deliverables in this phase - [x] Copy complete - [Draft](https://docs.google.com/document/d/1Gw7pppdf9QBSaAZsw0lfEla7FmoWRS5892JELkE6TWM/edit?usp=sharing) - [ ] First draft of page delivered - [ ] Page reviewed - [ ] Page live <!--THE END--> <!-- These labels will be automatically applied unless you edit or delete the following section -->

2020-12-23 17:02:38.383

Edit CD Solution Overview blog - The basics of GitLab CD

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/blog/ for details on the blog process. Unless you are just suggesting a blog post idea, you will need to create the formatted merge request for your blog post in order for it to be reviewed and published. --> ### Proposal Will edit and re-purpose this [unfiltered blog](https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/10238) https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/10238#note_473099796 ### Checklist - [ ] If you have a specific publish date in mind (please allow 3 weeks' lead time) - [ ] Include it in the issue title and apply the appropriate milestone (e.g. `Blogs October 2020`) - [ ] Give the issue a due date of a minimum of 2 working days prior - [ ] If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior - [ ] If [time sensitive](https://about.gitlab.com/handbook/marketing/blog/#process-for-time-sensitive-posts) - [ ] Add ~"Blog: Priority" label and supplied rationale in description - [ ] Mention `@rebecca` to give her a heads up ASAP - [ ] If wide-spread customer impacting or sensitive, mention `@nwoods` to give her a heads up ASAP, apply the ~"sensitive" label, and check the [PR handbook](https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements) in case you need to open an announcement request instead of a blog post issue - [ ] If the post is about one of GitLab's Technology Partners, including integration partners, mention `@arashidi`, apply the ~"Partner Marketing" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] If the post is about one of GitLab's customers, mention `@FionaOKeeffe`, apply the ~"Customer Reference Program" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] Indicate if supporting an event or campaign - [ ] Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment)

2020-12-23 16:55:01.132

Create separate CI and CD tags for the GitLab blog

With so much focus on Continuous Integration and Continuous Delivery as separate products, and with the creation of two separate topic pages, there is a greater need for separation of the two. Currently, we have one blog tag for CI/CD in the [blog handbook](https://about.gitlab.com/handbook/marketing/blog/#tags), but it looks like there are separate tags for CI and CD showing up [here](https://about.gitlab.com/blog/tags.html). Could we phase out the CI/CD blog tag and encourage using the CI and CD tags separately? Action Items: - [ ] Organize blogs under the existing CI/CD tag into either CI, CD, or both. - [ ] Update blog handbook to reflect two tags (CI and CD)

2020-12-23 16:26:35.141

Blog posts incorrectly placed in releases blog

This template is for filing a bug report related to the logged out marketing website https://about.gitlab.com/ and company handbook https://about.gitlab.com/handbook/ This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items. #### What is/are the relevant URL(s) https://about.gitlab.com/releases/2019/09/11/how-to-avoid-broken-master-with-pipelines-for-merge-requests/ #### Briefly describe the bug Some blog posts have been incorrectly placed in the releases blog repo. #### If possible, please specify how to reproduce the bug `Insert answer here` #### Please provide any relevant screenshots or screencasts How to take a screenshot: https://www.howtogeek.com/205375/how-to-take-screenshots-on-almost-any-device/ `Insert screenshot here` #### What is your window size, browser, operating system, and versions Please use the following website to determine your browser specifications and provide a link developers can follow: What is my browser https://www.whatsmybrowser.org `Insert results URL here` #### What computing device are you using? Please list the brand and model (Example: Samsung Galaxy S 10 Plus) `Insert answer here` #### Have you tried a fresh incognito window? Could this be related to cookies or account type/state? - [ ] I tried a fresh incognito window & it had no impact. - [ ] The problem goes away when using an incognito window. - [ ] The problem only happens when certain cookies are set to a specific value (please specify below). #### Please list any browser plugins you have enabled Why do we ask for this? Certain website bugs may be caused by plugins. For example: Adblock, noscript, ghostery, safe browsing. `Insert answer here` #### What is your geographic location Why do we ask for this? Certain bugs may be geographically related. For example, if you're in the European Union, it could be related to GDPR policy and cookies. `Insert answer here` #### What type of network are you connected to? **Type** - [ ] Wired - [ ] Wifi - [ ] Cellular (4G, 5G, etc) - [ ] Satellite - [ ] Other `Insert details here if applicable` **Location** - [ ] Home - [ ] Workplace - [ ] Travel facility (hotel, airport, conference center, etc) - [ ] Public venue (restaurant, library, cafe, etc) - [ ] VPN - [ ] Other `Insert details here if applicable` **Hardware** - [ ] I am behind a network security appliance such as a firewall - [ ] I am using a pi-hole or other hardware-based traffic blocker - [ ] Other `Insert details here if applicable` <!-- Please do not remove the items below, they are needed to automatically notify the relevant entities --> /cc @gl-website <!-- These labels will be automatically applied unless you edit or delete the following section -->

2020-12-16 20:06:18.254

Typos in blog post titles

#### What is/are the relevant URL(s) * https://about.gitlab.com/blog/2017/06/07/continous-integration-ticketmaster/ * typo from `continous` to `continuous` * https://about.gitlab.com/blog/2020/01/29/comparable-awards/ * typo from `comparable` to `comparably` #### Briefly describe the bug Example: A link is broken and when hovering over it the color is the wrong color and poorly aligned. `Certain blog post URLs have typos in them` #### Notes * [Related slack thread](https://gitlab.slack.com/archives/C2R1NED61/p1608069001225700). #### Deliverables * [ ] Update the URLs * [ ] Add redirects from old URL to new URL * [ ] MR reviewed by `@shanerice` and `@rebecca` <!-- These labels will be automatically applied unless you edit or delete the following section -->

2020-12-09 19:50:57.361

Blog Post: using GitLab SAST with Android - December 2020

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/blog/ for details on the blog process. Unless you are just suggesting a blog post idea, you will need to create the formatted merge request for your blog post in order for it to be reviewed and published. --> ### Proposal <!-- What do you want to blog about? Add your description here. If you are making an announcement, please open an `announcement` request issue in the Corporate Marketing project instead: https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements --> This blog post highlights the value of using GitLab SAST on Mobile Applications. It highlights specifically Android. I created a video as well as an application that user can clone and follow through with. ### Checklist - [x] If you have a specific publish date in mind (please allow 3 weeks' lead time) - [x] Include it in the issue title and apply the appropriate milestone (e.g. `Blogs October 2020`) - [x] Give the issue a due date of a minimum of 2 working days prior - [ ] If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior - [ ] If [time sensitive](https://about.gitlab.com/handbook/marketing/blog/#process-for-time-sensitive-posts) - [ ] Add ~"Blog: Priority" label and supplied rationale in description - [ ] Mention `@rebecca` to give her a heads up ASAP - [ ] If wide-spread customer impacting or sensitive, mention `@nwoods` to give her a heads up ASAP, apply the ~"sensitive" label, and check the [PR handbook](https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements) in case you need to open an announcement request instead of a blog post issue - [ ] If the post is about one of GitLab's Technology Partners, including integration partners, mention `@arashidi`, apply the ~"Partner Marketing" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] If the post is about one of GitLab's customers, mention `@FionaOKeeffe`, apply the ~"Customer Reference Program" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] Indicate if supporting an event or campaign - [ ] Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment)

2020-12-08 08:26:29.231

Fix Broken Link and Update "Where we are Headed"

The `Mock Press Release` link at https://about.gitlab.com/direction/plan/time_tracking/#where-we-are-headed hits a 404 (and also talks about September 2020 being in the future)- I think it could use an update :)  As a bit of an aside, I tried adding a comment here, in the hope somehow I could escalate/convert to an issue- https://gitlab.com/gitlab-com/www-gitlab-com/-/commit/779aac664fa6275e027c68754eecfbb68f1d8ff6#note_462135057 is there a clever way to do this that i'm missing?

2020-11-30 17:13:52.154

Blog post: How we prevented security fixes leaking into our public repositories (Dec 2020 / Jan 2021)

### Proposal Publish an engineering blog post about how we resolved these issues: * https://gitlab.com/gitlab-com/gl-infra/delivery/-/issues/426 * https://gitlab.com/gitlab-org/gitlab/-/issues/38386 * https://gitlab.com/gitlab-com/gl-infra/delivery/-/issues/914 ### Checklist - [x] If you have a specific publish date in mind (please allow 3 weeks' lead time) - [x] Include it in the issue title and apply the appropriate milestone (e.g. `Blogs October 2020`) - [ ] Give the issue a due date of a minimum of 2 working days prior - [-] If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior - [-] If [time sensitive](https://about.gitlab.com/handbook/marketing/blog/#process-for-time-sensitive-posts) - [-] Add ~"Blog: Priority" label and supplied rationale in description - [-] Mention `@rebecca` to give her a heads up ASAP - [-] If wide-spread customer impacting or sensitive, mention `@nwoods` to give her a heads up ASAP, apply the ~"sensitive" label, and check the [PR handbook](https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements) in case you need to open an announcement request instead of a blog post issue - [-] If the post is about one of GitLab's Technology Partners, including integration partners, mention `@arashidi`, apply the ~"Partner Marketing" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [-] If the post is about one of GitLab's customers, mention `@FionaOKeeffe`, apply the ~"Customer Reference Program" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [-] Indicate if supporting an event or campaign - [-] Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment)

2020-11-30 16:06:14.219

Blog post: Partial clone (TBD)

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/blog/ for details on the blog process. Unless you are just suggesting a blog post idea, you will need to create the formatted merge request for your blog post in order for it to be reviewed and published. --> ### Proposal (See https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/10021#note_456867365). Answering some Qs about partial clone. Previous post published on the topic: https://about.gitlab.com/blog/2020/03/13/partial-clone-for-massive-repositories/ Other resources: - Transcript: https://docs.google.com/document/d/18udLM2RRnA5y48w2qnAaGB0zHotbG3Wnu-NQfb-lBBk/edit?usp=sharing - https://gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/1421 - https://gitlab.com/groups/gitlab-org/-/epics/773 ### Checklist - [x] If you have a specific publish date in mind (please allow 3 weeks' lead time) - [x] Include it in the issue title and apply the appropriate milestone (e.g. `Blogs October 2020`) - [x] Give the issue a due date of a minimum of 2 working days prior - [ ] If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior - [ ] If [time sensitive](https://about.gitlab.com/handbook/marketing/blog/#process-for-time-sensitive-posts) - [ ] Add ~"Blog: Priority" label and supplied rationale in description - [ ] Mention `@rebecca` to give her a heads up ASAP - [ ] If wide-spread customer impacting or sensitive, mention `@nwoods` to give her a heads up ASAP, apply the ~"sensitive" label, and check the [PR handbook](https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements) in case you need to open an announcement request instead of a blog post issue - [ ] If the post is about one of GitLab's Technology Partners, including integration partners, mention `@arashidi`, apply the ~"Partner Marketing" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] If the post is about one of GitLab's customers, mention `@FionaOKeeffe`, apply the ~"Customer Reference Program" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] Indicate if supporting an event or campaign - [ ] Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment)

2020-11-26 10:31:16.136

News category missing from /blog

This template is for filing a bug report related to the logged out marketing website https://about.gitlab.com/ and company handbook https://about.gitlab.com/handbook/ This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items. #### What is/are the relevant URL(s) https://about.gitlab.com/blog/ #### Briefly describe the bug https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/68857 was merged to address https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/9985. Now the "News" category has disappeared from the blog homepage entirely and there is no way to view posts in this category:  #### If possible, please specify how to reproduce the bug Visit https://about.gitlab.com/blog/ #### Please provide any relevant screenshots or screencasts See above #### What is your window size, browser, operating system, and versions https://www.whatsmybrowser.org/b/91AC9 #### What computing device are you using? MacBook Pro 2020 #### Have you tried a fresh incognito window? Could this be related to cookies or account type/state? - [x] I tried a fresh incognito window & it had no impact. - [ ] The problem goes away when using an incognito window. - [ ] The problem only happens when certain cookies are set to a specific value (please specify below). #### Please list any browser plugins you have enabled N/A #### What is your geographic location EU #### What type of network are you connected to? **Type** - [ ] Wired - [x] Wifi - [ ] Cellular (4G, 5G, etc) - [ ] Satellite - [ ] Other `Insert details here if applicable` **Location** - [x] Home - [ ] Workplace - [ ] Travel facility (hotel, airport, conference center, etc) - [ ] Public venue (restaurant, library, cafe, etc) - [ ] VPN - [ ] Other `Insert details here if applicable` **Hardware** - [ ] I am behind a network security appliance such as a firewall - [ ] I am using a pi-hole or other hardware-based traffic blocker - [ ] Other `Insert details here if applicable` <!-- Please do not remove the items below, they are needed to automatically notify the relevant entities --> /cc @gl-website <!-- These labels will be automatically applied unless you edit or delete the following section -->

2020-11-25 16:37:31.232

Error occurred while installing nokogiri (1.10.10), and Bundler cannot continue on MacOS Big Sur

Installing the repo for the first time and ran into an issue when running `bundle install`. Lets diagnose what changes need to be made to our gemfile to fix this. ```` An error occurred while installing nokogiri (1.10.10), and Bundler cannot continue. Make sure that `gem install nokogiri -v '1.10.10' --source 'https://rubygems.org/'` succeeds before bundling. In Gemfile: capybara-screenshot was resolved to 1.0.25, which depends on capybara was resolved to 3.31.0, which depends on xpath was resolved to 3.2.0, which depends on nokogiri ```` #### System Information - macOS Big Sur - Version 11.0.1 - MacBook Pro 15 Inch 2018

2020-11-24 22:36:18.024

Create "How to find the right continuous integration tool" web article

<!-- This template is for requesting work related to the logged out [marketing website](https://about.gitlab.com/) and [company handbook](https://about.gitlab.com/handbook/). This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items. For information regarding working on the about website please visit the [Brand and Digital Handbook](https://about.gitlab.com/handbook/marketing/brand-and-digital-design/) You may link to this issue template using the following URL: https://gitlab.com/gitlab-com/www-gitlab-com/issues/new?issuable_template=-website-work-request --> #### What problem(s) are we trying to solve? What are the project goals? This will be a web article describing how to implement continuous integration that will be linked from the [CI/CD topics page](https://about.gitlab.com/topics/ci-cd/) #### Briefly describe your request Create a web article nested within the CI/CD topics page #### What is/are the relevant URL(s) https://about.gitlab.com/topics/ci-cd/choose-continuous-integration-tool This web article is repurposing an existing blog called **[How to find the right CI/CD solution](https://about.gitlab.com/blog/2019/07/15/finding-the-right-ci-cd/)** #### Please identify the directly responsible individual (DRI), stakeholders, and roles <!-- Who should we be asking for questions and reviews? Example in a markdown table: |Name|Role| |------|------| | `@cbuchanan` | DRI | | `tbd` | MPM | | `tbd` | PMM | | `tbd` | Design | --> #### Does this request require a form to capture registrations for a gated asset? - [x] No - [ ] Yes #### What are the project should-haves? This page should have the look and layout of other topics pages and sections at the bottom for listing other resources: eBooks, blogs, whitepapers, webcasts, etc #### What are the project could-haves? #### Where do you expect traffic to come from? * links from blogs * links from pdf assets * visitors searching for continuous integration topics online #### Please provide any related media files #### Will you need an opengraph image for social sharing? Not sure #### If applicable, please provide some example webpages for design guidance. Examples: * Pinterest implements recommendations well * Stripe has good payment UX * I like the aesthetics of nike.com * Animation examples, microinteractions, etc --> #### If applicable, do you have any user journeys, prototypes, content/data? #### Please create a checklist of deliverables in this phase - [x] Copy complete - [Draft](https://docs.google.com/document/d/1CpMvT2-gKlUVNvgk8R8QcUNI4So5Hq2usR-wxjoxyz4/edit?usp=sharing) - [x] First draft of page delivered - [ ] Page reviewed - [ ] Page live <!--THE END--> <!-- These labels will be automatically applied unless you edit or delete the following section -->

2020-11-24 21:25:58.866

Collections post: How our engineering team built things at GitLab (Jan 6)

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/blog/ for details on the blog process. Unless you are just suggesting a blog post idea, you will need to create the formatted merge request for your blog post in order for it to be reviewed and published. --> ### Proposal Some of our top-performing technical posts were about how our engineering team built certain features at GitLab or how our engineering team troubleshooted different problems on GitLab. This is our second collection post that has a round-up of the best technical content that fits this frame. ### Checklist - [ ] If you have a specific publish date in mind (please allow 3 weeks' lead time) - [ ] Include it in the issue title and apply the appropriate milestone (e.g. `Blogs October 2020`) - [ ] Give the issue a due date of a minimum of 2 working days prior - [ ] If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior - [ ] If [time sensitive](https://about.gitlab.com/handbook/marketing/blog/#process-for-time-sensitive-posts) - [ ] Add ~"Blog: Priority" label and supplied rationale in description - [ ] Mention `@rebecca` to give her a heads up ASAP - [ ] If wide-spread customer impacting or sensitive, mention `@nwoods` to give her a heads up ASAP, apply the ~"sensitive" label, and check the [PR handbook](https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements) in case you need to open an announcement request instead of a blog post issue - [ ] If the post is about one of GitLab's Technology Partners, including integration partners, mention `@arashidi`, apply the ~"Partner Marketing" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] If the post is about one of GitLab's customers, mention `@FionaOKeeffe`, apply the ~"Customer Reference Program" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] Indicate if supporting an event or campaign - [ ] Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment)

2020-11-21 07:32:56.308

Blog post: Learn more about Learn@GitLab - Jan 12

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/blog/ for details on the blog process. Unless you are just suggesting a blog post idea, you will need to create the formatted merge request for your blog post in order for it to be reviewed and published. --> ### Proposal Learn@GitLab is this beautiful resource that hasn't been promoted very much, so I'd like to write a blog about it and provide some details on how people can use it and link to a few of the videos and/or demos featured on the page. [Draft doc](https://docs.google.com/document/d/1gPh4wBM848iVQGTuFcB49kJZLMwu5BzYUiAmFCrLTMU/edit?usp=sharing) [Link to epic](https://gitlab.com/groups/gitlab-com/marketing/-/epics/954) ### Checklist - [x] If you have a specific publish date in mind (please allow 3 weeks' lead time) - [x] Include it in the issue title and apply the appropriate milestone (e.g. `Blogs October 2020`) - [x] Give the issue a due date of a minimum of 2 working days prior - [ ] If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior - [ ] If [time sensitive](https://about.gitlab.com/handbook/marketing/blog/#process-for-time-sensitive-posts) - [ ] Add ~"Blog: Priority" label and supplied rationale in description - [ ] Mention `@rebecca` to give her a heads up ASAP - [ ] If wide-spread customer impacting or sensitive, mention `@nwoods` to give her a heads up ASAP, apply the ~"sensitive" label, and check the [PR handbook](https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements) in case you need to open an announcement request instead of a blog post issue - [ ] If the post is about one of GitLab's Technology Partners, including integration partners, mention `@TinaS`, apply the ~"Partner Marketing" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] If the post is about one of GitLab's customers, mention `@KimLock` and `@FionaOKeeffe`, apply the ~"Customer Reference Program" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] Indicate if supporting an event or campaign - [ ] Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment)

2020-11-20 20:26:36.436

Handbook update: Add DIB checklist

<!-- This template is for requesting work related to the [company handbook](https://about.gitlab.com/handbook/). This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items. You may link to this issue template using the following URL: https://gitlab.com/gitlab-com/www-gitlab-com/issues/new?issuable_template=-handbook-update --> #### Briefly describe the update Drafting updates to the handbook so we can ensure all blog posts meet the DIB checklist criteria. This is a draft of the DIB checklist. <!-- These labels will be automatically applied unless you edit or delete the following section -->

2020-11-20 15:00:56.238

Set up markdown formatter that formats files following the Handbook’s Markdown style guide

### Proposal This is part of the effort to enforce a consistent markdown formatting style across Markdown pages in the Handbook. The goal is integrating a command line tool that formats markdown files following the [Handbook Markdown Style Guide](https://about.gitlab.com/handbook/markdown-guide/). There is an MR draft that implements the formatting tool. We plan to move these changes to a separate NPM repository to integrate the formatter in the Static Site Editor as well: https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/68569/

2020-11-19 19:42:29.939

Follow-up from "Homepage Redesign MVC2"

The following discussions from !66787 should be addressed: - [ ] @brandon_lyon started a [discussion](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/66787#note_451136114): (+2 comments) > Feedback from Slack this morning > > * White text link on white background under the customer case studies section. > * Video carousel on homepage is not inclusive/diverse, but this was a preexisting problem. > * Cookiebot might be blocking certain js on the homepage (icons on the devops tools comparison) > * "Learn more about our feature maturity" might not be linking to an appropriate spot.

2020-11-13 22:09:37.398

Make workflow diagram clickable

We made some progress on this but didn't merge the MR - https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/67804 We can use https://www.image-map.net/ to create the image map, however, the image is displayed at around 70% of the page width and the image map areas do not scale down, so the hotspots don't overlap with their parts of the diagram. The HTML looks like this: ``` <!-- Image Map Generated by http://www.image-map.net/ --> <img src="PDF-Diagram.svg" usemap="#image-map"> <!--> <map name="image-map"> <area target="_self" alt="Validation Backlog" title="Validation Backlog" href="/handbook/product-development-flow/product-development-flow-draft.html#validation-phase-1-validation-backlog" coords="175,253,305,333" shape="rect"> <area target="_self" alt="Problem Validation" title="Problem Validation" href="/handbook/product-development-flow/product-development-flow-draft.html#validation-phase-2-problem-validation" coords="92,197,65" shape="circle"> <area target="_self" alt="Design" title="Design" href="/handbook/product-development-flow/product-development-flow-draft.html#validation-phase-3-design" coords="166,81,43" shape="circle"> <area target="_self" alt="Solution Validation" title="Solution Validation" href="/handbook/product-development-flow/product-development-flow-draft.html#validation-phase-4-solution-validation" coords="388,198,64" shape="circle"> <area target="_self" alt="Plan" title="Plan" href="/handbook/product-development-flow/product-development-flow-draft.html#build-phase-1-plan" coords="538,159,672,242" shape="rect"> <area target="_self" alt="Develop and Test" title="Develop and Test" href="/handbook/product-development-flow/product-development-flow-draft.html#build-phase-2-develop--test" coords="679,73,811,154" shape="rect"> <area target="_self" alt="Launch" title="Launch" href="/handbook/product-development-flow/product-development-flow-draft.html#build-phase-3-launch" coords="820,160,951,239" shape="rect"> <area target="_self" alt="Improve" title="Improve" href="/handbook/product-development-flow/product-development-flow-draft.html#build-phase-4-improve" coords="677,251,812,332" shape="rect"> </map> ``` **Notes** - When copy/pasting from image-map.net, you will have to remove the indentation and re-add it from the beginning of each line. - The source file for the diagram is in [Figma](https://www.figma.com/file/ZHll9R1ER7IlSkpZrIiff3/Product-Development-Flow?node-id=0%3A1).

2020-11-13 19:49:15.622

How we do agile/sprints remotely - 2021-03-02

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/blog/ for details on the blog process. Unless you are just suggesting a blog post idea, you will need to create the formatted merge request for your blog post in order for it to be reviewed and published. --> ### Proposal Part of our [engineering + remote work series/collection](https://gitlab.com/gitlab-com/marketing/growth-marketing/global-content/editorial/-/issues/57#note_444393598), how we do agile and sprints remotely. Will add any relevant videos to the issue in description/comments. ### Questions for respondents * How does GitLab (the platform) enable teams to work more agilely? ([Here is a blog post we published on the topic](https://about.gitlab.com/blog/2018/03/05/gitlab-for-agile-software-development/), but I'd like to know your perspective as well) * How does your team specifically use sprints at GitLab? * Do you have experience working with Agile for software development while working in an office setting, at a previous company? * Do you feel that GitLab's structure as an all-remote async company makes it easier for programmers to work agilely? Why or why not? * Thinking specifically about Agile/sprints, what are some of the benefits of working in an office setting, with your colleagues next to you? What are some of the challenges? * Are there any major differences between conducting a sprint/Agile software development on an in-person team vs. an all-remote, asynchronous team? * What are some tools, strategies that are most useful for remote, Agile software development? Any links/resources I should include in this post? * What advice do you have for engineers that are adopting Agile for the first time, or are working remotely for the first time? * What else do I need to know but haven't asked? ### Some relevant links: - https://about.gitlab.com/blog/2020/11/11/gitlab-for-agile-portfolio-planning-project-management/ - https://about.gitlab.com/blog/2018/03/05/gitlab-for-agile-software-development/ - "[A Day in the Life of an Agilist](https://www.youtube.com/watch?v=5J0bonGoECs)" - Keynote from Virtual Commit: https://www.youtube.com/watch?v=t8BvRMalbkM&list=PLFGfElNsQthYQaTiUPQcu4O0O20WHZksz&index=10 ### Checklist - [x] If you have a specific publish date in mind (please allow 3 weeks' lead time) - [x] Include it in the issue title and apply the appropriate milestone (e.g. `Blogs October 2020`) - [x] Give the issue a due date of a minimum of 2 working days prior - [ ] If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior - [ ] If [time sensitive](https://about.gitlab.com/handbook/marketing/blog/#process-for-time-sensitive-posts) - [ ] Add ~"Blog: Priority" label and supplied rationale in description - [ ] Mention `@rebecca` to give her a heads up ASAP - [ ] If wide-spread customer impacting or sensitive, mention `@nwoods` to give her a heads up ASAP, apply the ~"sensitive" label, and check the [PR handbook](https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements) in case you need to open an announcement request instead of a blog post issue - [ ] If the post is about one of GitLab's Technology Partners, including integration partners, mention `@TinaS`, apply the ~"Partner Marketing" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] If the post is about one of GitLab's customers, mention `@KimLock` and `@FionaOKeeffe`, apply the ~"Customer Reference Program" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] Indicate if supporting an event or campaign - [ ] Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment)

2020-11-11 20:01:15.081

Creating People Data Team Catalog

Please select a template from the top left dropdown before continuing. This repository primarily relates to the logged out marketing website https://about.gitlab.com/ and company handbook https://about.gitlab.com/handbook/ This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items. If you do not select an appropriate template then your issue might get lost. For more information about our workflows, please reference the handbook for the marketing website https://about.gitlab.com/handbook/marketing/website/ or reference your team documentation. ### FAQ: Q: Which template should I use? A: Most people will use the "-website-bug-report" or "-handbook-update" issue templates. To request updates to existing pages or new content, please visit https://about.gitlab.com/handbook/marketing/growth-marketing/#requesting-support There are also templates for writing various kinds of blog posts including the unfiltered category. Please see the blog handbook for instructions before you open an issue: https://about.gitlab.com/handbook/marketing/blog/#publishing-process The rest of the templates are likely specific to team, role, or special occasion. Q: When will you get to this issue? A: Your issue will be refined and then prioritized relative to other issues. Marketing's website development team is currently an impacted resource. Q: How do I link to an issue template? A: https://gitlab.com/gitlab-com/www-gitlab-com/issues/new?issuable_template=name-of-template Q: How do I edit this FAQ? I have another question. A: Submit an issue https://gitlab.com/gitlab-com/www-gitlab-com/issues/new with FAQ in the title and assign it to @ brandon_lyon or another member of the website team https://about.gitlab.com/handbook/marketing/website/

2020-11-10 23:32:16.815

Register Here button on KubeCon Landing Page

Relates to https://gitlab.com/gitlab-com/marketing/growth-marketing/growth/-/issues/595

2020-11-10 23:05:23.874

Topic page sidebars phase 2

Relates to https://gitlab.com/gitlab-com/marketing/growth-marketing/growth/-/issues/640

2020-11-10 00:51:02.652

Make lifecycle icon banner mobile friendly

Let's make the lifecycle icon banner displayed on https://about.gitlab.com/upcoming-releases/ mobile friendly. This element was originally pulled from https://about.gitlab.com/devops-tools/. - Related https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/67340 - Related https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/8746/

2020-11-05 17:51:42.817

"Configure" misspelled in DevOps Lifecycle image

### Problem The DevOps Lifecycle image that is displayed at https://about.gitlab.com/stages-devops-lifecycle/ shows "CONFIGUR" instead of "CONFIGURE". This image is frequently-used, so this is a relatively high-visibility misspelling. ### Screenshot 

2020-11-04 19:03:55.836

Feature "How GitLab Pages uses the GitLab API to serve content" on main blog

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/corporate-marketing/content/editorial-team/#featuring-unfiltered-posts for details on the process for featuring Unfiltered blog posts on the main GitLab blog.--> <!-- Add a link to the original Unfiltered blog post and @ mention the author --> Feature How GitLab Pages uses the GitLab API to serve content https://about.gitlab.com/blog/2020/08/03/how-gitlab-pages-uses-the-gitlab-api-to-serve-content/ CC @jaime

2020-11-03 15:27:54.485

How to shift left with continuous integration web article

<!-- This template is for requesting work related to the logged out [marketing website](https://about.gitlab.com/) and [company handbook](https://about.gitlab.com/handbook/). This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items. For information regarding working on the about website please visit the [Brand and Digital Handbook](https://about.gitlab.com/handbook/marketing/brand-and-digital-design/) You may link to this issue template using the following URL: https://gitlab.com/gitlab-com/www-gitlab-com/issues/new?issuable_template=-website-work-request --> #### What problem(s) are we trying to solve? What are the project goals? This will be a web article describing the benefits of continuous integration that will be linked from the [CI/CD topics page](https://about.gitlab.com/topics/ci-cd/) #### Briefly describe your request Create a web article nested within the CI/CD topics page #### What is/are the relevant URL(s) https://about.gitlab.com/topics/ci-cd/shift-left-devops #### Please identify the directly responsible individual (DRI), stakeholders, and roles <!-- Who should we be asking for questions and reviews? Example in a markdown table: |Name|Role| |------|------| | `@cbuchanan` | DRI | | `tbd` | MPM | | `tbd` | PMM | | `tbd` | Design | --> #### Does this request require a form to capture registrations for a gated asset? - [x] No - [ ] Yes #### What are the project should-haves? This page should have the look and layout of other topics pages and sections at the bottom for listing other resources: eBooks, blogs, whitepapers, webcasts, etc #### What are the project could-haves? #### Where do you expect traffic to come from? * links from blogs * links from pdf assets * visitors searching for continuous integration topics online #### Please provide any related media files #### Will you need an opengraph image for social sharing? Not sure #### If applicable, please provide some example webpages for design guidance. Examples: * Pinterest implements recommendations well * Stripe has good payment UX * I like the aesthetics of nike.com * Animation examples, microinteractions, etc --> #### If applicable, do you have any user journeys, prototypes, content/data? #### Please create a checklist of deliverables in this phase - [x] Copy complete - [Draft](https://docs.google.com/document/d/1q2YZpV0DzgattC84mg-zzplOk3lqqWzJ5u7SvzUJVFA/edit?usp=sharing) - [ ] First draft of page delivered - [ ] Page reviewed - [ ] Page live <!--THE END--> <!-- These labels will be automatically applied unless you edit or delete the following section -->

2020-11-02 19:17:50.994

Blog: How pre-filled variables will make running pipelines easier - Dec 1

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/blog/ for details on the blog process. Unless you are just suggesting a blog post idea, you will need to create the formatted merge request for your blog post in order for it to be reviewed and published. --> ### Proposal https://gitlab.com/gitlab-com/marketing/growth-marketing/global-content/content-marketing/-/issues/241 *We have this feature coming out in 13.6 that I thought was really interesting and had a lot of engagement from the community.* - [Generate Run Pipeline form with pre-filled variables from .gitlab-ci.yml](https://gitlab.com/gitlab-org/gitlab/-/issues/30101) What made this topic interesting was that it had a lot of engagement (over 100 likes and several dozen comments). I would like to talk about this feature and also give three real-world examples of how this feature will impact workflows. Who will get the most value out of this feature? Is it something that saves time? Does it help users in some kind of specific way, and what examples can we give? ### Checklist - [x] If you have a specific publish date in mind (please allow 3 weeks' lead time) - [x] Include it in the issue title and apply the appropriate milestone (e.g. `Blogs October 2020`) - [ ] Give the issue a due date of a minimum of 2 working days prior - [ ] If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior - [ ] If [time sensitive](https://about.gitlab.com/handbook/marketing/blog/#process-for-time-sensitive-posts) - [ ] Add ~"Blog: Priority" label and supplied rationale in description - [ ] Mention `@rebecca` to give her a heads up ASAP - [ ] If wide-spread customer impacting or sensitive, mention `@nwoods` to give her a heads up ASAP, apply the ~"sensitive" label, and check the [PR handbook](https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements) in case you need to open an announcement request instead of a blog post issue - [ ] If the post is about one of GitLab's Technology Partners, including integration partners, mention `@TinaS`, apply the ~"Partner Marketing" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] If the post is about one of GitLab's customers, mention `@KimLock` and `@FionaOKeeffe`, apply the ~"Customer Reference Program" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] Indicate if supporting an event or campaign - [ ] Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment)

2020-11-02 19:08:57.258

Blog: How we're making migrating to GitLab CI easier - Dec 8

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/blog/ for details on the blog process. Unless you are just suggesting a blog post idea, you will need to create the formatted merge request for your blog post in order for it to be reviewed and published. --> ### Proposal https://gitlab.com/gitlab-com/marketing/growth-marketing/global-content/content-marketing/-/issues/232 We have a ton of documentation around making the migration process from Jenkins easier - let's talk about that. Found this product direction [here](https://about.gitlab.com/direction/verify/jenkins_importer/) and think it could be worth talking about. We could make this specific to how we're improving the migration process from Jenkins and use it for the Jenkins competitive campaign relaunch. Would like to see your thoughts on this. * [Reddit thread](https://www.reddit.com/r/devops/comments/8bxbyw/why_do_you_want_to_migrate_from_jenkins/) asking why you want to migrate from Jenkins Could also really use your help on the title. Should I say migrating from Jeknins or migrating to GitLab CI and then mentioning Jenkins in the subtitle? ### Checklist - [x] If you have a specific publish date in mind (please allow 3 weeks' lead time) - [x] Include it in the issue title and apply the appropriate milestone (e.g. `Blogs October 2020`) - [x] Give the issue a due date of a minimum of 2 working days prior - [ ] If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior - [ ] If [time sensitive](https://about.gitlab.com/handbook/marketing/blog/#process-for-time-sensitive-posts) - [ ] Add ~"Blog: Priority" label and supplied rationale in description - [ ] Mention `@rebecca` to give her a heads up ASAP - [ ] If wide-spread customer impacting or sensitive, mention `@nwoods` to give her a heads up ASAP, apply the ~"sensitive" label, and check the [PR handbook](https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements) in case you need to open an announcement request instead of a blog post issue - [ ] If the post is about one of GitLab's Technology Partners, including integration partners, mention `@TinaS`, apply the ~"Partner Marketing" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] If the post is about one of GitLab's customers, mention `@KimLock` and `@FionaOKeeffe`, apply the ~"Customer Reference Program" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [x] Indicate if supporting an event or campaign - Jenkins campaign - [ ] Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment)

2020-10-30 13:22:08.029

Collection: remote work + engineering - 2021-03-12

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/blog/ for details on the blog process. Unless you are just suggesting a blog post idea, you will need to create the formatted merge request for your blog post in order for it to be reviewed and published. --> ### Proposal Post collecting new and existing remote work + engineering stories. To include new posts: - https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/9899 - https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/9898 - https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/9809 - https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/9810 Older posts to be considered: - https://about.gitlab.com/blog/2020/08/27/measuring-engineering-productivity-at-gitlab/ - https://about.gitlab.com/blog/2019/06/03/how-we-turned-40-person-meeting-into-a-podcast/ ### Checklist - [ ] If you have a specific publish date in mind (please allow 3 weeks' lead time) - [x] Include it in the issue title and apply the appropriate milestone (e.g. `Blogs October 2020`) - [ ] Give the issue a due date of a minimum of 2 working days prior - [ ] If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior - [ ] If [time sensitive](https://about.gitlab.com/handbook/marketing/blog/#process-for-time-sensitive-posts) - [ ] Add ~"Blog: Priority" label and supplied rationale in description - [ ] Mention `@rebecca` to give her a heads up ASAP - [ ] If wide-spread customer impacting or sensitive, mention `@nwoods` to give her a heads up ASAP, apply the ~"sensitive" label, and check the [PR handbook](https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements) in case you need to open an announcement request instead of a blog post issue - [ ] If the post is about one of GitLab's Technology Partners, including integration partners, mention `@TinaS`, apply the ~"Partner Marketing" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] If the post is about one of GitLab's customers, mention `@KimLock` and `@FionaOKeeffe`, apply the ~"Customer Reference Program" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] Indicate if supporting an event or campaign - [ ] Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment)

2020-10-29 11:40:51.161

Feature Unfiltered posts

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/corporate-marketing/content/editorial-team/#featuring-unfiltered-posts for details on the process for featuring Unfiltered blog posts on the main GitLab blog.--> Unfiltered posts to consider for featuring: - https://about.gitlab.com/blog/2020/09/01/a-tale-of-two-editors/ - This reminds me of [this post](https://about.gitlab.com/blog/2020/02/27/how-holistic-ux-design-increased-gitlab-free-trial-signups/) which got over 1,700 unique views in 2 months after publishing. Probably only needs a light edit. - https://about.gitlab.com/blog/2020/08/03/how-gitlab-pages-uses-the-gitlab-api-to-serve-content/ - This seems like a classic technical post about a popular feature. These posts both got >200 unique views as Unfiltered posts.

2020-10-28 20:31:22.988

CI blogs for repurpose

I went through the spreadsheet of blogs [grouped by topic](https://docs.google.com/spreadsheets/d/15RorS3Y7fRHWoIaNR-37Oq34F_xRyihAjXM_o-yXous/edit?usp=sharing) and selected some CI blogs that would be good candidates for repurposing into web articles. ## [How to find the right CI/CD solution](https://about.gitlab.com/blog/2019/07/15/finding-the-right-ci-cd/) This can be some helpful content that isn't GitLab-focused, and provides some good action steps that would fit into the CI topic page. ## [4 Benefits of CI/CD](https://about.gitlab.com/blog/2019/06/27/positive-outcomes-ci-cd/) I can roll the benefits section into the existing benefits of continuous integration, but there's a section in this blog about measuring CI success that would be good for its own web article ## [Defending the CI/CD pipeline](https://about.gitlab.com/blog/2019/11/19/defend-cicd-security/) Tips for defending pipelines would work well for CI ## [CI/CD: The ticket to multicloud](https://about.gitlab.com/blog/2020/01/17/ci-cd-the-ticket-to-multicloud/) I think his would be a good tie in for CI or it could be a good web article for the multicloud page on "How to implement multicloud" or "the challenges of multicloud"

2020-10-23 14:00:04.009

Collection post: How to do XYZ with GitLab (Dec 17)

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/blog/ for details on the blog process. Unless you are just suggesting a blog post idea, you will need to create the formatted merge request for your blog post in order for it to be reviewed and published. --> ### Proposal "Collection" post highlighting our most popular engineering stories, including blog posts and potentially select videos from Commit sessions (https://gitlab.com/gitlab-com/marketing/growth-marketing/global-content/editorial/-/issues/43). Supporting https://gitlab.com/groups/gitlab-com/marketing/growth-marketing/-/epics/137. ### Checklist - [x] If you have a specific publish date in mind (please allow 3 weeks' lead time) - [x] Include it in the issue title and apply the appropriate milestone (e.g. `Blogs October 2020`) - [x] Give the issue a due date of a minimum of 2 working days prior - [ ] If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior - [ ] If [time sensitive](https://about.gitlab.com/handbook/marketing/blog/#process-for-time-sensitive-posts) - [ ] Add ~"Blog: Priority" label and supplied rationale in description - [ ] Mention `@rebecca` to give her a heads up ASAP - [ ] If wide-spread customer impacting or sensitive, mention `@nwoods` to give her a heads up ASAP, apply the ~"sensitive" label, and check the [PR handbook](https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements) in case you need to open an announcement request instead of a blog post issue - [ ] If the post is about one of GitLab's Technology Partners, including integration partners, mention `@TinaS`, apply the ~"Partner Marketing" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] If the post is about one of GitLab's customers, mention `@KimLock` and `@FionaOKeeffe`, apply the ~"Customer Reference Program" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] Indicate if supporting an event or campaign - [ ] Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment)

2020-10-19 15:34:48.574

Temporarily disable related blog posts

Relates to https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/65289#note_431800820

2020-10-18 15:53:42.459

Correct graphics on DevSecOps image

This template is for filing a bug report related to the logged out marketing website https://about.gitlab.com/ and company handbook https://about.gitlab.com/handbook/ This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items. #### What is/are the relevant URL(s) The page is https://about.gitlab.com/solutions/dev-sec-ops. This page is a key asset in the DevSecOps campaign and in all security communications. Please correct it asap. #### Briefly describe the bug The graphics for DevSecOps were improperly modified changing the message incorrectly #### If possible, please specify how to reproduce the bug This is the graphic that is incorrect:  #### Please provide any relevant screenshots or screencasts This arrow is pointing the wrong direction. It should point FROM the review app TO the actions. It is intended to create an iterative circle in which the developer works. The message is totally lost with the current image.  While the image is being changed, please move the security dashboard over to the right to visually separate the security activity from the iterative developer activity.  It should be in keeping with the original graphic here.  #### What is your window size, browser, operating system, and versions Please use the following website to determine your browser specifications and provide a link developers can follow: What is my browser https://www.whatsmybrowser.org Chrome 86 #### What computing device are you using? Please list the brand and model (Example: Samsung Galaxy S 10 Plus) Apple macbook #### Have you tried a fresh incognito window? Could this be related to cookies or account type/state? not applicable - [ ] I tried a fresh incognito window & it had no impact. - [ ] The problem goes away when using an incognito window. - [ ] The problem only happens when certain cookies are set to a specific value (please specify below). #### Please list any browser plugins you have enabled Why do we ask for this? Certain website bugs may be caused by plugins. For example: Adblock, noscript, ghostery, safe browsing. not applicable #### What is your geographic location Why do we ask for this? Certain bugs may be geographically related. For example, if you're in the European Union, it could be related to GDPR policy and cookies. USA #### What type of network are you connected to? **Type** - [ ] Wired - [x] Wifi - [ ] Cellular (4G, 5G, etc) - [ ] Satellite - [ ] Other `Insert details here if applicable` **Location** - [x] Home - [ ] Workplace - [ ] Travel facility (hotel, airport, conference center, etc) - [ ] Public venue (restaurant, library, cafe, etc) - [ ] VPN - [ ] Other `Insert details here if applicable` **Hardware** n/a - [ ] I am behind a network security appliance such as a firewall - [ ] I am using a pi-hole or other hardware-based traffic blocker - [ ] Other `Insert details here if applicable` <!-- Please do not remove the items below, they are needed to automatically notify the relevant entities --> /cc @gl-website <!-- These labels will be automatically applied unless you edit or delete the following section -->

2020-10-16 18:55:41.971

Remove lightning talk from Hashicorp page

Relates to https://gitlab.com/gitlab-com/marketing/growth-marketing/growth/-/issues/477

2020-10-14 15:57:33.947

Blog post: How Kamil created the DevOps platform software category from Poland (Oct 29)

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/blog/ for details on the blog process. Unless you are just suggesting a blog post idea, you will need to create the formatted merge request for your blog post in order for it to be reviewed and published. --> ### Proposal Sid: I propose I write an article headlined: How Kamil created the DevOps platform software category from Poland. It will first talk about the Gartner validation including "Our definition of VSDP does not describe a system that cobbles together disparate DevOps tools. Instead, we view VSDPs as integrated platforms that enhance productivity, collaboration, communication, and business outcomes for product teams via interactions between the platform components." Then, how Kamil advocated for integrating GitLab SCM with CI in 2016. Helpful links: - [Gartner Market Guide for DevOps Value Stream Delivery Platforms](https://drive.google.com/file/d/1qHpdyCPDHgdfID56_io_-vwXHXjH7PH2/view?usp=sharing) - [Gartner Hype Cycle for Agile and DevOps, 2020 (pages 13-15)](https://drive.google.com/file/d/1gRIZc82ShZAw_3W8mC1QSLb7hIh-I8jr/view?usp=sharing) - [Handbook: Developing a new category](https://about.gitlab.com/analysts/#thought-leadership-analysts) - [Gartner Market Guide Methodology](https://www.gartner.com/en/research/methodologies/market-guide) - [HBR: Why it pays to be a category creator](https://hbr.org/2013/03/why-it-pays-to-be-a-category-creator) ### Checklist - [ ] If you have a specific publish date in mind (please allow 3 weeks' lead time) - [ ] Include it in the issue title - [ ] Give the issue a due date of a minimum of 2 working days prior - [ ] If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior - [ ] If [time sensitive](https://about.gitlab.com/handbook/marketing/blog/#process-for-time-sensitive-posts) - [ ] Add ~"Blog: Priority" label and supplied rationale in description - [ ] Mention `@rebecca` to give her a heads up ASAP - [ ] If wide-spread customer impacting or sensitive, mention `@nwoods` to give her a heads up ASAP, apply the ~"sensitive" label, and check the [PR handbook](https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements) in case you need to open an announcement request instead of a blog post issue - [ ] If the post is about one of GitLab's Technology Partners, including integration partners, mention `@TinaS`, apply the ~"Partner Marketing" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] If the post is about one of GitLab's customers, mention `@KimLock` and `@FionaOKeeffe`, apply the ~"Customer Reference Program" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] Indicate if supporting an event or campaign - [ ] Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment)

2020-10-12 23:20:11.776

Continuous integration best practices web article

<!-- This template is for requesting work related to the logged out [marketing website](https://about.gitlab.com/) and [company handbook](https://about.gitlab.com/handbook/). This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items. For information regarding working on the about website please visit the [Brand and Digital Handbook](https://about.gitlab.com/handbook/marketing/brand-and-digital-design/) You may link to this issue template using the following URL: https://gitlab.com/gitlab-com/www-gitlab-com/issues/new?issuable_template=-website-work-request --> #### What problem(s) are we trying to solve? What are the project goals? This will be a web article describing continuous integration best practices that will be linked from the [CI/CD topics page](https://about.gitlab.com/topics/ci-cd/) #### Briefly describe your request Create a web article nested within the CI/CD topics page #### What is/are the relevant URL(s) https://about.gitlab.com/topics/ci-cd/continuous-integration-best-practices #### Please identify the directly responsible individual (DRI), stakeholders, and roles <!-- Who should we be asking for questions and reviews? Example in a markdown table: |Name|Role| |------|------| | `@cbuchanan` | DRI | | `tbd` | MPM | | `tbd` | PMM | | `tbd` | Design | --> #### Does this request require a form to capture registrations for a gated asset? - [x] No - [ ] Yes #### What are the project should-haves? This page should have the look and layout of other topics pages and sections at the bottom for listing other resources: eBooks, blogs, whitepapers, webcasts, etc #### What are the project could-haves? #### Where do you expect traffic to come from? * links from blogs * links from pdf assets * visitors searching for continuous integration topics online #### Please provide any related media files #### Will you need an opengraph image for social sharing? Not sure #### If applicable, please provide some example webpages for design guidance. Examples: * Pinterest implements recommendations well * Stripe has good payment UX * I like the aesthetics of nike.com * Animation examples, microinteractions, etc --> #### If applicable, do you have any user journeys, prototypes, content/data? #### Please create a checklist of deliverables in this phase - [x] Copy complete - [Draft](https://docs.google.com/document/d/1vy7N3gWUhd7lcDMG-rEePiF1ImNrELRG1xpxjgiGyis/edit?usp=sharing) - [ ] First draft of page delivered - [ ] Page reviewed - [ ] Page live <!--THE END--> <!-- These labels will be automatically applied unless you edit or delete the following section -->

2020-10-12 19:13:13.205

What is pipeline as code article

<!-- This template is for requesting work related to the logged out [marketing website](https://about.gitlab.com/) and [company handbook](https://about.gitlab.com/handbook/). This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items. For information regarding working on the about website please visit the [Brand and Digital Handbook](https://about.gitlab.com/handbook/marketing/brand-and-digital-design/) You may link to this issue template using the following URL: https://gitlab.com/gitlab-com/www-gitlab-com/issues/new?issuable_template=-website-work-request --> #### What problem(s) are we trying to solve? What are the project goals? This will be a web article describing pipeline as code that will be linked from the [CI/CD topics page](https://about.gitlab.com/topics/ci-cd/) #### Briefly describe your request Create a web article nested within the CI/CD topics page #### What is/are the relevant URL(s) https://about.gitlab.com/topics/ci-cd/pipeline-as-code #### Please identify the directly responsible individual (DRI), stakeholders, and roles <!-- Who should we be asking for questions and reviews? Example in a markdown table: |Name|Role| |------|------| | `@cbuchanan` | DRI | | `tbd` | MPM | | `tbd` | PMM | | `tbd` | Design | --> #### Does this request require a form to capture registrations for a gated asset? - [x] No - [ ] Yes #### What are the project should-haves? This page should have the look and layout of other topics pages and sections at the bottom for listing other resources: eBooks, blogs, whitepapers, webcasts, etc #### What are the project could-haves? #### Where do you expect traffic to come from? * links from blogs * links from pdf assets * visitors searching for continuous integration topics online #### Please provide any related media files #### Will you need an opengraph image for social sharing? Not sure #### If applicable, please provide some example webpages for design guidance. Examples: * Pinterest implements recommendations well * Stripe has good payment UX * I like the aesthetics of nike.com * Animation examples, microinteractions, etc --> #### If applicable, do you have any user journeys, prototypes, content/data? #### Please create a checklist of deliverables in this phase - [x] Copy complete - [Draft](https://docs.google.com/document/d/19R8JPLfo5dpIlSHpFdIpeQTI_sJMkzN4TS2t5sJNsk0/edit?usp=sharing) - [ ] First draft of page delivered - [ ] Page reviewed - [ ] Page live <!--THE END--> <!-- These labels will be automatically applied unless you edit or delete the following section -->

2020-10-08 20:56:24.289

How a continuous integration pipeline works web article

<!-- This template is for requesting work related to the logged out [marketing website](https://about.gitlab.com/) and [company handbook](https://about.gitlab.com/handbook/). This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items. For information regarding working on the about website please visit the [Brand and Digital Handbook](https://about.gitlab.com/handbook/marketing/brand-and-digital-design/) You may link to this issue template using the following URL: https://gitlab.com/gitlab-com/www-gitlab-com/issues/new?issuable_template=-website-work-request --> #### What problem(s) are we trying to solve? What are the project goals? This will be a web article describing the benefits of continuous integration that will be linked from the [CI/CD topics page](https://about.gitlab.com/topics/ci-cd/) #### Briefly describe your request Create a web article nested within the CI/CD topics page #### What is/are the relevant URL(s) https://about.gitlab.com/topics/ci-cd/continuous-integration-pipeline #### Please identify the directly responsible individual (DRI), stakeholders, and roles <!-- Who should we be asking for questions and reviews? Example in a markdown table: |Name|Role| |------|------| | `@cbuchanan` | DRI | | `tbd` | MPM | | `tbd` | PMM | | `tbd` | Design | --> #### Does this request require a form to capture registrations for a gated asset? - [x] No - [ ] Yes #### What are the project should-haves? This page should have the look and layout of other topics pages and sections at the bottom for listing other resources: eBooks, blogs, whitepapers, webcasts, etc #### What are the project could-haves? #### Where do you expect traffic to come from? * links from blogs * links from pdf assets * visitors searching for continuous integration topics online #### Please provide any related media files #### Will you need an opengraph image for social sharing? Not sure #### If applicable, please provide some example webpages for design guidance. Examples: * Pinterest implements recommendations well * Stripe has good payment UX * I like the aesthetics of nike.com * Animation examples, microinteractions, etc --> #### If applicable, do you have any user journeys, prototypes, content/data? #### Please create a checklist of deliverables in this phase - [x] Copy complete - [Draft](https://docs.google.com/document/d/1-fnVAf0fZIl2O3vr6fSkSTeyz7iX6-FD7S3dsPtQErI/edit?usp=sharing) - [ ] First draft of page delivered - [ ] Page reviewed - [ ] Page live <!--THE END--> <!-- These labels will be automatically applied unless you edit or delete the following section -->

2020-10-08 17:51:35.476

The benefits of continuous integration web article

<!-- This template is for requesting work related to the logged out [marketing website](https://about.gitlab.com/) and [company handbook](https://about.gitlab.com/handbook/). This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items. For information regarding working on the about website please visit the [Brand and Digital Handbook](https://about.gitlab.com/handbook/marketing/brand-and-digital-design/) You may link to this issue template using the following URL: https://gitlab.com/gitlab-com/www-gitlab-com/issues/new?issuable_template=-website-work-request --> #### What problem(s) are we trying to solve? What are the project goals? This will be a web article describing the benefits of continuous integration that will be linked from the [CI/CD topics page](https://about.gitlab.com/topics/ci-cd/) #### Briefly describe your request Create a web article nested within the CI/CD topics page #### What is/are the relevant URL(s) https://about.gitlab.com/topics/ci-cd/benefits-continuous-integration #### Please identify the directly responsible individual (DRI), stakeholders, and roles <!-- Who should we be asking for questions and reviews? Example in a markdown table: |Name|Role| |------|------| | `@cbuchanan` | DRI | | `tbd` | MPM | | `tbd` | PMM | | `tbd` | Design | --> #### Does this request require a form to capture registrations for a gated asset? - [x] No - [ ] Yes #### What are the project should-haves? This page should have the look and layout of other topics pages and sections at the bottom for listing other resources: eBooks, blogs, whitepapers, webcasts, etc #### What are the project could-haves? #### Where do you expect traffic to come from? * links from blogs * links from pdf assets * visitors searching for continuous integration topics online #### Please provide any related media files #### Will you need an opengraph image for social sharing? Not sure #### If applicable, please provide some example webpages for design guidance. Examples: * Pinterest implements recommendations well * Stripe has good payment UX * I like the aesthetics of nike.com * Animation examples, microinteractions, etc --> #### If applicable, do you have any user journeys, prototypes, content/data? #### Please create a checklist of deliverables in this phase - [x] Copy complete - [Draft](https://docs.google.com/document/d/1etfMVnLvzLbjGpv2pnh3sH1URxaB9aXJt3WLaoz_ABo/edit?usp=sharing) - [x] First draft of page delivered - [ ] Page reviewed - [ ] Page live <!--THE END--> <!-- These labels will be automatically applied unless you edit or delete the following section -->

2020-10-02 16:13:37.297

Refactor and add tests for `generators/releases.rb`

- Refactor code - Add tests The following discussion from !64079 should be addressed: - [ ] @sean_carroll started a [discussion](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/64079#note_422673457): (+1 comment) > Hi @nfriend thanks for this change! > > In reviewing the code, I was surprised to see that there are no tests for the existing code, before the changes on this MR. It is moderately complex code, and it is also quite visible being on our main website. > > I think we should take this opportunity to add a spec for `generators/release`, we can use https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/spec/generators/org_chart_spec.rb as a model. > > I'm happy to help with this if useful. > > Back to you :ping_pong:

2020-10-01 20:56:53.529

Commit - on demand links switched to youtube playlist

Relates to https://gitlab.com/gitlab-com/marketing/growth-marketing/growth/-/issues/439 ## Deliverables - [x] Switch "view on demand" button URLS from `https://gitlabcommitvirtual.com/` to `https://www.youtube.com/c/Gitlab/playlists?view=50&sort=dd&shelf_id=5` - [x] Swap the video recap section with a video slider of the above playlist. - [x] Replace the Sched embed with a PDF. - [x] Temporarily add then remove the manual_cookiebot frontmatter.

2020-09-28 16:24:39.108

Bug fix: # in blog frontmatter tweet field truncates the click to tweet

This template is for filing a bug report related to the logged out marketing website https://about.gitlab.com/ and company handbook https://about.gitlab.com/handbook/ This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items. #### What is/are the relevant URL(s) about.gitlab.com/blog #### Briefly describe the bug If a # is used in the blog's tweet line in the front matter the click-to-tweet feature is truncated right before the hashtag. #### If possible, please specify how to reproduce the bug Just insert a # in the "tweet" line in the blog front matter. <!-- Please do not remove the items below, they are needed to automatically notify the relevant entities --> /cc @gl-website <!-- These labels will be automatically applied unless you edit or delete the following section -->

2020-09-27 19:21:41.152

Dead link [bind us as a company] in jobs/faq

#### What is/are the relevant URL(s) [https://about.gitlab.com/jobs/faq/#gitlabs-outbound-recruiting-model](https://about.gitlab.com/jobs/faq/#gitlabs-outbound-recruiting-model) [https://about.gitlab.com/jobs/faq/handbook/leadership/biggest-risks/#loss-of-the-values-that-bind-us](https://about.gitlab.com/jobs/faq/handbook/leadership/biggest-risks/#loss-of-the-values-that-bind-us) #### Briefly describe the bug The link `bind us as a company` in **GitLab’s outbound recruiting model** section is broken and produces a 404 error. #### If possible, please specify how to reproduce the bug Click on the link `bind us as a company` on the page "Jobs at GitLab - FAQ", section **GitLab’s outbound recruiting model** #### What is your window size, browser, operating system, and versions `https://www.whatsmybrowser.org/b/QZ3DM` #### What computing device are you using? Custom build PC. #### Have you tried a fresh incognito window? Could this be related to cookies or account type/state? - [x] I tried a fresh incognito window & it had no impact. - [ ] The problem goes away when using an incognito window. - [ ] The problem only happens when certain cookies are set to a specific value (please specify below). #### Please list any browser plugins you have enabled Why do we ask for this? Certain website bugs may be caused by plugins. For example: Adblock, noscript, ghostery, safe browsing. - Adblock Plus - DuckDuckGo Privacy Essentials - Facebook Container #### What is your geographic location Europe / France #### What type of network are you connected to? **Type** - [x] Wired - [ ] Wifi - [ ] Cellular (4G, 5G, etc) - [ ] Satellite - [ ] Other **Location** - [x] Home - [ ] Workplace - [ ] Travel facility (hotel, airport, conference center, etc) - [ ] Public venue (restaurant, library, cafe, etc) - [ ] VPN - [ ] Other **Hardware** - [ ] I am behind a network security appliance such as a firewall - [ ] I am using a pi-hole or other hardware-based traffic blocker - [ ] Other <!-- Please do not remove the items below, they are needed to automatically notify the relevant entities --> /cc @gl-website <!-- These labels will be automatically applied unless you edit or delete the following section -->

2020-09-25 17:08:38.652

Links to blog posts from review app wrong for file names with uppercase letters

Blog post urls are automatically downcased during the build. This is good because mixed case URLs are bad for SEO. However, when a review app links directly to blog post with a mixed case file name, it returns a error. This is because the review app link doesn't change the URL link to all downcase. For example, a blog post file name of `2020-09-30-Q3-hackathon-recap.html.md.erb` will directly link to this URL from the review app this https://hackathon-recap.about.gitlab-review.app/blog/2020/09/30/Q3-hackathon-recap/index.html. That will return an "no file found" xml error because the of the mixed casing. The correct and reachable URL is https://hackathon-recap.about.gitlab-review.app/blog/2020/09/30/q3-hackathon-recap/index.html The related MR to the blog post is [here](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/63488). I have also encountered this issue with other MRs too. Can we get the review app to link to the correct blog post?

2020-09-23 17:46:09.496

Update scss lint rules

Per slack, @laurenbarker could we look into disabling the following scss lint rules? * `no-qualifying-elements` * ~~`class-name-format`~~

2020-09-17 08:44:02.685

Define outcomes and activities for Validation phase 2: Problem validation

Associated MR: https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/63272 **Problems to solve:** - [x] Doesn’t Encourage Cross-Functional Collaboration - [x] Too Many Steps - [x] Too Prescriptive Detailed problems to solve for reference: https://docs.google.com/presentation/d/1BxUVcoPyjYkR7MOHn1aZGllMCqlH5eb27JKM_bb_uDA/edit#slide=id.g94724597ab_3_0 **Requirements:** (can fall into multiple MRs) - [x] Do not remove or change workflow labels - [x] Maintain or add clarity on what is REQUIRED per https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/9090 - [x] Maintain or add clarity on who the cross-functional collaborators in the phase are - [x] Consider referencing the current step by step as a sample flow - [x] Incorporate link outs to handbook resources that support activities to achieve outcomes Potential template to leverage: https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/61793

2020-09-17 08:43:00.350

Define outcomes and activities for Validation phase 1: Validation backlog

**Problems to solve:** - [ ] Doesn’t Encourage Cross-Functional Collaboration - [ ] Too Many Steps - [ ] Too Prescriptive Detailed problems to solve for reference: https://docs.google.com/presentation/d/1BxUVcoPyjYkR7MOHn1aZGllMCqlH5eb27JKM_bb_uDA/edit#slide=id.g94724597ab_3_0 **Requirements:** (can fall into multiple MRs) - [ ] Do not remove or change workflow labels - [ ] Maintain or add clarity on what is REQUIRED per https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/9090 - [ ] Maintain or add clarity on who the cross-functional collaborators in the phase are - [ ] Consider referencing the current step by step as a sample flow - [ ] Incorporate link outs to handbook resources that support activities to achieve outcomes Potential template to leverage: https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/61793

2020-09-01 19:00:18.425

Update trademark module look & feel to be less prominent

Currently the trademark module on this page (https://about.gitlab.com/devops-tools/) is too prominent. See screenshot below:  Please update page design to de-emphasize this section, per Becky's comment on design item #10 here: https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/8468/designs/screencapture-about-gitlab-devops-tools-2020-07-27-14_04_35.png#note_405511055

2020-08-25 16:08:25.988

Review metrics triggers on pricing

Relates to https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/8842 Some of the metrics triggers we setup in LaunchDarkly aren't collecting data and need to be updated to more specific classnames/IDs. `Click start {{plan}}` cc @shanerice

2020-08-24 19:42:05.640

All-Remote Lightbox shows Yes box instead of Checkbox

This template is for filing a bug report related to the logged out marketing website https://about.gitlab.com/ and company handbook https://about.gitlab.com/handbook/ This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items. #### What is/are the relevant URL(s) `https://about.gitlab.com/company/culture/all-remote/` #### Briefly describe the bug Example: A link is broken and when hovering over it the color is the wrong color and poorly aligned. `The `yes` box towards the bottom of the form should be a checkbox. I have made the necessary changes in Marketo, but can't get this field to update. See https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/8355#note_399665866` Made changes to the Marketo form `Form 2430` https://app-ab13.marketo.com/#FO2430A1ZN13LA1 #### If possible, please specify how to reproduce the bug Go to https://about.gitlab.com/company/culture/all-remote/ and click `Download the Remote PLaybook Now` #### Please provide any relevant screenshots or screencasts  #### What is your window size, browser, operating system, and versions Please use the following website to determine your browser specifications and provide a link developers can follow: What is my browser https://www.whatsmybrowser.org `https://www.whatsmybrowser.org/b/68HGR` #### What computing device are you using? Please list the brand and model (Example: Samsung Galaxy S 10 Plus) `Insert answer here` #### Have you tried a fresh incognito window? Could this be related to cookies or account type/state? - [x] I tried a fresh incognito window & it had no impact. - [ ] The problem goes away when using an incognito window. - [ ] The problem only happens when certain cookies are set to a specific value (please specify below). #### Please list any browser plugins you have enabled Why do we ask for this? Certain website bugs may be caused by plugins. For example: Adblock, noscript, ghostery, safe browsing. `Ublock` #### What is your geographic location Why do we ask for this? Certain bugs may be geographically related. For example, if you're in the European Union, it could be related to GDPR policy and cookies. `Grover Beach, CA` #### What type of network are you connected to? **Type** - [ ] Wired - [x] Wifi - [ ] Cellular (4G, 5G, etc) - [ ] Satellite - [ ] Other `Insert details here if applicable` **Location** - [x] Home - [ ] Workplace - [ ] Travel facility (hotel, airport, conference center, etc) - [ ] Public venue (restaurant, library, cafe, etc) - [ ] VPN - [ ] Other `Insert details here if applicable` **Hardware** - [ ] I am behind a network security appliance such as a firewall - [ ] I am using a pi-hole or other hardware-based traffic blocker - [ ] Other `Insert details here if applicable` <!-- Please do not remove the items below, they are needed to automatically notify the relevant entities --> /cc @gl-website <!-- These labels will be automatically applied unless you edit or delete the following section -->

2020-08-24 17:49:38.536

Bug with mobile menu on events template

This template is for filing a bug report related to the logged out marketing website https://about.gitlab.com/ and company handbook https://about.gitlab.com/handbook/ This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items. #### What is/are the relevant URL(s) `https://about.gitlab.com/events/commit/` #### Briefly describe the bug Example: A link is broken and when hovering over it the color is the wrong color and poorly aligned. `The mobile menu on the event page feels broken since the menu doesn’t collapse upon selecting a link.` #### If possible, please specify how to reproduce the bug `On a mobile device (small display), open the hamburger menu and click on a link.` #### Please provide any relevant screenshots or screencasts How to take a screenshot: https://www.howtogeek.com/205375/how-to-take-screenshots-on-almost-any-device/  #### What is your window size, browser, operating system, and versions Please use the following website to determine your browser specifications and provide a link developers can follow: What is my browser https://www.whatsmybrowser.org `https://www.whatsmybrowser.org/b/QV0IN` #### What computing device are you using? Please list the brand and model (Example: Samsung Galaxy S 10 Plus) `Mobile phone` #### Have you tried a fresh incognito window? Could this be related to cookies or account type/state? - [x] I tried a fresh incognito window & it had no impact. - [ ] The problem goes away when using an incognito window. - [ ] The problem only happens when certain cookies are set to a specific value (please specify below). #### Please list any browser plugins you have enabled Why do we ask for this? Certain website bugs may be caused by plugins. For example: Adblock, noscript, ghostery, safe browsing. `N/A` #### What is your geographic location Why do we ask for this? Certain bugs may be geographically related. For example, if you're in the European Union, it could be related to GDPR policy and cookies. `N/A` #### What type of network are you connected to? **Type** - [ ] Wired - [ ] Wifi - [x] Cellular (4G, 5G, etc) - [ ] Satellite - [ ] Other `Insert details here if applicable` **Location** - [x] Home - [ ] Workplace - [ ] Travel facility (hotel, airport, conference center, etc) - [ ] Public venue (restaurant, library, cafe, etc) - [ ] VPN - [ ] Other `Insert details here if applicable` **Hardware** - [ ] I am behind a network security appliance such as a firewall - [ ] I am using a pi-hole or other hardware-based traffic blocker - [ ] Other `Insert details here if applicable` <!-- These labels will be automatically applied unless you edit or delete the following section -->

2020-08-24 14:38:59.800

Add info to handbook about creating new DevOps comparison templates

Per Becky's note here: https://gitlab.com/groups/gitlab-com/marketing/growth-marketing/-/epics/13#note_399701003

2020-08-21 21:47:02.068

DevSecOps survey - CI insights – 2020-10-22

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/blog/ for details on the blog process. Unless you are just suggesting a blog post idea, you will need to create the formatted merge request for your blog post in order for it to be reviewed and published. --> ### Proposal Need to go over the DevSecOps survey and find some CI or CI/CD-related content and talk about it. Then I need to recommend some other CI-content. Awareness-level ### Checklist - [ ] If you have a specific publish date in mind (please allow 3 weeks' lead time) - [ ] Include it in the issue title - [ ] Give the issue a due date of a minimum of 2 working days prior - [ ] If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior - [ ] If [time sensitive](https://about.gitlab.com/handbook/marketing/blog/#process-for-time-sensitive-posts) - [ ] Add ~"Blog: Priority" label and supplied rationale in description - [ ] Mention `@rebecca` to give her a heads up ASAP - [ ] If wide-spread customer impacting or sensitive, mention `@nwoods` to give her a heads up ASAP, apply the ~"sensitive" label, and check the [PR handbook](https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements) in case you need to open an announcement request instead of a blog post issue - [ ] If the post is about one of GitLab's Technology Partners, including integration partners, mention `@TinaS`, apply the ~"Partner Marketing" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] If the post is about one of GitLab's customers, mention `@KimLock` and `@FionaOKeeffe`, apply the ~"Customer Reference Program" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] Indicate if supporting an event or campaign - [ ] Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment)

2020-08-21 21:34:18.058

How to get started with GitLab's pipeline templates - 2020-09-23

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/blog/ for details on the blog process. Unless you are just suggesting a blog post idea, you will need to create the formatted merge request for your blog post in order for it to be reviewed and published. --> ### Proposal There has been some confusion in the past on Auto DevOps and that the term means. I think a blog discussing Auto DevOps in the context of pipeline templates would be helpful. I think a tutorial-type of blog post showing how to use these templates, how to customize them, and how to use them to get started quickly with GitLab CI would helpful for developers. ### [Link to draft](https://docs.google.com/document/d/1ccPqcd2CrSM-r5wLriRtTt7TmTndNWJ6XQJzaTFffv8/edit?usp=sharing) ### Checklist - [x] If you have a specific publish date in mind (please allow 3 weeks' lead time) - [x] Include it in the issue title - [x] Give the issue a due date of a minimum of 2 working days prior - [ ] If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior - [ ] If [time sensitive](https://about.gitlab.com/handbook/marketing/blog/#process-for-time-sensitive-posts) - [ ] Add ~"Blog: Priority" label and supplied rationale in description - [ ] Mention `@rebecca` to give her a heads up ASAP - [ ] If wide-spread customer impacting or sensitive, mention `@nwoods` to give her a heads up ASAP, apply the ~"sensitive" label, and check the [PR handbook](https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements) in case you need to open an announcement request instead of a blog post issue - [ ] If the post is about one of GitLab's Technology Partners, including integration partners, mention `@TinaS`, apply the ~"Partner Marketing" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] If the post is about one of GitLab's customers, mention `@KimLock` and `@FionaOKeeffe`, apply the ~"Customer Reference Program" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] Indicate if supporting an event or campaign - [ ] Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment)

2020-08-21 21:17:15.588

How to get the most out of your YAML configs - 2020-10-01

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/blog/ for details on the blog process. Unless you are just suggesting a blog post idea, you will need to create the formatted merge request for your blog post in order for it to be reviewed and published. --> ### Proposal This is a best practices blog post specifically designed for optimizing YAML rather than just pipelines or other CI-related terms. Other platforms discuss YAML and I think it would be helpful for us to talk about this as well. ### Checklist - [ ] If you have a specific publish date in mind (please allow 3 weeks' lead time) - [ ] Include it in the issue title - [ ] Give the issue a due date of a minimum of 2 working days prior - [ ] If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior - [ ] If [time sensitive](https://about.gitlab.com/handbook/marketing/blog/#process-for-time-sensitive-posts) - [ ] Add ~"Blog: Priority" label and supplied rationale in description - [ ] Mention `@rebecca` to give her a heads up ASAP - [ ] If wide-spread customer impacting or sensitive, mention `@nwoods` to give her a heads up ASAP, apply the ~"sensitive" label, and check the [PR handbook](https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements) in case you need to open an announcement request instead of a blog post issue - [ ] If the post is about one of GitLab's Technology Partners, including integration partners, mention `@TinaS`, apply the ~"Partner Marketing" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] If the post is about one of GitLab's customers, mention `@KimLock` and `@FionaOKeeffe`, apply the ~"Customer Reference Program" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] Indicate if supporting an event or campaign - [ ] Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment)

2020-08-21 18:00:22.844

Community contribution pipelines fail

There is a new recurring issue with community contributions to `www-gitlab-com` over the past few weeks. When they create/change an MR, the pipelines fail. When a GitLab team member clicks the “Run Pipeline” button, the pipelines pass - despite making no changes. Here is an example: - https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/59977/pipelines. Here is an another example: - https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/59503 Why is this happening and can it be resolved? CC @dmurph @johncoghlan @cwoolley-gitlab

2020-08-21 17:24:39.815

Reapply redirects in pipeline for testing manually

## Question Can we reapply redirects manually from a pipeline to a branch after redirects deploy for a newer branch? ## Scenario Occasionally there will be multiple redirect updates in different branches and we might need to test redirects in an older MR. Right now, redirects are applied to the latest MR with changes to `redirects.yml`. Can we apply redirects manually to older MRs for testing if needed? @laurenbarker you asked for me to ask this in another MR but I don't have a branch to ask so I created this issue. I'm assigning to you for now, let me know if I can help with any part of it

2020-08-21 01:48:34.513

Add a visual element on Handbook pages to differentiate it from Marketing pages

### Proposal Add a visual element on the Handbook pages to help differentiate it from Marketing pages. ### What problem is this solving? At the moment we have enabled editing with the static site editor on Handbook pages. However some marketing pages look like Handbook pages and it is confusing users why they can't use the static site editor. An example of this is with the Direction page (https://about.gitlab.com/direction/) One approach to solving this problem is moving the content to the Handbook. This approach may take a while to coordinate across teams so we are considering a smaller more immediate change on the Handbook side to help users quickly recognise that they are on the Handbook. | Handbook Page | Non-handbook Page | | ------ | ------ | |  |  | _example of two pages looking very similar, however, are in different areas of the site_ ### Suggestion We are considering changing the background image of the header area of the Handbook. This would be an extension of what we are already doing with the favicon in the browser for Handbook page  ### Extra information The current background image is constructed of a left and a right svg (226x400 px) - https://about.gitlab.com/images/home/icons-pattern-left.svg - https://about.gitlab.com/images/home/icons-pattern-right.svg ~"group::static site editor" ~"devops::create" ~"category::static site editor"

2020-08-13 22:09:35.802

Add A beginner's guide to GitOps ebook to topics page

Please select a template from the top left dropdown before continuing. This repository primarily relates to the logged out marketing website https://about.gitlab.com/ and company handbook https://about.gitlab.com/handbook/ This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items. If you do not select an appropriate template then your issue might get lost. For more information about our workflows, please reference the handbook for the marketing website https://about.gitlab.com/handbook/marketing/website/ or reference your team documentation. ### FAQ: Q: Which template should I use? A: Most people will use the "-website-bug-report" or "-handbook-update" issue templates. To request updates to existing pages or new content, please visit https://about.gitlab.com/handbook/marketing/growth-marketing/#requesting-support There are also templates for writing various kinds of blog posts including the unfiltered category. Please see the blog handbook for instructions before you open an issue: https://about.gitlab.com/handbook/marketing/blog/#publishing-process The rest of the templates are likely specific to team, role, or special occasion. Q: When will you get to this issue? A: Your issue will be refined and then prioritized relative to other issues. Marketing's website development team is currently an impacted resource. Q: How do I link to an issue template? A: https://gitlab.com/gitlab-com/www-gitlab-com/issues/new?issuable_template=name-of-template Q: How do I edit this FAQ? I have another question. A: Submit an issue https://gitlab.com/gitlab-com/www-gitlab-com/issues/new with FAQ in the title and assign it to @ brandon_lyon or another member of the website team https://about.gitlab.com/handbook/marketing/website/

2020-08-13 16:46:07.190

Commit disable scholarship apply button

After the deadline passes for the scholarship application process on /events/commit/ we need to disable the "apply now" button. The end date is set for Sunday 2020-08-16 so we'll disable it on Monday.

2020-08-12 14:26:28.836

Phase 2 Website Update - stages-devops-lifecycle/

``` BL notes to self: * The parts left for me are outlined in a comment near the bottom https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/8738#note_422873185 ``` This template if for the Marketing Growth Team for their Phase 2 Webpage updates Title this issue: Phase 2 Website Update - (Page Name) [Phase 2 Epic](https://gitlab.com/groups/gitlab-com/marketing/growth-marketing/-/epics/23) ## Metadata for page - **Intent:** - **Goal:** - **Who is code owner:** - **SME Group:** ## Adjustments to be made: These adjustments are from this audit round - [x] Add metadata - [x] Swapping content or content links - [ ] Adding pathfactory link - [ ] Adjusting SEO - [ ] Adding CTA buttons - [x] Adjusting copy on CTA buttons - [x] Adjusting old/erroneous messaging - [ ] Improve mobile optimization - [ ] Clean up alignment - [ ] Adjust color schemes - [x] Swap out old assets ## Roles and Responsibilities | Role | DRI | | ------ | ------ | | Project DRI | @rreich | | Marketing Analytics | @shanerice | | Content/Messaging | @erica| | Web Dev | @skarpeles | | Brand/Design | @luke | | GM Stakeholder | @dmor | | PMM approver (copy updates) | @williamchia | ## Production **Project DRI** - [x] Add design to design tab - [ ] Decide on audit items and check-off - [ ] Assign to relevant Team Leads for visibility - [ ] Make relevant WIP MRs - [ ] Add this issue to the page epic description - [ ] Close issue once set of MRs is complete **Team Leads** You may make comments in the design tab for tracking, but conversations on updates should be kept to the relevant MRs

2023-01-26 15:06:16.004

Document how to investigate Release Stage error budget in handbook

### Overview This issue tracks the effort to document how to investigate drops in the [error budget](https://dashboards.gitlab.net/d/stage-groups-detail-release/stage-groups-release-group-error-budget-detail?orgId=1). The aim here is ensure new joiners and other engineers can follow a clear process to investigate such issues moving forward. ### Proposal - Add a new section in the [Release Group](https://about.gitlab.com/handbook/engineering/development/ops/release) handbook page. - Under the new section, document the steps one could follow to investigate issues with the [error budget](https://dashboards.gitlab.net/d/stage-groups-detail-release/stage-groups-release-group-error-budget-detail?orgId=1).

2023-01-10 08:52:16.864

Evaluate Cube.dev as read abstraction layer for ClickHouse and PostgreSQL

## Background One of the exit criteria for [ClickHouse Working group](https://about.gitlab.com/company/team/structure/working-groups/clickhouse-datastore/#exit-criteria) states > Consider an abstraction layer to interaction with ClickHouse or alternatives With motivation behind it being the fact that ClickHouse requires significant resources to be run, and for smaller installations of GitLab it might not return investment with provided performance improvement. That in result creates a risk that ClickHouse might not be globally available for all installations and all features would need to account for the fact that there might be different data stores available. In order to avoid placing burned of detecting and handling multiple data stores on each feature implementation an abstraction layer is considered that will abstract specific data store from feature code ## Goal Build prof of concept prototype that would follow outlined later exercise scenario and provide summary that is going to rate prospect solution agains following criteria: 1. Can all requirements from exercise scenario be completed: (Yes/No) 1. Can database engine specific functions like ([percentile_disc](https://www.postgresql.org/docs/9.4/functions-aggregate.html)) being used: (Yes/No/After additional work): 1. Measure execution time for each of the exercise scenarios 1. Have you encountered any performance issues and/or excessive hardware resources consumption On scale 1 to 5 (1 - very easy, 5 - very hard): 1. How complex was to write request to realise outlined scenarios 1. How complex would be to configure add new table to each of the engines 1. How complex would be to apply changes to schema of each relations described in the exercise scenario section ## Exercise scenario Proof of concept prototype with [cube.dev](https://cube.dev/docs/getting-started/docker) must retrieve following information for each of data engines: 1. Total number of clients for each country 1. Get 75 [percentile](https://en.wikipedia.org/wiki/Percentile) for total price of orders 2. Find `order_id` of the order that have the biggest total price Data engines schema details are: ### PostgreSQL 1. Create 4 tables `Clients (id, name, country)`, `Orders(id, client_id, created_at)`, `LineItems(id, item_id, order_id, created_at)` and `Items(id, name, created_at, price)` 2. Seed tables with 100 clients records 3. Seed 100 items records 4. Seed 1000 000 orders, where 250000 orders contain 1 line item, 250000 orders contain 2 lines items, 250000 orders contain 3 lines items, and finally 250000 orders contain 4 lines items # Clickhouse 1. Create single table `LineItemAddToOrderEvent(id, client_name, client_country, order_id, item_name, item_price, created_at)` 2. Seed it with 2 500 000 rows

2023-01-10 08:51:32.587

Collect list of prospect ClickHouse and PostgreSQL abstraction layer solutions

## Background One of the exit criteria for [ClickHouse Working group](https://about.gitlab.com/company/team/structure/working-groups/clickhouse-datastore/#exit-criteria) states > Consider an abstraction layer to interaction with ClickHouse or alternatives With motivation behind it being the fact that ClickHouse requires significant resources to be run, and for smaller installations of GitLab it might not return investment with provided performance improvement. That in result creates a risk that ClickHouse might not be globally available for all installations and all features would need to account for the fact that there might be different data stores available. In order to avoid placing burned of detecting and handling multiple data stores on each feature implementation an abstraction layer is considered that will abstract specific data store from feature code ## Goal Collect list of available solutions including both open source ones like cube.dev and option to build one in house. When looking at solution it is not expected to provide in detail evaluation against criteria defined at https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/14402 but rather have them in mind as next steps, and discard solutions that from the first glance seems to not suffice requirements

2022-11-18 22:42:36.538

Stop Proposal: Stop maintaining the PPS data on the "Features by Theme" page

## Start pointing to the Post purchase survey (PPS) Dashboard We currently update the `pps_*` values in `features.yml` in order to populate the [Features by Theme page](https://about.gitlab.com/features/by-theme/). We should discontinue maintaining those values and instead direct the audience to the [PPS Dashboard](https://app.periscopedata.com/app/gitlab:safe-dashboard/1007759/PPS-Dashboard). ## What was the initial objective? https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/66574 created `features/by-theme` in order to create: > a page that represents the key features by capability and cleanups some of the listed features for those capabilities. The cleanup mostly involved removing features that seemed duplicative when listed alongside others in the same capability. https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/84577 added the PPS data to the page ... But there isn't any additional context on the intent in the MR. ## Are we achieving the objective? I'm not sure, but updating the pps values to populate that page is an inefficient, time-consuming process. Now that all of the PPS data is available in Sisense we should utilize it as the primary destination for this type of data. If grouping the results by pricing theme is valuable to team members, we could explore a way to provide that visualization in Sisense. ## Proposal 1. Remove the PPS values from the table and return the page to its initial design:  _Wayback machine_ 2. Add a link to the page pointing visitors to the PPS Dashboard if they are looking for PPS data for a given feature. 3. Optionally, delete the page entirely if "Features by Theme" is no longer used by team members in strategic decision making. ## Traffic Is there an audience for this page? The page had 711 visits in calendar year 2022. 509 if you remove that strange spike at the end of August.  The vast majority are from Google, but I'm not sure what to make of that. It's an internal-facing page, so the low traffic may not be particularly instructive.

2022-11-14 15:28:10.712

Feature Flag training for Aaron Huntsman - Q32022

# Feature Flag And Monitoring Training [Feature Flags](https://docs.gitlab.com/ee/development/feature_flags/) are used by GitLab engineers in order to roll out changes while monitoring the impact. They are **not the same** as the [**Operations > Feature Flag**](https://docs.gitlab.com/ee/operations/feature_flags.html) feature inside of GitLab. This template is intended to help understand how and when to use this tool in development. Currently as part of the feature flag process [there is an expectation](https://docs.gitlab.com/ee/development/feature_flags/controls.html#process) that GitLab engineers will monitor their changes with our monitoring tools. When the changes are low risk and do not require the [change management process](https://about.gitlab.com/handbook/engineering/infrastructure/change-management/#feature-flags-and-the-change-management-process) the expectation is that the engineer conducting the rollout will monitor their change themselves. This training is also designed to allow GitLab engineers to become aware of and comfortable with the [monitoring](https://about.gitlab.com/handbook/engineering/monitoring/) that is provided by the [Infrastructure department](https://about.gitlab.com/handbook/engineering/infrastructure/). Regardless of risk assessment, **it is expected that the engineer responsible will follow up with the change in production when the flag is flipped**. Doing so can lower the likelihood of a production issue and if a production issue does occur we can lower the time they last and impact they have. ## Steps - [x] Assign this issue to yourself with the title of Feature Flag Training - First Name Last Name - Q#YYYY - [x] [Get access](https://docs.gitlab.com/ee/development/feature_flags/controls.html#access) to control feature flags ## Feature flag ### Read - [x] [Starting with Feature Flags in Development](https://docs.gitlab.com/ee/development/feature_flags/#feature-flags-in-gitlab-development) - [x] [Controlling feature flags](https://docs.gitlab.com/ee/development/feature_flags/controls.html) - [x] [Pete Hodgson & Martin Fowler on Feature Flags](https://martinfowler.com/articles/feature-toggles.html) - [x] [Including a feature behind a feature flag in the final release](https://about.gitlab.com/handbook/product-development-flow/feature-flag-lifecycle/#including-a-feature-behind-feature-flag-in-the-final-release) ## Monitoring and Debugging ### Read - [x] [GitLab Engineering Monitoring](https://about.gitlab.com/handbook/engineering/monitoring/) - [x] [Performance at GitLab](https://docs.gitlab.com/ee/development/performance.html) - [x] [GitLab metrics currently being monitored](https://docs.gitlab.com/ee/administration/monitoring/prometheus/gitlab_metrics.html) - [x] [Adding Prometheus metrics](https://docs.gitlab.com/ee/development/prometheus_metrics.html) - [x] [Logging at GitLab](https://docs.gitlab.com/ee/development/logging.html) ### Watch ### _(Approximately 3 hours)_ - [x] [Observability at GitLab (Internal)](https://www.youtube.com/watch?v=DVNyH3zQWBo&list=PL05JrBw4t0KpQMEbnXjeQUA22SZtz7J0e) [(Slides)](https://docs.google.com/presentation/d/1F_ngvyiF1v7ibMRoWkaE65I9Z3ZxxT2LGh2RqUj90Q0) - [x] [Sentry/Kibana Training (Internal)](https://www.youtube.com/watch?v=o02t3V3vHMs&list=PL05JrBw4t0KpQMEbnXjeQUA22SZtz7J0e) - [x] [Sitespeed.io training](https://www.youtube.com/watch?v=6xo01hzW-f4&list=PL05JrBw4t0KpQMEbnXjeQUA22SZtz7J0e) - [x] [Intro to monitoring - GitLab Runners](https://www.youtube.com/watch?v=wEcoyC1cE5M&list=PL05JrBw4t0KpQMEbnXjeQUA22SZtz7J0e) - [x] [How Gitaly uses prometheus](https://www.youtube.com/watch?v=R6F674Nj3wI&list=PL05JrBw4t0KpQMEbnXjeQUA22SZtz7J0e) - [x] [Finding an issue for a specific user in Sentry (Internal)](https://www.youtube.com/watch?v=NPmv43Rnw9A&list=PL05JrBw4t0KpQMEbnXjeQUA22SZtz7J0e) - [x] [How to search for an issue in Kibana](https://www.youtube.com/watch?v=fKmwH0aNUQQ&list=PL05JrBw4t0KpQMEbnXjeQUA22SZtz7J0e) - [x] [GitLab Performance Toolkit Runthrough on 2019 08 27](https://www.youtube.com/watch?v=HobeuFtfZac&list=PL05JrBw4t0KpQMEbnXjeQUA22SZtz7J0e) - [x] [Performance bar demo](https://www.youtube.com/watch?v=WSVHXmh_Guk&list=PL05JrBw4t0KpQMEbnXjeQUA22SZtz7J0e) - [x] [How to create Kibana visualizations for checking performance](https://www.youtube.com/watch?v=5oF2rJPAZ-M&list=PL05JrBw4t0KpQMEbnXjeQUA22SZtz7J0e) **Notes**: As we increase the use of feature flags, engineers have an opportunity/expectation to use our monitoring that they did not have previously. The [DORA research program](http://services.google.com/fh/files/misc/dora_research_program.pdf) specifically calls out observability and monitoring as being one of 38 key factors driving effective continuous delivery. The more comfortable we are using the monitoring and observability tools for our systems, the better our outcomes will be in terms of mean-time-to-recovery, individual contributor awareness of infrastructure and scalability concerns, usage of infrastructure engineers' time, and teams' psychological safety.

2022-11-03 14:42:13.296

Upgrades notes are not rendered correctly

The content assembly script is not working correctly with the upgrade notes. In general: - There's no newline between the items. - Dashes are not turned into bullet lists (strangely enough, lists work correctly locally [screenshot](/uploads/e8d744b9bdebb3de5c3e5371e4d1d7f9/Screenshot_2022-11-03_at_15-34-46_GitLab_15.5_released_with_GitLab_Cloud_Seed_and_Autocomplete_suggestions.png)) If we take https://about.gitlab.com/releases/2022/10/22/gitlab-15-5-released/#upgrade for an example, this section was created from three items: - https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/data/release_posts/15_5/utilization-minimum-days-automatic-dormant-user-deactivation-setting.yml - https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/data/release_posts/15_5/systems-geo-move-container-registry-to-ssf.yml - https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/data/release_posts/15_5/systems-geo-proxying-fail-to-find-new-pipeline-refs.yml The end result though is the following. Notice there's no newline between items and lists are not rendered correctly. 

2022-10-21 18:37:06.534

Update deprecation and removal content guidelines

## Problem Right now, we're often treating deprecations like notifications of an incoming removal. But users see a deprecation as a warning that you need to take action, to prevent a breaking change in the future. It's a subtle difference, but important. When they see a deprecation announcement, they expect to be able to do something immediately. ([Original source](https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/13399#deprecations-should-be-actionable)) ## Proposed solution We should make it a requirement that all deprecations are actionable. [This list of Stripe's API changes](https://stripe.com/docs/upgrades#api-versions) shows the kind of implementation we should strive for. Key terms to take note of: `deprecated in favor of`, `removed in favor of`, `use YYY instead`, etc. It is clearly explained what people need to do for each item. Examples: * We have removed tax_percent from objects and requests in favor of tax rates. * Deprecate the payment_method.card_automatically_updated webhook in favor of payment_method.automatically_updated. * Checkout Sessions no longer include the display_items property. Use the includable line_items property instead. Then our requirement that breaking changes be announced at least 2-3 milestones before the major milestone means: * We're *not* giving users 2-3 milestones to *prepare* for the change. We're giving them time to **make** the change. * It isn't good enough to just make an announcement, we must have the deprecation *action* available at least 2-3 milestones before the breaking change as well. In fact, the deprecation process could be essentially: "Step 1, prepare the replacement, step 2, create the deprecation, Step 3..." ### What is the Action when a replacement isn't provided? The action would be "Discontinue use of this feature by X.Y." ### An example that we should try to avoid would be: * Deprecation: Feature A is being removed, to be replaced with a future feature. Action: Wait for the future feature, and switch to it when it becomes available. In this case, the deprecation should be delayed until the replacement is available. ## How to do it - [x] Update process documentation - [x] Docs https://gitlab.com/gitlab-org/gitlab/-/merge_requests/104449 - [x] Handbook https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/115169 - [x] Announce updated process and structure examples to Product and TW teams - [x] Create follow-up steps with TW and ProdOps stakeholders to review adoption https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/14318

2022-10-20 21:46:22.281

Update Recruitment Alignment

#### Updating recruiting alignment page to complete training task and add Jess Dallmar Here is the link to the current page https://about.gitlab.com/handbook/hiring/recruiting-alignment/. The update is italicized. ## Talent Acquisition Leader Alignment | Department | Leader | |--------------------------|-----------------| | Talent Acquisition | Rob Allen | _Jess Dallmar_ | Talent Brand and Enablement | Devin Rogozinski | | Talent Acquisition (Sales) | Jake Foster| | Talent Acquisition (Marketing) | Jake Foster / Steph Sarff | | Talent Acquisition (G&A) | Jake Foster | | Talent Acquisition (R&D) | Ursela Knezevic | | Candidate Experience & Enablement | Marissa Ferber | | Inbound Sourcing | Chris Cruz |

2022-10-11 17:01:24.077

Update Fulfillment handbook page to better describe Slack communications

<!-- This template is for requesting work related to the [company handbook](https://about.gitlab.com/handbook/). This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items. You may link to this issue template using the following URL: https://gitlab.com/gitlab-com/www-gitlab-com/issues/new?issuable_template=-handbook-update --> #### Briefly describe the update <!-- Example: Updating team documentation regarding project workflow. --> https://gitlab.com/gitlab-org/fulfillment-meta/-/issues/704#note_1122535474 Update the fulfillment page to better describe which slack channels to use for which use cases <!-- These labels will be automatically applied unless you edit or delete the following section -->

2022-10-03 17:42:43.184

Oracle-Cloud-Infrastructure (OCI) and GitLab DevOps Platform - 2022-10-12

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/blog/ for details on the blog process. Unless you are just suggesting a blog post idea, you will need to create the formatted merge request for your blog post in order for it to be reviewed and published. --> ## Triage (REQUIRED) Please note that there is a different process for when you want to announce something via the blog. Please see [announcement requests](https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements) in the handbook and open an announcement request issue instead of a blog post issue. Generally speaking, engineering blog posts that are tutorials/how-tos or which share how we built or debugged something, are popular with our audience. **If your proposed blog post is aligned with our [Attributes of a successful blog post guidelines](https://about.gitlab.com/handbook/marketing/blog/#attributes-of-a-successful-blog-post), you can skip straight to your [proposal](#proposal).** If you are pitching something outside of those guidelines, please fill in the below to help us prioritize. You can check out [examples of high- and low-performing blog posts to help with your rationale](https://about.gitlab.com/handbook/marketing/inbound-marketing/content/editorial-team/#top-performing-blog-posts). **This issue fulfills one of these goals:** <!--(Requestor check one)--> - [ ] Drive traffic to our website - [ ] Convert traffic into leads - [ ] Thought leadership/share expertise - [x] Build relationships with potential **partner** - [ ] Drive long-term results (please explain below in your proposal) - [ ] Announcement - `Link to announcement request issue (required, see https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements)` - [ ] Cross-functional support - `Link to OKR (required if this box is checked)` ## Proposal <!-- What do you want to blog about? --> - Talk about Why GitLab DevOps platform --- which leads into Why OCI (Oracle Cloud Platform) and GitLab. - Oracle Team (OCI Field CTO potentially) has agreed to contribute to the blog - Goal - keep it below 1200 words - We have 2 speaking sessions at Oracle CloudWorld on Oct 17-20 - 1 Workshop 90 min on how to install & run GitLab on OCI - 1 Breakout session 45min on standard GitLab DevOps message - Blog document [Google-doc-shared-with-OCI](https://docs.google.com/document/d/1oC30CUveeyh6a_udjLzUbhwvXZWbUubeq-7QRGgwYFI/edit) will be converted to MR after OCI inputs are received by **2022-10-05** ## Roles and Responsibilities | Person | Role | | ------ | ------ | | @vkelkar | requestor/author | | xyz | OCI Co-author/TBD | | @Sgittlen | editor | | @hbelz | partner-marketing review | ### Checklist - [x] If you have a specific publish date in mind (please allow 3 weeks' lead time) - [x] Include it in the issue title and apply the appropriate marketing milestone (e.g. `Mktg: 2021-03-28`) - [x] Give the issue a due date of a minimum of 2 working days prior - [ ] If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior - [ ] If [time sensitive](https://about.gitlab.com/handbook/marketing/blog/#process-for-time-sensitive-posts) - [ ] Add ~"Blog: Priority" label and supplied rationale in description - [ ] If wide-spread customer impacting or sensitive, mention `@nwoods` to give her a heads up ASAP, apply the ~"sensitive" label, and check the [PR handbook](https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements) in case you need to open an announcement request instead of a blog post issue - [x] If the post is about one of GitLab's Technology Partners, including integration partners, mention `@dpduncan`, apply the ~"Partner Marketing" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] If the post is about one of GitLab's customers, mention `@FionaOKeeffe`, apply the ~"Customer Reference Program" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [x] Indicate if supporting an event - **Oracle CloudWorld** Oct 17-20, Las Vegas, USA - [ ] Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment) ## Production - [ ] Requestor to complete issue template (Triage, Proposal, Roles and Responsibilities, Checklist ) - [ ] Issue sent through triage for consideration (pitch, planning/in progress, review, scheduled) - [ ] Issue assigned to requestor to draft blog post and open MR - [ ] MR created and linked to issue - issue is now deprecated in favor of MR and will close once MR is complete

2022-07-26 19:12:05.393

Low engagement on Release post MVP nominations

# Summary We would like to request some ideas on how to increase the number of MVP nominations we receive on a monthly basis. It's an important component of the release post that gives us a chance to live out our values of Collaboration and Inclusion, but with each milestone, we receive very few nominations and the same contributors are nominated again and again. ## Current process 1. An MVP nomination issue is generated for each release post cycle: [15.2 example](https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/13658) 1. The [issue template](https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/.gitlab/issue_templates/release-post-mvp-nominations.md) mentions `@gl-product @gitlab-org/coaches @gitlab-com/marketing/community-relations` in order to increase awareness amongst relevant teams 1. The release post manager solicits nominations on the 7th and 12th by sharing a link to the nomination issue in the following Slack channels `#release-post, #community-relations, #mr-coaching #core` 1. The release post manager makes a selection from the nominations on the 15th, or escalates the lack of a nominee in those same channels ## Contributing to this issue 1. Scan the issue to see if your idea has already been contributed 1. Start a thread with a recommendation to increase MVP nominations @gl-product @gitlab-org/coaches @gitlab-com/marketing/community-relations

2022-07-07 18:13:00.471

Apply `removal_milestone` filter to the Deprecations page via URL parameter

## Problem Creating the Breaking Changes blog post is challenging to coordinate. It is necessary because it makes it easy for customers to find all the breaking changes in one place without any noise. ## Proposed solution If the deprecations page could be filtered by removal_milestone and breaking_change in the URL (i.e. `https://docs.gitlab.com/ee/update/deprecations.html?removal_milestone=16.0&breaking_change=true`) this URL could then serve as the SSOT for breaking changes instead of a blog post. We use broadcast messages (and in 16.0, we hope to incorporate email) to direct customers to "See all the Breaking Changes coming in X.Y." - [x] [Filter by removal milestone](https://gitlab.com/gitlab-org/gitlab-docs/-/merge_requests/2906) - [ ] Filter by breaking change ## Current limitation Currently, the filtering UI on the deprecations page does not update the URL when a filter is selected. So, there isn't a way to link to a URL that will automatically apply a filter.

2022-06-23 09:05:12.734

New release post template feedback

After seeing a few notes about the new release post layout on socials I thought it would be a good idea to create an issue to collate feedback. Relates to !105999 and https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/979

2022-06-22 20:03:12.941

Adding Work Zones to Handbook Scheduling Meetings Page

<!-- This template is for requesting work related to the [company handbook](https://about.gitlab.com/handbook/). This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items. You may link to this issue template using the following URL: https://gitlab.com/gitlab-com/www-gitlab-com/issues/new?issuable_template=-handbook-update --> #### Briefly describe the update <!-- Example: Updating team documentation regarding project workflow. --> Adding a reference on Handbook page that shows overlaps in different work zones (EMEA/APAC/AMER) which will help when scheduling meetings across multiple work zones. A better definition of "friendly" times across three work zones. <!-- These labels will be automatically applied unless you edit or delete the following section -->

2022-06-16 22:18:46.285

Application metrics mvc/poc

### What The intention is to build out a minimal viable product or proof of concept for application metrics within the GitLab project. Artifacts from this effort should be: - Application metric sent to Prometheus (think code block timing) - Dashboard showing this metric build on prometheus (aggregated like averages/P95/other?) - Playbook for other teams showing how to product application metrics and dashboards The intention is to provide team members with metrics that enable them to performance tune their code. ### Why Metrics is one component of our tooling that will enable team member efficiency, reduce chances for customer visible outages, and help avoid security and other bugs. More information on this effort can be found here: https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/13521 ### When The minimal viable product or proof of concept will ideally be complete before the end of the quarter. ### Questions - How much effort is involved? - This is up to the team who agrees to take on this task. There may be libraries needed, processes, and/or methodologies developed but fundamentally this is more a proof of concept that is functioning - think a roller skate rather than a car wheel. - Others?

2022-04-25 17:48:01.528

Reduce the frequency of trainee maintainers in Reviewer Roulette

From the [2022-04-25 Maintainership working group](https://docs.google.com/document/d/1RuWhO2q7rsgSKrnSCf2xsOrp56SXBHe_z5XKDls5px8/edit#) we discussed that maintainers and trainees sometimes take their busy indicator off, and immediately get several reviews. Because trainee maintainers get 3 times the amount of a regular reviewer (so that they get more experience), this can be even more overwhelming. We should consider reducing this. ### Context Initially, [trainees were weighted higher](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/60035) at 3x as a trial but it does not look like we ever followed up. At the time, this would have meant a trainee maintainer gets picked 3/39 of the time. Today, [Roulette works by](https://gitlab.com/gitlab-org/ruby/gems/gitlab-dangerfiles/blob/master/lib/danger/plugins/roulette.rb#L147) creating a list of reviewers, traintainers, and maintainers. Since traintainers _are_ reviewers, this means they are added to the list 4x [(3x for being a traintainer and 1 more time for being a reviewer)](https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/13298#note_924545182). Does this still make sense? ### Data Here is a brief sample of preliminary data: For frontend: - 25 maintainers - 11 trainee maintainers - 21 reviewers (10 non-trainees) - Chances of a regular reviewer getting picked: 1/21 or 4% of the time - Chances of a trainee maintainer getting picked: 4/21 or 19% of the time - Chances of a maintainer getting picked: 1/25 or 4% of the time For backend: - 44 maintainers - 19 trainee maintainers - 55 reviewers (36 non-trainees) - Chances of a regular reviewer getting picked: 1/55 or 2% of the time - Chances of a trainee maintainer getting picked: 4/55 or 7% of the time - Chances of a maintainer getting picked: 1/44 or 2% of the time For database: - 9 maintainers - 5 trainee maintainers - 19 reviewers (14 non-trainees) - Chances of a regular reviewer getting picked: 1/19 or 5% of the time - Chances of a trainee maintainer getting picked: 4/19 or 21% of the time - Chances of a maintainer getting picked: 1/9 or 11% of the time ### Resources - [Roulette logic](https://gitlab.com/gitlab-org/ruby/gems/gitlab-dangerfiles/-/blob/master/lib/danger/plugins/roulette.rb) - [Roulette Dangerfile](https://gitlab.com/gitlab-org/gitlab/-/blob/master/danger/roulette/Dangerfile) ### Plan - [x] Reduce trainee maintainers weight in Roulette - see https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/13298#note_972867144 - https://gitlab.com/gitlab-org/ruby/gems/gitlab-dangerfiles/-/merge_requests/132, https://gitlab.com/gitlab-org/ruby/gems/gitlab-dangerfiles/-/merge_requests/134 and https://gitlab.com/gitlab-org/gitlab/-/merge_requests/90389 - new Roulette calculation ``` # +------------------------------+--------------------------------+ # | reviewer type | weight(times in reviewer pool) | # +------------------------------+--------------------------------+ # | reduced capacity reviewer | 1 | # | reviewer | 2 | # | hungry reviewer | 4 | # | reduced capacity traintainer | 1 | # | traintainer | 2 | # | hungry traintainer | 6 | # +------------------------------+--------------------------------+ ``` - [x] Communicate this change in EWIR(engineering week in review) and development slack channel

2022-04-01 16:09:17.857

Could we add a "Special Recognitions" content block for Group MVPs, notable contributions, etc.?

Could we add a "Special Recognitions" content block for Group MVPs, notable contributions, etc.? Following on from [a conversation in Slack](https://gitlab.slack.com/archives/C3TRESYPJ/p1646837064632809?thread_ts=1646759801.045189&cid=C3TRESYPJ): `@ogolowinski`: "I wonder if we can make a group MVP? Add a new category for community collaboration?" `@fseifoddini`: "I love the idea of special recognitions content block in the release post, if we wanna discuss in retro or do a proposal issue, regardless." `@cbacharakis`: "I don't see a reason for not having more than one MVP, especially in this case where everyone worked together towards the same goal. It also encourages people to work together as pairs/teams which increases the sense of ownership and collaboration." @ogolowinski @cbacharakis @sam.white @johncoghlan @NicoleSchwartz @fseifoddini What are the merits of adding a "Special Recognition" section to the template versus modifying the code and process to allow for multiple MVPs in a given release? For what it's worth, modifying the template to allow for multiple MVP entries in a release would be trivial.

2022-03-15 04:38:11.673

Proposal: Improve deprecation/removal documentation and process

Prod Ops release notes DRI is on board with the general direction of this proposal. Please see [this comment](https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/13399#note_1135324831) for more details. ## Proposals ### Change from separate deprecation/removal pages to "Important changes in GitLab XX" pages. The current pages are too big, and the lists will grow forever, so we should have pages for each major version and all minor versions until the next major version. So one page for GitLab 14, one for GitLab 15, and so on. Most breaking changes happen in the major milestone, so if the new pages are sorted by milestone, starting with XX.0, the breaking changes will be near the top of the page. ### Only use "deprecation"/"removal" terminology if it's truly a deprecation or a removal. The documentation should be flexible enough that a PM/EM can write the exact information that users need to know, without needing to massage the language to fit the "deprecation -> removal" concept. We could: - Just ensure it's clear that these notifications can use whatever language is needed to match the change - Document a stricter third style for non-deprecation/removal content (with examples). - Have a completely separate place for "notable changes". Example important changes that might need to be explained differently than deprecations/removals. - Feature flag status changes. - Limit additions/changes. - Changes to a feature, like where it is in the UI, the tier changing, etc. - API/GraphQL changes might warrant different language as well, or even a different page as these are very common but clutter the pages. Perhaps one page for REST deprecations/changes, one for GraphQL? - Feature that are no longer recommended, or perhaps no longer being developed, but not yet deprecated. "Feature A is no longer in development, but current users can continue using it and receiving support." `@brhea` pointed out how Ruby handles this by noting everything that isn't a deprecation or a removal under "Notable changes" for each release. For example: https://guides.rubyonrails.org/6_0_release_notes.html#active-support ### Deprecations should be actionable This is a suggestion to improve the deprecation process itself. Right now, we're often treating deprecations like notifications of an incoming removal. But users see a deprecation as a warning that you need to take action, to prevent a breaking change in the future. It's a subtle difference, but important. When they see a deprecation announcement, they expect to be able to do something immediately. We should make it a requirement that all deprecations are fully actionable. Some examples: - Deprecation: `types` keyword being removed from CI/CD configuration. Action: Start using the `stages` keyword, which already exists. - Deprecation: Certificate-based Kubernetes integration being removed from GitLab. Action: Start using the Agent for Kubernetes (already exists). - Deprecation: Pseudonymizer feature is being removed from GitLab, with no replacement. Action: Stop using Pseudonymizer. Then our requirement that breaking changes be announced at least 2-3 milestones before the major milestone means: - We're _not_ giving users 2-3 milestones to _prepare_ for the change. We're giving them time to **make** the change. - It isn't good enough to just make an annoucement, we must have the deprecation _action_ available at least 2-3 milestones before the breaking change as well. In fact, the deprecation process could be essentially: "Step 1, prepare the replacement, step 2, create the deprecation, Step 3..." An example that we should try to avoid would be: - Deprecation: Feature A is being removed, to be replaced with a future feature. Action: Wait for the future feature, and switch to it when it becomes available. In this case, the deprecation should be delayed until the replacement is available. ### Non-deprecation breaking changes We also need to think about the language for non-deprecation breaking changes, as well as the action users should take. For example: - A feature being moved to Ultimate-only shouldn't be considered a deprecation, but is a breaking change that should be announced early. The action would be to upgrade to Ultimate, or stop using the feature. We can document examples of several kinds of announcement styles. - A new limit being added, especially to .com, isn't a deprecation, but would require action. Like "The maximum numbers of jobs in a pipeline will be set to 1234". The action would then be to bring the project within the limit range before it is added. ## Previous issue content <details> <summary>Click me to expand/collapse.</summary> As we've come closer and closer to 15.0, we've increasingly seen problems with the deprecation/removal notification process. Currently, the process is to "deprecate" and notify users at least 2 releases before we then "remove" and notify users of the removal. Deprecations and removals can be considered Breaking Changes, or not. But this somewhat simple process is not flexible enough for the variety of important changes that we implement each month, and repeated complaints seem to highlight this. - Quotes from the thread in https://gitlab.com/gitlab-org/gitlab/-/merge_requests/84339#note_901244690: - `That is not what deprecation notices are for. They mean "Check for a replacement NOW, so you don't have issues later."` - `It's a different story for "we are just dropping this without replacement, stop using it" deprecations.` - `The "deprecated" makes it sound like you should not use it anymore, which is why people are concerned about a lack of replacement.` - From: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/82646#note_874257859 - `it seems like we're experiencing some scope creep as to what qualifies as a deprecation/removal. I've also been asked by other PMs to add things to the deprecation/removal doc that aren't deprecations or removals. To my knowledge, the deprecations/removals doc isn't for breaking changes that aren't caused by feature deprecations/removals.` - From: https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/13230#note_923349881 - (Paraphrasing) A breaking change notice was late because it was neither a deprecation nor a removal, and it was not intuitive that it should be added to either page. - etc... ## Expanding on the issues ### Breaking changes Breaking changes can come from all types of changes, including: - Removals - Limits (New/changed) - Feature flag default state changes. - Feature defaults changing from to on/off (or off/on). - Feature changing tiers. - Any other change in behavior that forces a user to take action before they can continue to work as normal. It's notable that the only page that exists for these breaking changes is the removals page. I'm not considering the deprecations page for this, because a deprecation itself is not actually a breaking change (though it may warn of a future breaking change). ### Deprecations: People generally expect deprecation warnings to mean: "Stop doing X" (often combined with a "Start doing Y instead"). But our deprecation announcements are rarely that clear or simple, and the variability is huge: - Sometimes immediately actionable: - "The `types` keyword is deprecated, start using the `stages` keyword". - "The X integration has been discontinued and will not be replaced." (The action is to just stop using the feature) outright. - Sometimes not immediately actionable: - "The X feature is deprecated, it will be replaced in milestone Y.yy." - "This feature's behavior will change in future milestone Y.yy" We also have trouble with many deprecation notices not really being deprecations, but being written as such to make it fit on the page, because there is no other place for these announcements. For example (paraphrased): - Using this feature in the Premium tier is deprecated and will be removed in 15.0. It is not deprecated for use in Ultimate. - Using more than X jobs in a pipeline is deprecated and will be removed in 15.0. ### Removals Similar to the issues raised in the breaking changes section above, the removals page will have a huge variety of types of removals in 15.0 (if we use the earlier deprecation notices as a prediction). But many of these will not be things we'd consider deprecations, but are listed there because they are breaking changes that we want people to be aware of. ### Product documentation Outside of the deprecation/removals pages, we have a lot of feature docs that may or may not also have details about the upcoming changes, and I'm not sure we've got a solid standard for what to do with the feature docs. - Should deprecation/removal warnings be in the feature docs too? - Should removed features continue to be documented to support self-managed users on older versions that are still supported by GitLab support? ## Brainstorming I believe we should make significant changes to our processes for deprecations/removals/breaking changes, and have some ideas. ### Idea 1 - Limit use of `Deprecation` terminology We should only use the term `Deprecation` when we mean: "Stop doing A, start doing B." In many cases, it seems like "End of development" announcements might make more sense. For a real example: https://docs.gitlab.com/ee/ci/yaml/#only--except. This is even more useful when there is no replacement yet available. ### Idea 2 - New page for important announcements Instead of a deprecation page and a removal page, we could have one "Notable changes" (title TBD) page where we list everything we think people should really know about. It can be important changes to feature in the current milestone, or planned changes to features in future milestones. Breaking changes of **any** kind can then be added to the page. New limits, feature changes, removals, etc. If it's important for people to know, we can put it there. We have badges in the docs (see the red ultimate here: https://docs.gitlab.com/ee/administration/monitoring/gitlab_self_monitoring_project/#take-action-on-prometheus-alerts), with on-hover text, and a link. We could add a new `Breaking Change` badge to add to all sections on this doc that are considered breaking changes. On-hover text will give a little bit more detail, and clicking it will bring you to a page that gives more details about breaking changes in general. Like major ".0" milestones for most breaking changes, minor milestones for important security fixes, etc. Sorting up for discussion, but perhaps some kind of "Milestone when you can/need to do something about it". For example, a deprecation could be announced in any milestone, but perhaps should be listed under the milestone when the replacement is expected to be available. A removal warning for an integration being dropped in 15.0 with no replacement should be a breaking change warning listed under 15.0. ### Idea 3 - Have boilerplate language for product docs Similar to our documentation for feature flagged features: https://docs.gitlab.com/ee/development/documentation/feature_flags.html#use-a-note-to-describe-the-state-of-the-feature-flag We should have a warning box style for important notices about the feature (or we can just reuse `FLAG:`), along with a collection of standard language that can be copied and pasted into the box and added to the feature docs themselves. I expect the language to be simple and clear, and easily pasted as needed. You may need to mix and match. Some potential examples: - This feature has reached end of development and will no longer receive updates, but can still be used. - This feature is deprecated. You should now use Y instead. - This feature will be removed in X.xx. You will need to use Y. - This limit will be increased/decreased in X.xx. To prepare, you should Y. - This feature's feature flag will be enabled by default in XX.x. To prepare, self managed users can X. SaaS users can Y. - etc... (these are all just quick ideas, the language is not polished yet) ## Extras - Should we be thinking about severity of the changes? - We should research what other companies are doing for these kinds of announcements. - I imagine self managed users would love it if all breaking changes were added 2 releases ahead of a major milestone, but behind a disabled feature flag. They'd have two full releases to enable the flag whenever they want, and they'd be fully ready when the major milestone comes around that sets the flag to enabled by default (because it'll already be enabled on their instance). Wouldn't work for SaaS... - How to handle security breaking change announcements? # OLD Previous Issue discussion In https://gitlab.com/gitlab-org/gitlab/-/merge_requests/82646#note_874257859, @ngaskill points out: > It seems like we're experiencing some scope creep as to what qualifies as a deprecation/removal. I've also been asked by other PMs to add things to the deprecation/removal doc that aren't deprecations or removals. To my knowledge, the deprecations/removals doc isn't for breaking changes that aren't caused by feature deprecations/removals. Something for the TW team to discuss. Is _everything_ we are adding to the "deprecations" and "removals" pages truly a deprecation or removal? Some examples of breaking changes that are not deprecations: - A project setting changing from default disabled to default enabled. Happens from time to time, and could easily be a breaking change, but not a deprecation. - Instance limit updates. Happens quite frequently actually, usually to improve performance or reduce potential abuse of a limit that was too high. You try to rewrite it to make it more like a deprecation by focusing on the ability that is being removed: "The ability to create job names with more than 256 characters is being deprecated". I don't think most people consider that a deprecation though, and it might be more easily understood as simply a new limit: "We are introducing a limit on the length of job names" (not a deprecation). So how do we handle notifying users about: - Non-breaking change deprecations. - Breaking change deprecations. - Breaking changes to features that are not being deprecated, ex: https://docs.gitlab.com/ee/update/deprecations.html#changes-to-the-ci_job_jwt - New instance limits, ex: https://docs.gitlab.com/ee/update/deprecations.html#cicd-job-name-length-limit - Tightening of security, like stricter permissions, ex: https://docs.gitlab.com/ee/update/deprecations.html#graphql-permissions-change-for-package-settings Right now, they are all being put in the same deprecations and removals pages due to being similar, but they are not exactly the same. ### Proposals Perhaps we should: - Rename the pages? Some initial brainstorming ideas: - `Deprecations and planned changes` / `Removals and changes` - `Deprecations and announcements` / `Removals and important changes` - `Deprecations and planned breaking changes` / `Removals and breaking changes` - `Planned changes` / `Important changes by GitLab release version` - `Planned breaking changes` / `Breaking changes by GitLab release` - Change what's on the page? A lot of the suggestions above relate to changing the focus on the pages from deprecations to essentially "Any important change we really want users to be aware of". So perhaps, along with a rename, we should change what kind of content is on these pages. Looking at deprecations, for example, these are some of the options: - List all deprecations only, both breaking and non-breaking. <- Current - List all deprecations, and also non-deprecation changes that are breaking. - List only breaking changes. That includes deprecations, but does NOT include deprecations that are not breaking changes. This is an interesting idea, because I suspect what people really need/want to know are the _breaking changes_, no matter the type. Deprecations that are not breaking, like the removal of support of some integration that already didn't work because the related product itself is gone, doesn't need to be documented here, does it? It could be handled in the regular feature docs? </details>

2022-02-10 00:03:05.879

Release Post Item generator is creating MRs for deprecations and removals in the wrong repo

### Description For context: https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/84700#note_837950452 Since deprecations and removals used to be release blog post items, the generator creates MRs in `www-gitlab-com` if an Issue matches any `release post item::` label. Which includes ~"release post item::deprecation" and ~"release post item::removal" ### Challenge These MRs are now noisy because we've updated the deprecations and removals process. Deprecation and removal MRs are now created in the `gitlab` project and compiled directly into GitLab Docs. ### Proposal - [ ] Tweak the generator so that it only creates MRs for ~"release post item" Issues and Epics that are not ~"release post item::deprecation" or ~"release post item::removal" ### Nice to have - [ ] Create the MR in the `gitlab` project following [the updated process](https://about.gitlab.com/handbook/marketing/blog/release-posts/#deprecations)

2022-01-28 18:46:05.333

Perform release post content assembly with a bot

### Summary [Content assembly: merging release post items (content blocks) to your branch](https://about.gitlab.com/handbook/marketing/blog/release-posts/#content-assembly-merging-release-post-items-content-blocks-to-your-branch) could be run on a regular basis by a Bot. The RPM's responsibility would be to check the branch for issues rather than running the assembly themselves. ### Proposal **Option A: Simple** Create a job that runs the once nightly, where `X-Y` is the active milestone. ``` git checkout master git pull git checkout release-X-Y git pull git merge master bin/release-post-assemble git push git push origin release-X-Y ``` **Option B: [Specific](https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/12865#note_820269872)** > I think that a commit should queue a pipeline that checks if the branch name matches the release post naming convention (e.g. release-x-y). If the branch matches that naming convention run the content assembly script for every commit. If the pipeline fails, email the committer that their commit needs to be fixed (or better yet, slack them). Related: https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/12865#note_815576374

2022-01-10 17:43:00.765

Document prioritization sessions in handbook

<!-- This template is for requesting work related to the [company handbook](https://about.gitlab.com/handbook/). This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items. You may link to this issue template using the following URL: https://gitlab.com/gitlab-com/www-gitlab-com/issues/new?issuable_template=-handbook-update --> #### Briefly describe the update Document prioritization sessions in handbook, a planning tool in times of uncertainty and lack of direction. Link from/to: - https://about.gitlab.com/handbook/product-development-flow/ - https://about.gitlab.com/handbook/product/product-processes/#using-the-rice-framework <!-- These labels will be automatically applied unless you edit or delete the following section -->

2021-12-22 15:29:11.291

Slack integrations for release post announcements and notifications

## Proposal - if the release post MR pipeline fails, notify on Slack - if the release post MR is merged, notify on Slack

2021-12-22 12:51:55.763

Blog Post: Parent-child pipelines VS multi-project pipelines (title TBD)

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/blog/ for details on the blog process. Unless you are just suggesting a blog post idea, you will need to create the formatted merge request for your blog post in order for it to be reviewed and published. --> ## Triage (REQUIRED) Please note that there is a different process for when you want to announce something via the blog. Please see [announcement requests](https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements) in the handbook and open an announcement request issue instead of a blog post issue. Generally speaking, engineering blog posts that are tutorials/how-tos or which share how we built or debugged something, are popular with our audience. **If your proposed blog post is aligned with our [Attributes of a successful blog post guidelines](https://about.gitlab.com/handbook/marketing/blog/#attributes-of-a-successful-blog-post), you can skip straight to your [proposal](#proposal).** If you are pitching something outside of those guidelines, please fill in the below to help us prioritize. You can check out [examples of high- and low-performing blog posts to help with your rationale](https://about.gitlab.com/handbook/marketing/inbound-marketing/content/editorial-team/#top-performing-blog-posts). **This issue fulfills one of these goals:** <!--(Requestor check one)--> - [x] Drive traffic to our website - [ ] Convert traffic into leads - [x] Thought leadership/share expertise - [ ] Build relationships with potential customers - [x] Drive long-term results (please explain below in your proposal) - [ ] Announcement - `Link to announcement request issue (required, see https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements)` - [ ] Cross-functional support - `Link to OKR (required if this box is checked)` ## Proposal <!-- What do you want to blog about? Add your description here. If you are making an announcement, please open an `announcement` request issue in the Corporate Marketing project instead: https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements --> Write how [parent-child pipelines](https://docs.gitlab.com/ee/ci/pipelines/parent_child_pipelines.html) and [multi-project pipelines](https://docs.gitlab.com/ee/ci/pipelines/multi_project_pipelines.html) features can help tacking growing complexity of CI/CD pipelines. Describe the advantages of using [one feature over the other one](https://gitlab.com/gitlab-org/gitlab/-/issues/273399) and highlight [key differences](https://gitlab.com/gitlab-org/gitlab/-/issues/336884) to help customers choose the right approach for their needs. ## Roles and Responsibilities | Person | Role | | ------ | ------ | | @fabiopitino | requestor | | `@person`| editor | | `@person` | approver (optional) | ### Checklist - [ ] If you have a specific publish date in mind (please allow 3 weeks' lead time) - [ ] Include it in the issue title and apply the appropriate marketing milestone (e.g. `Mktg: 2021-03-28`) - [ ] Give the issue a due date of a minimum of 2 working days prior - [ ] If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior - [ ] If [time sensitive](https://about.gitlab.com/handbook/marketing/blog/#process-for-time-sensitive-posts) - [ ] Add ~"Blog: Priority" label and supplied rationale in description - [ ] If wide-spread customer impacting or sensitive, mention `@nwoods` to give her a heads up ASAP, apply the ~"sensitive" label, and check the [PR handbook](https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements) in case you need to open an announcement request instead of a blog post issue - [ ] If the post is about one of GitLab's Technology Partners, including integration partners, mention `@dpduncan`, apply the ~"Partner Marketing" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] If the post is about one of GitLab's customers, mention `@FionaOKeeffe`, apply the ~"Customer Reference Program" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts) - [ ] Indicate if supporting an event or campaign - [ ] Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment) ## Production - [x] Requestor to complete issue template (Triage, Proposal, Roles and Responsibilities, Checklist ) - [ ] Issue sent through triage for consideration (pitch, planning/in progress, review, scheduled) - [ ] Issue assigned to requestor to draft blog post and open MR - [ ] MR created and linked to issue - issue is now deprecated in favor of MR and will close once MR is complete

2021-12-02 15:31:01.956

Link from UX handbook to guidelines on discussing competitors in public

The following discussion from !94038 should be addressed: - [ ] @pedroms started a [discussion](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/94038#note_740219469): (+4 comments) > these kinds of discussions are not specific to Product Designers or other members of the UX department. I frequently witness Product Managers engaging in similar discussions and sharing competitor features. I wonder if there's a more generic location for this? Maybe as a sub-page of our SAFE guidelines? ## Proposal > I'm thinking the [UX Department “How we work” page](https://about.gitlab.com/handbook/engineering/ux/how-we-work/) might be a good place to link to these new guidelines.

2021-09-21 19:39:58.111

Fix Timeout Issue Estimated cost of Abuse KPI

https://app.periscopedata.com/app/gitlab/780726/WIP:-Blocked-User-Usage-Data?widget=12404680&udv=0 sometimes times out because the query takes too long, need to optimize it. Look at using monthly table instead of `legacy.gitlab_dotcom_project_statistic_snapshots_daily` to reduce time

2021-09-21 17:01:22.306

create corrective action charts

From slack > @dawsmith thanks @meks - adding @amoter who was looking to do some more estimates on arrival/close rates > Right now we have https://app.periscopedata.com/app/gitlab/787921/Corrective-Actions showing the cumulative overdue corrective actions over time. I think we were looking to add a daily or weekly arrival/close graph of corrective actions Add charts for: - [x] how many new infrastructure CAs were created in a week - https://app.periscopedata.com/app/gitlab/787921/Corrective-Actions---Infrastructure?widget=12802448&udv=0 - [x] how many infrastructure CAs were closed in a week - https://app.periscopedata.com/app/gitlab/787921/Corrective-Actions---Infrastructure?widget=12802466&udv=0 - [x] if possible, broken down by sev/priority levels - [x] of the closed, how many have the label "workflow-infra::cancelled" and how many have the label "workflow-infra::done" - https://app.periscopedata.com/app/gitlab/787921/Corrective-Actions---Infrastructure?widget=12845002&udv=0 ## UPDATE Corrective actions dashboard & KPI logic changed to only include corrective actions under [Infrastructure project](https://gitlab.com/gitlab-com/gl-infra/infrastructure)

2021-09-07 19:18:19.636

Add/hide blog tags

I'd like to add a tag to the blog tags/categories: DevOps Platform Here are associated posts you can use to queue this up: https://about.gitlab.com/blog/2021/09/03/the-code-review-struggle-is-real-heres-what-you-need-to-know/ https://about.gitlab.com/blog/2021/09/02/the-journey-to-a-devops-platform/ https://about.gitlab.com/blog/2021/08/03/welcome-to-the-devops-platform-era/ https://about.gitlab.com/blog/2021/06/22/gitlab-14-modern-devops/ https://about.gitlab.com/blog/2021/05/19/agile-planning-with-a-devops-platform/ And I'd like to make Unfiltered invisible, if that's possible. Thanks much!

2021-08-12 20:16:58.543

Stacked MR Chart based on group

I'd like to see a stacked chart based on group for MRs. Ideally I'd either have filter capability for the type of MR (feature, bug, etc.) OR I can also just have it for feature MRs. It may end up being a performance indicator, but right now I need it to assess how our product investment is going and which teams are still doing feature work.

2021-08-05 18:20:13.415

Ensure accuracy of group->stage-> section label

Currently snippets pull - group -> group (group label) - Snippet: https://app.periscopedata.com/app/gitlab/snippet/select_group_name_from_label/5563886fad9b48bb857880de1e7cd019/edit - stage -> stage (devops label) - Snippet: https://app.periscopedata.com/app/gitlab/snippet/select_stage_from_label/554ade7075c54af092bb6075603302d2/edit - stage -> section (section label) - Snippet: https://app.periscopedata.com/app/gitlab/snippet/development_section_by_stage_label/55b957e9630748308ed9c61b09707b86/edit Long term we should create a sheetload or mapping table that has group -> stage-> section cc @kwiebers @lmai1 @meks

2021-07-30 16:02:39.380

add issue_links dbt model

To support analysis that links infradev issues to incidents need to create usable dbt dim model for issue_links table added to MR: https://gitlab.com/gitlab-data/analytics/-/merge_requests/5251

2021-07-29 15:52:15.078

Create Dimensional Model to support MR metrics

Create fact/dim/mart tables to support current & future MR metrics to make queries faster & add more of the logic in dbt modeling layer Final table should include fields needed for MR based Metrics: - [ ] is_part_of_product (uses ops & .com data) - [ ] daily history of MRs with state at each day (merged vs open) - [ ]

2021-07-29 15:45:59.740

Create Dimensional Model Tables to support Issue Metrics and improve rendering performance

Create Dimensional Models to support end fact/mart table that will support all the issue metrics we use, especially "Open Age" Metrics & Label based metrics See https://gitlab.com/gitlab-data/analytics/-/merge_requests/5251 for example of how to do this Final Table should include - [x] historical dates by day of issues & state at that time (open v closed) - [ ] common labels with correct valid dates (ex. sev 2 from Jan 1 2020 -> Jan 3, then Sev 3 afterwards - see corrective actions snippet for guidance - [x] Severity Labels - [ ] Priority Labels - [ ] section/stage/group labels - [ ] Incident labels (is_incident) - [x] full label array included - [x] issue age - [x] issue age since severity label was added - [x] full linkable issue URL - [x] array of assigned users

2021-07-28 17:26:28.232

Review Corrective Actions Logic

When working on Infradev Issue logic, found might need to adjust corrective action logic to stop tracking issue age once they have been closed (remove historicals from current averages)

2021-07-27 17:49:08.162

Follow-up from "add ytTracker.digestPotentialVideos() to video modal"

The following discussion from !86913 should be addressed: - [ ] @laurenbarker started a [discussion](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/86913#note_635786114): (+5 comments) > @@dennis106 ping me when we're ready to deploy this MR. Thanks!

2021-07-27 16:44:21.658

Visibility of InfraDev issues and work stream type allocations

Based on the recent discussions in Engineering Allocations, the goal is to track `infradev` issues on age per product groups. From @sloyd >>> We need to clear up the delineation of Corrective Actions vs infradev escalations as they aren’t the same, yet there is also overlap. >>> @andrewn also has done weekly reports in this in https://gitlab.com/gitlab-org/infradev-reports/-/issues/5#summary-by-severity ### To-DO - [x] Create Central Eng Metrics for S1 Open Age, S2 Open Age & Table - https://app.periscopedata.com/app/gitlab/798401/Infrastructure-Embedded-Dashboard - [x] Create Infradev Summary Dashboard with Filters - https://app.periscopedata.com/app/gitlab/899982/InfraDev - [x] add metric for # of related incidents of infradev issues to match what gets shown in Andrew's infradev report - tracking in https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/12226 ### Requirements * Create a new filterable equivalent dashboard similar to [corrective actions](https://app.periscopedata.com/app/gitlab/787921/Corrective-Actions) but only honed in for infradev * Key charts: * Past due infradev * Average age of open infradev * Ability to view as a holistic view that can drill down to each product groups * We need to be able to see how each product teams are doing and if they are able to keep up. * Lean on our philosophy of measuring open things ### Examples of the key charts  ## Plan * We are aligned on the metric `Open InfraDev Age`. This aligns with other Eng PIs (OMA, OBA, Open UX Debt Age) Reasons: * As a long-term indicator, provide a measure that captures the total effort. Average Age of Open achieves this, we give credit to efforts when any open issue is fixed * Give agency to each team to prioritize what is most severe, a recent infradev S2 may need action now than an older infradev S2 (example from this https://gitlab.com/gitlab-org/gitlab/-/issues/333184) * Facilitate a 2 way direction of recognizing completed efforts and feedback loop. e.g. * A product group team is doing well if `Open InfraDev Age` is going down. * A product group team needs help if `Open InfraDev Age` is going up. * Slice this by severity * This negates the complication of restarting SLOs when severity shifts, we set teams to focus on burning down infradev in each severity as one bucket. The first being S1 and S2 which is the agreed on path from the last meeting. * @davis_townsend to create: * Open InfraDev Age S1 chart (add total number of issues in the backdrop) * Open InfraDev Age S2 chart (add total number of issues in the backdrop) * @lmai1 to add a table at the end showing list of Open infradev issues (S1/S2) * @lmai1 will ensure the handbook dashboard structure is accurate https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/12154 * This dashboard https://app.periscopedata.com/app/gitlab/798401/Infrastructure-Embedded-Dashboard is filterable down to every stage and group and is in our handbook dashboards https://about.gitlab.com/handbook/engineering/metrics/dev/create/#infrastructure-indicators * This will provide visibility into each teams and if we need to dial up more * Separately we already have types of MRs merged per stage/group in the Development Indicators section of the same pages * This will tell us what type of work needs to increase/decrease *  * We aim to have this in by next Engineering Allocation meeting.  ### Dashboards Main entry point https://about.gitlab.com/handbook/engineering/metrics cc @lmai1 for your visibility as this may also come up for development analytics

2021-07-26 14:42:48.338

Refresh query for Incident Root Cause

I suspect that we're not querying the right data, probably due to the recent change to Incident Issue type? https://app.periscopedata.com/app/gitlab/793517/Infrastructure-Incident-Data?widget=10637568&udv=1311208 What I note is that the July number of incidents is way down (inconsistent with our real incident count), and doesn't show any root cause info

2021-07-20 19:07:41.000

Investigate Long Loading Time of PI Pages

Stakeholders have brought up the long loading times of the PI Pages as an issue. Examples: * https://about.gitlab.com/handbook/engineering/infrastructure/performance-indicators/ * https://about.gitlab.com/handbook/engineering/development/performance-indicators/ We should investigate if this mainly a problem with the query times of the PIs or with rendering time of the charts If the issue is rendering time, will probably need help from others to improve that, but if the issue the queries we can improve that load time by optimizing the longest running queries, & eliminating excess PI charts ## Ideas ### Backend performance * @davis is currently looking into query performance * Davis: Looked at query times of the underlying performance. Have processing be done at Snowflake. ### Frontend performance * Render only KPIs Don’t render charts for (Regular) RPIs, requiring a click thru to Sisense instead * Lazy load RPIs on scroll * Only render RPIs in a popup/modal if someone mouses-over an icon * Other? cc @edjdev