Developer Advocacy

On this page

Developer Advocates act as spokespeople and liaisons between GitLab and its users. Their role is to make developers happy to use GitLab by getting customer feedback into the product.

Code

In addition to providing enhancements to GitLab itself, Advocates can also provide miscellaneous code samples for everyone to view.

Public Speaking

Speaking at/attending events is an important facet of developer outreach as it's one of the best places to get in front of people.

Where to Speak

There are a few places where you can keep tabs on open Calls for Papers.

In general, try to avoid sponsored speaking slots/slots we have to pay to get. There's value in these, but attendance rates are lower than organic conference talks.

Talk Preparation

Abstracts

Slides

Practice!

At the Event

Speaking

Q&A

If you do a Q&A session, it's important to maintain control of it so that everyone gets a chance to ask questions they may have.

Post-Talk

Talk Debrief

After speaking, it's important to make note of things that went well and things that need improvement. You can use the following template to get started (but feel free to modify it). Put your debrief in a comment on the event's issue. If no issue exists, please create it and tag Emily so she sees.

Event Name:
Event Dates:
Event Location:

Talk Title:
Talk Presenter(s):
Talk Slides (if available online somewhere):
Talk Abstract:
Talk Time (include timezone):
Attendee Estimate (how many people attended your session?):

How was the talk received by the audience?

What went well?

What didn't go so well?

Were there any technical difficulties?

What questions did people ask?

Events

Events are an important part of developer relations efforts. You can expect to travel a lot. Keep track of which events you go to via your calendar and make sure you take some vacation time.

Selecting Events

Most events will be selected by field marketing. If you have suggestions for events, open an issue with the following information:

Before the Event

Be sure to use social channels to let people know you'll be there. If you're giving a talk, make sure to include that too. Add events to your calendar and make sure to let everyone else on the developer relations team know so they can plan accordingly.

At The Event

After the Event

Event Debrief

After an event, put a debrief together to help us determine whether we're hitting our goals. A short summary should answer:

This information can be posted on the relevant event issue in the issue tracker. If no issue exists, please create one and tag Emily in it. If you gave a talk be sure to include a debrief about that as well.

Make sure to follow up with anyone you spoke to at the event, even if it's just to say "Thanks for chatting!"

Event organizers also love to hear feedback about their events. Make sure to thank them and tell them what they did well. If things didn't go according to plan, make sure they know that too so they can incorporate your feedback next time.

Travel

Please abide by GitLab's travel policy unless an exception is noted below.

Booking Travel

Packing List

Here's a list of things you may want to put in your carry-on bag:

If you're speaking at an event, include the following:

In your checked bag:

Social Media

Advocates follow these guidelines when posting as GitLab.

Social Media Channels

GitLab has a presence across many social media channels. The following is a list of channels we actively monitor.

Twitter

There are two GitLab Twitter accounts

Representing GitLab on Twitter

Express gratitude

Be friendly

About using the tools

Ignore tweets that are negative about competitors

Use English

Replies to commonly asked questions on Twitter

Facebook

YouTube

LinkedIn

Docs comments

Comments are enabled in the GitLab docs portal where users can leave a note if something is wrong with our documentation.

They are powered by Disqus and are tracked in the docs-comments chat channel. When an advocate replies to a comment:

Other channels

See the ones listed on our getting help page.

Blogging

The developer relations team may need technical content that is more abstract than how-to technical guides. Developer Advocates can produce relevant content to fill the content calendar.

Training Programs

CI/CD Training

Overview

We're offering training around CI/CD and GitLab to raise awareness of the feature and introduce people to the concept of rapid testing and deploying.

Session Breakdown

In general, the slides contain the most up to date outline of the content. However, attendees can expect to see the following points in a 3 hour session:

Post-Session

Thank everyone for coming and make sure attendees get swag.

Each attendee should be asked to fill out a survey while on-site at the event. You can view an example survey here.

Slides

The slides for this training can be found here. The content is subject to change from time to time, so please be sure to make a copy for your own reference.

In general, the speaker notes contain the content to be covered on the slide. Much of the training is a live demo, but there are slides with screenshots in case the live demo doesn't work. You're encouraged to do the live demo whenever possible as it's a more compelling story.

If you'd like to use this deck or make edits, please make a copy in your own Drive folder first.

Tentative Schedule

Scheduling/Promoting

Ideally CI/CD training will be paired with events that we plan on attending. If there are no events to attend, we will host trainings in cities with larger GitLab user bases such as San Francisco, Toronto, or Amsterdam. Community members can host these trainings anywhere provided that the location is conducive to getting more than 20 attendees and there’s a strong community.

Venues

Try to find venues that are close to public transit/have parking. Ideally venues are located downtown in the desired city. Make sure we can bring snacks and drinks for attendees or ask about catering.

Landing Pages

Follow this guide to create campaigns in SalesForce and Marketo. If you get stuck, talk to the Marketing Ops team for help.

You will also need to create a landing page in Unbounce to collect RSVPs. You can copy an existing page, but make sure to change the information outlined in the guide above so that RSVPs count under the right event.

Blog

When the details are finalized, create a quick blog post that outlines what the training is about and key details such as time and location. Make sure this gets tweeted.

Advertising

Once the landing pages are set up, advertise the event through the following channels:

Paid ads can be set up by the Marketing Ops team as needed. Use the "Social Media" issue template in the Marketing project.

Customer Support

While they're not full-time support team members, advocates can field some of the questions the support team receives.