Community Relations Program Management

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

On this page

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

The Community 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.

Community Relations handbook updates

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

MRs must be tagged with the Community 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.

Community Relations issue boards

| Board | Program | Usage | Notes | | — | — | — | — | | OKRs | Team | Quarterly OKR status tracking | | | Community Team Content | Team | Blog content the team is working on | Top level group board | | Community Team, by assignee | Team | Issue workload per team member | Top level group board | | Evangelist Program | Evangelists | Work related to the Evangelist Program | | | Meetups | Evangelists | Meetup tracking and organization | | | Code Contributor Program | Code contributors | Work related to the Code Contributor Program | | | Education Program | Education | Work related to the Education Program | | | Developer Evangslism | Developer Evangelism | Developer Evangelism issues across the entire gitlab-com group | | | Consortium Memberships | Open Source | Track all activities related to GitLab's consortium memberships | | | Open Source Partners Support (Internal) | Open Source | Contains sensitive partner requests and therefore confidential. | | «««< sites/handbook/source/handbook/marketing/community-relations/project-management/index.html.md | Linux Foundation Parntership | Open Source | Activities and initiatives related to our partnership with the Linux Foundation | | | Startups | Startups | Issues related to the Startups program | | ======= | Linux Foundation Parntership | Open Source | Activities and initiatives related to our partnership with the Linux Foundation | | | Startups | Startups | Issues related to the Startups program | |

sites/handbook/source/handbook/marketing/community-relations/project-management/index.html.md | Community Sponsorship Requests | Community Ops | Requests from the community for event and other types of sponsorship | |

Community 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

Label	Program	Usage	Notes
Community Relations	Community Relations	Main team label	gitlab-com group label. Merge requests with this label generate automatic notifications for the Community team via the Slack channel #community-relations when they are merged
Open Source Program	Open Source	Main program label	gitlab-com group label
Open Source	Open Source		gitlab-org group label
Open Source Partners::Backlog	Open Source	Internal support issues members of the GitLab Open Source Partners program have filed
Open Source Partners::Assigned	Open Source	Internal issues someone has been assigned to address on behalf of GitLab Open Source Partners program members
Open Source Partners::Working	Open Source	Internal issues we're working on behalf of GitLab Open Source Partners program members
Open Source Partners::Complete	Open Source	Internal issues we've resolved for members of the GitLab Open Source Partners program
movingtogitlab	Open Source	Track open source migrations
Evangelist Program	Evangelists	Main program label: Tech meetups, tech speakers, and community-driven evangelism
Meetups	Evangelists	GitLab Meetups planning and tracking
Heroes	Evangelists	Heroes applications, content, speaking engagements, and other Heroes program issues
Speaker Needed	Evangelists	Events or meetups that need a speaker
become-a-speaker	Evangelists	Support for community members who want to become tech speakers	Community Relations group label
heroes-content	Evangelists	For issues related to a blog, video, or other content generated by a GitLab Hero	Project label
heroes-talk	Evangelists	For issues related to a CFP submission or tech talk given by a GitLab Hero	Project label
request-for-heroes	Evangelists	Share speaking, blogging, and other contribution opportunities with GitLab Heroes	Project label
Code contributor program	Code contributors	Main program label: for general issues related to the program
1st contribution	Code contributors	Automatic contribution label	gitlab-com group label
1st contribution	Code contributors	Automatic contribution label	gitlab-org group label
Community contribution	Code contributors	Automatic contribution label	gitlab-com group label
Community contribution	Code contributors	Automatic contribution label	gitlab-org group label
Hackathon	Code contributors	Community contribution during GitLab Hackathon events	gitlab-org group label
GitLab Hackathon	Code contributors	Community contribution during GitLab Hackathon events	gitlab-com group label
OKRs	Team	Quarterly team OKRs
Community Team Content	Team	Track the status of content created by the team. Generally blog posts	Top-level group label
education program	Education	Main program label: for general issues related to the program
dev-evangelism	Developer Evangelism	Any issue in the gitlab-com group where the developer evangelism team is involved

Community 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 Community 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 Community 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.