Blog Post: GitLab CI/CD success story from customer: Orange (July 28)
Triage (REQUIRED)
The Inbound Marketing team prioritizes requests that drive results and meet our goals of generating organic traffic and inquiries.
Please note that there is a different process for when you want to announce something via the blog. Please see announcement requests 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, you can skip straight to your 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.
This issue fulfills one of these goals:
-
Drive traffic to our website -
Convert traffic into leads -
Thought leadership/share expertise -
Build relationships with potential customers -
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
This proposal is from a GitLab community member who is excited about GitLab and helped launch several initiatives that gained a lot of traction in his company. He'd like to write something for the GitLab blog about CI/CD. Here's his email to us:
I'm Pierre Smeyers, Developer Advocate at Orange and GitLab enthusiast. During the last two years I've developed generic GitLab CI templates for a vast range of technologies used within Orange (languages, DevSecOps tools, hosting & deployment technologies, acceptance testing tools ...).
It quickly became a very successful innersource project, with about 1000 members (mainly users, a handful of contributors), and last week I opensourced it under the name "to be continuous". I'll let you discover this, but in a word I would introduce those templates as an "opinionated CI/CD framework".
Home Page: https://orange-opensource.gitlab.io/tbc/doc/ Reference doc: https://orange-opensource.gitlab.io/tbc/doc/intro Kicker (an interactive wizard): https://orange-opensource.gitlab.io/tbc/kicker/ (you'll see all available templates there)
I'm currently writing an article to tell about this project (and tell a bit about its history), and I'm wondering if I could propose it to the GitLab blog.
Articles already published:
- https://pismy.medium.com/to-be-continuous-869ad895d51b
- https://dev.to/pismy/to-be-continuous-opinionated-gitlab-ci-1fi2
Roles and Responsibilities
Person | Role |
---|---|
@person |
requestor |
@person |
editor |
@person |
approver (optional) |
Unsure -- will need to the community member on this issue.
Contact Info in confidential issue: https://gitlab.com/gitlab-com/marketing/strategic-marketing/product-marketing/-/issues/5267
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 -
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 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 -
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 -
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
-
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