GitLab Speakers Bureau

1. You are here:
2. Handbook
3. Marketing
4. Community Relations
5. Developer Evangelism
6. GitLab Speakers Bureau

Maintained by:

On this page

• What is the Speakers Bureau?
• Find a speaker
• Join the Speakers Bureau

What is the Speakers Bureau?

The Speakers Bureau is a group of GitLab team members and members of the wider GitLab community who are available to participate in events and deliver talks about GitLab, CI/CD, open source, remote work, and other topics.

Find a speaker

A list of speakers bureau members can be found on our Speakers Bureau page. After identifying a speaker for an event or other speaking opportunity, please follow the instructions on the Speakers Bureau page.

Join the Speakers Bureau

If you would like to join the speakers bureau, we ask that you submit an MR to add yourself to the Speakers Bureau page. This can be done by adding the following lines to the speakers.yml file in the www-gitlab-com project.

To create an MR for the Speakers Bureau page, you will need:

• Your personal Twitter / GitLab handles
• Links to recent, relevant presentations or talks you have delivered

Once you have the above items, follow these steps to add yourself to create your MR:

1. Go to the speakers.yml file in the GitLab.com / www-gitlab-com project.
2. On the file page, click on the button labeled Web IDE near the middle of the page.
3. For community members: if prompted, click Fork to create a Fork of the repo which will allow you to make changes and submit a Merge Request.
4. You should see the speakers.yml file open in your browser. Add the fields as detailed at the top of the file and enter your information into each of the blank fields.
5. Once you have finished adding your information, click the Commit button in the bottom left. It should say something like 1 unstaged and 0 staged changes. This will bring up a sidebar with an Unstaged and Staged area.
6. Check the file to ensure your updates are what you expect. If they are, click the check mark next to the filename to "stage" these changes.
7. Once you have verified all of the edits, enter a short commit message including what you've changed. Choose Create a new branch. Name the branch in the format of YOURINITIALS-speakers-bureau or similar. Tick the Start a new merge request checkbox. Then click Commit once more.
8. Click on the Activity link in the header to go to your Activity page. Once there, click on the blue Create merge request button at the top of the page.
9. Fill out the merge request details. Community members who are applying should tick the box to Allow commits from members who can merge to target branch as detailed on the Allow collaboration on merge requests across forks page in our docs.
10. Team members should assign to @johncoghlan and community members should mention @johncoghlan in a comment in the merge request so our team can review and merge.