Content Hack Day takes place quarterly, on the second Friday of the quarter. It's a day dedicated to writing posts for the GitLab blog, and all GitLabbers are encouraged to take part. GitLabbers are welcome to brainstorm post ideas in the #content-hack-day channel on Slack, or join the open Zoom call with content team members to discuss. The Zoom call link will be announced and pinned in the Slack channel.
These can also be found on the GitLab Team Meetings calendar.
Starting from www-gitlab-com project: If you've chosen an issue from the blog-post backlog, label it
content hack day and start a merge request for your draft.
Starting from the Content Hack Day project: Once you've chosen an issue to work on from the Content Hack Day, assign to yourself, and start a merge request in the www-gitlab-com project. Do not create a duplicate issue in the www-gitlab-com project.
Make sure the merge request and issue are cross-linked. If you are drafting in a Google doc, include a link to the doc in the MR. The post should be reviewed by a peer before assigning to Rebecca.
In order to be eligible for an individual or team prize, participants must begin working on their post/s on the day of the event, and submit a complete draft (merge request or Google doc in the case of GitLabbers unfamiliar with creating a blog merge request) by the end of the day on the Friday following the Hack Day (so for the event taking place on 02/08, complete posts need to be submitted by the end of the day on 02/15).
The Monday following the deadline, the managing editor will move all issues with an associated MR to the www-gitlab-com project for tracking. Any issue that doesn't have an associated MR will be not be counted.
Your post will be reviewed as soon as possible, but please be prepared for some delay! The point of the Hack Day is so that you have a dedicated day for writing and working on posts with your department, but we will stagger publishing your posts throughout the rest of the quarter.
There may be some feedback for you to address after your review; this is a collaborative process and it should hopefully result in the best possible version of your blog post.
A member of the content team will let you know when to expect to see your post live, so you can go forth and share it with your networks.
Please note, it is possible that the content team will determine that your post is a better fit for our audience on LinkedIn or Medium. This is to ensure your post gets the best possible exposure and reaches the people who would be most interested in it. We'll notify you when we review your post if that's the case. Don't worry, your contribution will still count towards the prizes!
Criteria: Minimum 50 percent team participation (participation can be in the form of opening issues, submitting MRs, reviewing other team members' blog posts or joining the Zoom call on the day) + the highest proportion of blog posts relative to the team's size.
To be considered for the team prize, all blog posts must be written to the theme:
Prize: An additional evangelism dinner
Tiebreaker: In the unlikely event we have two departments with equal claim to the prize, we will award the prize to the department with the most additional blog posts submitted (i.e. those that are on topics outside of the theme).
Prizes: GitLab noise-canceling headphones OR a GitLab messenger/duffel bag
Swag will be given away randomly throughout the day. Anyone who has joined the Zoom call or been active in the project or the Slack channel is eligible. Names will be entered into a random picker to decide on winners.
Examples of spot prizes: GitLab reusable coffee cup, GitLab water bottle, GitLab speaker, coffee gift card.
GitLabbers may expense up to US $15 (or equivalent) for snacks and drinks to keep you going throughout the day. Use the category