Community Newsletter

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

On this page

• Overview of the Community Newsletter
  • Process
  • Format
    • Submissions

Overview of the Community Newsletter

We run a monthly Community Newsletter to share developer-focused content, keep community members informed about upcoming events, and promote contributions within the community. The target audience for this newsletter is aspiring and existing GitLab contributors in our community. This newsletter will not be used to drive or generate leads.

Process

The Community Newsletter is scheduled to send on last Thursday of each month at 10 AM PT / 6 PM UTC.

• Open an issue using the community-newsletter template for the upcoming draft at least two weeks before the due date.
• label Community Newsletter::Draft: the newsletter is put together in an issue with submissions from the community and GitLab team members.
• Send a slack reminder for the content deadline. Content is due the week before the planned send date to allow time for building the draft, design, and reviews.
• Collaborate with the Social Marketing team on copy for sharing and promoting the newsletter issue.
• label Community Newsletter::Ready: the newsletter is ready to be compiled in Mailjet. Mailjet is an email marketing used amongst other teams at GitLab to build and send newsletters.
• label Community Newsletter::Feedback: After the newsletter has been sent, we leave the issue open for a week to collect feedback.
• Capture the newsletter performance data in the issue, address any feedback for future iterations, and then close the issue.

Format

• Introduction: a welcome message from the curators sharing projects they are working on, upcoming events, and a summary of the issue.
• Featured Events: a feature on upcoming meetups or highlights from a recent community event.
• GitLab Release Highlights
• Resources: technical content from the GitLab Blog and other newsletters or resources.
• Upcoming opportunities (e.g CFPs, projects)
• Community Spotlight: a spotlight on our Community Programs or GitLab Heroes
• Community Shoutout: sharing a tweet, video, or fun clip from the community.

Submissions

We would love to hear from you! To submit to the newsletter, please search for an active Newsletter Issue with the label Community Newsletter::Draft and share your submission in a comment.