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)

Story points: 5.0