To build GitLab's technical brand with deep, meaningful conversations on engineering topics relevant to our industry by leveraging our community of team-members and the broader ecosystem.
The GitLab developer evangelists are engineers who enjoy learning and teaching the latest technology topics with the wider community. The evangelists are supported by program management within the team and also collaborate closely with the content and PR teams in corporate marketing to amplify their voices. There are two specific goals for the team:
We are members of the Community Relations team.
We build our thought leadership on social media. See Developer Evangelism on Social Media to learn more about our strategies and become an evangelist yourself.
Our team maintains many projects to help show off technical concepts, engage with communities, provide examples of using GitLab with other technologies, and automate our team processes. See Developer Evangelism Projects for a list of all of those projects.
The Developer Evangelism team has several interactions with "CFPs" - calls for proposals for speaking at conferences. Firstly, many of our Developer Evangelists directly contribute by speaking at conferences themselves. In addition, our program team manages responses to CFPs for GitLab through our issue boards.
We work in the open using the GitLab's Corporate Marketing issue tracker. We own the label dev-evangelism which can be applied to issues in any project under the gitlab-com and gitlab-org parent groups.
You can follow the latest our team is working on by looking at our label-based issue board.
Using the dev-evangelism label on an issue means we are working on it or participating in the ongoing conversation. Team members are subscribed to issue/MR updates for this label.
The dev-evangelism label is accompanied by some labels we use to organize our work.
You only need to use the dev-evangelism label on issues requiring the attention of the Developer Evangelism team. Other labels are applied by the team as their state change or as contained in various issue templates.
| 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 |
If you require a Developer Evangelist's help for anything, please use this "Developer Evangelist Request" issue template to create an issue, and we will get back to as soon as possible. On creating the request issue, two labels are applied: DE-Request::New & DE-Request-Type::External and transitioned through different states as listed below:
| Request Labels | Description |
|---|---|
DE-Request::New |
Newly created requests |
DE-Request::Open |
Requests that are still being worked on or considered |
DE-Request::Done |
Completed requests |
DE-Request::Cancelled |
Requests not considered by the team |
DE-Request-Type::External |
Identifies Requests created by other teams |
DE-Request-Type::internal |
Identifies Requests created by Developer Evangelism team members |
See 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.
Covers any content request, Webcast, Interview, Meetup, etc. These content issues first get the parent dev-evangelism label applied, and are then transitioned through different stages using the scoped labels below:
| CFP Labels | Description |
|---|---|
DE-Content::new-request |
New content request |
DE-Content::draft |
A member of the TE team is working on the content |
DE-Content::review |
Content Author is seeking review from other team memebers |
DE-Content::published |
Content has been published |
DE-Content::Repurposing |
Content is being repurposed on other platforms or mediums |
DE-Content::cancelled |
Content is no longer needed, and no one is working on it |
GitLab team members can also reach us at any time on the #developer-evangelism Slack channel where we share updates, ideas, and thoughts with each other and the wider team.
