Developer Relations Program Management

1. You are here:
2. Handbook
3. Marketing
4. Developer Relations
5. Developer Relations Program Management

Maintained by:

On this page

• Developer Relations handbook updates
• Developer Relations Roadmap
  • Epics
• Developer Relations issue boards
• Developer Relations labels
• Developer Relations Group Conversation
  • What is a Group Conversation (GC)?
  • Old Group Conversation decks
  • Group Conversation Directly Responsible Individual (DRI)

The Developer Relations team works from issues and issue boards. If you need our assistance with any project, please open an issue and use one of the main program labels anywhere within the GitLab repo.

Developer Relations handbook updates

Merged updates to the handbook are posted to the #community-relations-fyi Slack channel.

MRs must be tagged with the Developer Relations labeled before being merged in order to be posted to Slack. When you create a new MR, be sure to add the label upon creation so this step isn't forgotten. If you are assigned to merge an MR, ensure the label is added prior to merging.

Developer Relations Roadmap

The Developer Relations team conducts project and content planning via the Roadmap in the Developer Relations Group.

Epics

Work items that fit into our team strategy, including events and content plans, are tracked in the roadmap by using Epics and Child Epics.

Please use this template when creating Epics for activities that should appear in the Developer Relations team roadmap:

<!--  Epic Title Formatting Guide:

Dates should be using ISO dates, see https://about.gitlab.com/handbook/communication/#writing-style-guidelines 

Event: Event Name, Location, Date 
Content: Title, Date
Others: Title, Date

Reminder: Start and due dates are required in order for this Epic to display correctly in the team roadmap. 
-->

## Activity Summary


## Goal or expected outcome 



## Team or Individual DRIs
<!--  Please add team label to epic -->


## Relevant Issues, Epics or resources



<!-- Example 

/label ~"Community::Events" ~"Region::AMER" ~"FY24-Q1" 

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 -->
/parent_epic URL 

<!-- Link to Child epic where necessary -->
/child_epic URL 

<!-- Mention team members that should be aware of the epic -->
/cc 

Developer Relations issue boards

Developer Relations labels

• We track the workflow with the Marketing Status labels.
• Some programs use scoped labels in addition.
• Main program labels are defined either at the top gitlab-com or the gitlab-com/marketing group level to facilitate cross-collaboration and visibility across issue boards

Developer Relations Group Conversation

What is a Group Conversation (GC)?

GitLab teams update the rest of the company on what they are achieving and working on through Group Conversations. Group Conversations are an important way to make sure the rest of the organization is aware of what each team is up to, has an opportunity to ask questions, and have a collection of links and information for reference.

Old Group Conversation decks

The Developer Relations team's previous decks are in our Google drive (GitLab employees only). It's useful when putting together the next GC deck to look at the last one to make sure that items on the calendar edge don't get missed or included a second time.

Group Conversation Directly Responsible Individual (DRI)

A DRI from the Developer Relations team will be identified for each GC approximately 3 weeks before the next scheduled GC. The DRI should rotate through team members to give everyone a chance to lead the GC. The DRI is responsible for:

• Creating an issue in the Community Building Project using the community-relations-group-conversation template.
• Complete all the tasks in the group conversation template.
• Prepare a few questions for the team prior to the GC in the case there aren't any questions in the agenda during the GC.
• Lead the GC.
• Close the GC issue.