These can also be found on the GitLab Availability calendar.
If a team member wants to tackle an issue from the blog posts project, they should open a new issue in the Content Hack Day project and mark it as related to the existing blog posts project issue.
Team members 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.
Please also refer to the blog handbook for guidance, and feel free to submit a merge request to improve it!
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 team members 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 7/13, complete posts need to be submitted by the end of the day on 7/20). Please assign to @rebecca for review.
The post should be reviewed by a peer before assigning to Rebecca.
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!
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 team, 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.
team prizeon the issue). If a team member wants to propose a topic to be considered for the team prize, they can open an issue and ping @rebecca to review the topic suggestion before writing, or mention on their merge request that they would like to propose it be included in the team prize contributions.
Prize: An additional evangelism dinner
Tiebreaker: In the unlikely event we have two teams with equal claim to the prize, we will award the prize to the team with the most additional blog posts submitted (i.e. those that are on topics we didn't suggest).
Prizes: GitLab noise-canceling headphones OR select a one-off swag item
Note: Individuals don't need to stick to our suggested topics to qualify, but their posts won't count towards the team prize if they aren't from the suggested posts.
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.
Team members may expense up to US $15 for snacks and drinks to keep you going throughout the day. Use the category
Meals - company provided.