Welcome to the Developer Evangelism team workflow page. Learn how the team works and how to work with the team. We primarily use the Developer Evangelism Meta issue tracker. We own the team label dev-evangelism and all of our other labels which are located at the gitlab-com group level. You can add the labels as necessary to any issue under this group for our team to track.
Opening an issue is the best way to get a conversation started. The dev-evangelism label is at the gitlab-com group level, which means it can be added to any issue or merge request in the group's structure.
The dev-evangelism label is required, other labels are optional. The DE-Bot or a team member will do the triage and add the necessary labels. To reduce noise in the comments, please add the DE-Type::Consulting and the relevant Consulting team labels yourself.
You can use the request an evangelist issue template to submit a request. It provides a guide to collect the required information to triage the request.
The Developer Evangelism uses the Roadmap in the Developer Relations Group to track our work. Epics for our team are tracked within this group using the dev-evangelism label.
Work items that fit into our team strategy, including events and content plans, are tracked using Epics and Child Epics. There are currently 2 parent epics that capture all the activities of the team, the Events & Content epics. There is also a Release Evangelism epic under the Content epic which contains child epics for all of our monthly releases. For each activity of the team, a sub-epic should be created under the relevant parent epic and with relevant labels added.
For each fiscal year's plan, we use the following structure to organize epics on our roadmap:
For blog posts and other content, start and due dates should correspond with the expected week of publishing. Do not set start date to the time you'll begin working on a piece of content as this can affect the roadmap view.
These are the recommended labels for Epics created in the Developer Relations group. They are used for filtering the epics.
| Label | Description |
|---|---|
DevRel-Events |
Should be applied to all events related epics |
DevRel-Content |
Should be applied to all Content related epics |
Region-AMER |
Applied to events happening in North America |
Region-APAC |
Applied to events happening in APAC |
Region-EMEA |
Applied to events in EMEA |
Region-LATAM |
Applied to events in Latin America |
Content-Blog |
GitLab Blog posts |
Content-Newsletter |
Newsletters |
Content-Partner Blog |
Blogs posts on partner websites |
Content-Social |
Social media campaigns or threads |
Content-Video |
Video Content or Streaming |
Content-Webinar |
Online Webinars |
Content-Releases |
GitLab Release campaigns |
CFP |
Any event epic (and ancestor epics) that have a CFP issue |
Important! Where you are adding a label to a sub-epic, its ancestors must include the label for filtering to work properly. This is a workaround, because the roadmap only filters top-level epics using labels, but works when an epic and its ancestors have the label you are filtering with. For example, in the image below, you will notice that the FY24 Content & the sub epic "Blog post - March 2023", both have the label Content-Blog, they both appear when the label is used as a filter. The child epic will not appear in the filter, when its ancestors don't have the label you are searching with.
Please use this template when creating Epics for activities that should appear for the Developer Evangelism team on the roadmap:
> Epic Title Guide:
> Dates should be using ISO dates, see https://about.gitlab.com/handbook/communication/#writing-style-guidelines
> Format:
> Content: Title - Author - Publish Month, Publish Year
## Activity Summary
**Please consider addressing these key questions in your summary:**
1. Who is our audience?
- A:
2. What is the best content type (blog post, video, how-to) to deliver this message?
- A:
3. How does this content help our audience?
- A:
4. How does this content help us achieve our goals?
- A:
## Team or Individual DRIs
**Please add team label to epic.**
## Relevant Issues, Epics or resources
-
<!-- these labels should be included on all templates -->
/label ~"dev-evangelism"
<!-- Example:
/label ~"DevRel-Content" ~"FY24-Q3"
Note: These are samples for guidance, please add relevant labels for activity region, type, quarter or any other labels relevant to your team/program. Please include additional relevant labels here. -->
<!--Link to parent epic where necessary. Please choose the quarterly epic from the FY24 main epic
https://gitlab.com/groups/gitlab-com/marketing/developer-relations/-/epics/98 -->
/parent_epic https://gitlab.com/groups/gitlab-com/marketing/developer-relations/-/epics/240
<!-- Link to Child epic where necessary -->
/child_epic
/cc @gitlab-de
<!-- Mention team members that should be aware of the epic -->
/cc
> Epic Title Guide:
> Dates should be using ISO dates, see https://about.gitlab.com/handbook/communication/#writing-style-guidelines
> Format:
> Content: Title - Author - Publish Month, Publish Year
> Event: Event Name, Location, ISO Date
## Activity Summary
**Please consider addressing these key questions in your summary:**
1. Who is our audience?
- A:
2. What is the best content type (blog post, video, how-to) to deliver this message?
- A:
3. How does this content help our audience?
- A:
4. How does this content help us achieve our goals?
- A:
## Team or Individual DRIs
**Please add team label to epic.**
## Relevant Issues, Epics or resources
-
<!-- these labels should be included on all templates -->
/label ~"dev-evangelism"
<!-- Example:
/label ~"DevRel-Events" ~"Region-AMER" ~"FY24-Q3"
Note: These are samples for guidance, please add relevant labels for activity region, type, quarter or any other labels relevant to your team/program. Please include additional relevant labels here. -->
<!--Link to parent epic where necessary -->
<!-- Events epic (default) -->
/parent_epic https://gitlab.com/groups/gitlab-com/marketing/community-relations/-/epics/97
<!-- Link to Child epic where necessary -->
/child_epic
/cc @gitlab-de
<!-- Mention team members that should be aware of the epic -->
/cc
## 👀 Pins
* [Dev Evangelism Release Evangelism handbook](https://about.gitlab.com/handbook/marketing/developer-relations/developer-evangelism/social-media/#release-evangelism) provides all resources.
* [#release-post](https://gitlab.slack.com/archives/C3TRESYPJ) Slack channel (internal)
### ✍ Release post
* [Release Post MR](FIXME_MR)
* [Release Post Review App](FIXME_REVIEWAPP)
#### CommunityApps Campaign Links
> Create campaign links in the [Release Evagelism Campaign](https://campaign-manager.gitlab.com/campaigns/view/3), under the Community Team in [CommunityApps](https://campaign-manager.gitlab.com/), and add them here.
- Twitter:
- LinkedIn:
- Mastodon:
## 🔥 Interesting Items
### MVP
<!-- Create a screenshot from the MVP section, tag the user if possible, and give a shoutout, linking the blog post `#mvp` anchor. -->
### Plan/Create/Manage
<!-- Issues, epics, code review, editor, roadmaps, etc. -->
- [ ] Text:
- URL:
### CI/CD
<!-- CI config, editor, runner, deployments, environments, etc. -->
- [ ] Text:
- URL:
### IaC/GitOps
<!-- Configure, Package, Release, Deploy, etc. -->
- [ ] Text:
- URL:
### DevSecOps
<!-- Secure, Protect, SAST, container/dependency scanning, etc. -->
- [ ] Text:
- URL:
### Observability
<!-- Metrics, Opstrace, -->
- [ ] Text:
- URL:
## ❤️ Social Shares
- Item:
- Twitter:
- LinkedIn:
> 💡 Add a new buffer campaign and post screenshots into this issue.
/label ~"dev-evangelism" ~"DE-Type::Evangelist" ~"DevRel-Content" ~"Content-Releases"
/cc @gitlab-de
CFP epics should not be created to avoid clutter on the Roadmap, instead the CFP label should be added to the corresponding event's epic. If no related event epic exists, create one and add the CFP issue to it.
The DE-Bot uses the GitLab Triage project to ensure appropriate & consistent usage of labels.
The Developer Evangelism team workflow is supported by labels, which help determine the type of issue, its status, and other relevant information. The team's primary label is dev-evangelism. All issues the team owns, are a part of, or needs to be aware of, should be tagged with dev-evangelism. Other Labels are listed below:
| CFP Labels | Description |
|---|---|
DE-DueSoon |
This is used to monitor DE issues that are due soon |
DE-Peer-Review |
Feedback is needed on the issue from DE team members |
DE-Ops |
Used to label issues related to the Developer Evangelism Ops in DevOps theme |
DE-Dev |
Used to label issues related to the Developer Evangelism Dev in DevOps theme |
DE-k8s |
Used to label issues related to the Developer Evangelism Kubernetes theme |
The team creates issues for iteration, team discussions, and other issues for internal processes. These issues are tracked using the following labels:
| Process Labels | Description |
|---|---|
DE-Process::Open |
Process related issues that are still being discussed or worked |
DE-Process::Pending |
Process related issues on hold due to an external factor |
DE-Process::Done |
Completed Process issues |
DE-Process::FYI |
Issues that require no action from the team, but need to be aware of |
| Label | Use |
|---|---|
DE-Status::ToDo |
Issues that are planned for the future |
DE-Status::Doing |
Issues the team is currently working on |
DE-Status::Done |
Issues that have been completed |
DE-Status::OnHold |
Issues that are for whatever resume pending |
DE-Status::Cancelled |
Issues that have been cancelled, either by the team or the requestor in the case of a consulting request |
DE-Status::FYI |
Issues the team needs to be aware of but no action is required |
The default flow is from ToDo -> Doing -> (OnHold) -> Done. Issues with FYI don't go through any workflow, as they are owned by another team and will go through a different workflow.
These labels help identify the type of activity documented in an issue. These are useful for the team to understand where time is spent and assign appropriate DRIs.
| Label | Use |
|---|---|
DE-Type::Content |
Issues for Content creation, this can be any type of content |
DE-Type::Evangelist |
Issues for the Evangelist program |
DE-Type::Process |
Issues for operational activities of the team, mostly owned by the Developer Evangelism Program Manager |
DE-Type::Response |
Issues for Community Response activities |
DE-Type::Consulting |
Issues requested by other teams, more details below |
Requests from other teams for the Developer Evangelism to own, participate or collaborate on activities are classified as consulting, and these requests are usually labeled based on the team requesting. These are teams in the company that the Developer Evangelism team collaborate with often, here are their labels:
DE-Consulting::AlliancesDE-Consulting::CorpCommsDE-Consulting::CorpEventsDE-Consulting::CommunityDE-Consulting::EngineeringDE-Consulting::FieldMktgDE-Consulting::GrowthMktgDE-Consulting::ProductDE-Consulting::SalesThese labels are required where an issue has DE-Issue-Type::External and DE-Type::Consulting, aside the team label dev-evangelism and DE-Status scoped label. If your team is not listed, you can still submit a request and it will be triaged appropriately
Issues created for Consulting count against team quarterly budgets, you can learn more in the Request budgets section below.
These labels are automatically assigned by the DE-Bot for triaging purposes.
| Label | Use |
|---|---|
DE-Bot::Auto |
Issue is automatically created by DE-Bot and will be closed after a period, usually 2 weeks from creation |
DE-Bot::Hold |
Issue is currently on hold and should not be triaged by teh DE-Bot except where it has been in the Hold status for too long. |
DE-Bot::Skip |
The DE-Bot should not perform any action on issues with this label |
DE-Bot::Triage |
Issue has been silent for a while and needs to be triaged |
DE-Due::AddDate |
An Issue needs a due date |
DE-Due::N/A |
Due date is not needed because the team doesn't own the issue or a due date is not applicable |
DE-Due::Past |
Issue is past its due date |
DE-Due::Soon |
Issue is due soon |
| Label | Use |
|---|---|
DE-Release-Evangelism |
Release Evangelism issues, often auto created and closed by the DE-Bot |
DE-Issue-Type::External |
Issues created by Other teams |
DE-Issue-Type::Internal |
Issues created & owned by the DevEvangelism team |
These labels are used to track workflow of the CFP submissions.
| Label | Use |
|---|---|
CFP |
Identifies CFP labels, this is needed |
CFP::Upcoming |
Identifies CFPs that will be open soon |
CFP::Open |
Identifies Open CFPs |
CFP::Closed |
Identifies Closed CFPs |
CFP::Cancelled |
Identifies Cancelled CFPs |
CFP::Submitted |
Identifies that submissions were made for the CFP |
CFP::Accepted |
Identifies if any submission was accepted for a CFP |
CFP-EDU |
Identifies CFPs that are relevant to the Education team |
CFP-OSS |
Identifies CFPs that are relevant to the Open Source teams |
CFP-Submitted::{0..7} |
This is used to note the number of submissions that were made for metrics purposes |
CFP-Accepted::{0..7} |
This is used to note the number of acceptances for metrics purposes |
The CFP workflow is based on the CFP labels explained above.
Example CFP workflow using quick actions:
~"CFP" ~"CFP::Open" labels.~CFP-Submitted ~CFP-Submitted::1~CFP-Submitted:: scoped label to reflect the correct number.submissions section in the issue. Comment on the issue for visibility./label ~CFP-Submitted ~CFP-Submitted::1
CFP::Closed label and update the due date to the CFP notification date listed in the issue./due <cfp notification date>
~CFP-Accepted ~CFP-Accepted::1~CFP-Accepted:: scoped label./label ~CFP-Accepted ~CFP-Accepted::1
DE-Status::Done and close it./label ~DE-Status::Done
/close
If no talks were accepted, only close the issue shown above.
If the CFP closed without submission, add the CFP::Closed label. In case the CFP was planned to submit, and decisions were made otherwise, add the CFP::Cancelled label.
Team General Issue Board Team Activity Type Issue Board CFP Issue Board
In order to prevent burnout, prioritize requests appropriately, and ensure we successfully deliver on the requests to which we commit, our team has created budgets for our internal stakeholders. These budgets encourage team members to prioritize their requests, ensuring our team addresses the highest priority needs for GitLab.
These request types fall into the following categories:
Ongoing activities including team-driven content creation and speaking opportunities that supports our goals and OKRs, release support, and social media monitoring, including Hacker News, do not count towards any team budgets.
Event requests include both event attendance (ex: attending client meetings, event staffing, attending dinners or social events, monitoring events for news) and speaking engagements at events such as demos and presentations.
CFP requests include asking a Developer Evangelist to submit a proposal for an event or media opportunity or support a fellow team member in submitting to an open CFP.
See Requesting a Developer Evangelist to submit a CFP to request a Developer Evangelist to submit to a CFP for a corporate, field, or partner event.
Content requests include blog post, podcasts, media interviews, or any request that involves engaging a Developer Evangelist in a media opportunity.
| Request Type | New / Existing Content | Budget score |
|---|---|---|
| Event | New | 3 |
| Event | Existing / No content | 1 |
| CFP | New | 2 |
| CFP | Existing | 1 |
| Content | New | 2 |
| Content | Existing | 1 |
Each team listed below is allocated 15 points per quarter for requests:
| Team | Team Label |
|---|---|
| Corporate Events | DE-Consulting::CorpEvents |
| Corporate Communications | DE-Consulting::CorpComms |
| Developer Relations | DE-Consulting::Community |
| Growth Marketing | DE-Consulting::GrowthMktg |
| Field Marketing / ABM | DE-Consulting::FieldMktg |
| Sales / SDRs | DE-Consulting::Sales |
| Alliances | DE-Consulting::Alliances |
| Product | DE-Consulting::Product |
| Engineering | DE-Consulting::Engineering |
If your team is not listed above, we will handle your request based on our availability.
This process covers any content request, Webcast, Interview, Meetup, etc. The process involves the following: