Thanks for checking out the GitLab Team Member Social Media Policy and helpful Guidelines! We have two goals:
Much of this can be summed up into this sentence: Be diligent and if it's questionable, don't say it. You are personally responsible for the social posts, likes and shares, and replies you post on social media while representing GitLab. Everything you publish is publicly viewable and will be available for a long time even if redacted. Remember that you represent GitLab and our culture. When commenting on posts please keep in mind: "Don't argue but represent".
You'll be asked to confirm reading this section during your onboarding to the company. For existing employees, we'll ask everyone to review and sign off on review in partnership with legal.
The GitLab Social Media policy for team members applies to traditional social media channels, like Twitter and LinkedIn, as well as "social-like" sites, like HackerNews, Reddit, blog comments (on the GitLab website, Medium, or any other blog site), message boards, and forums (including the GitLab Forum).
Please adhere to the Community Code of Conduct, as we would require of all members of the community.
Social Media somestimes generates press and media attention or legal questions. Please refere all inquires to the Communications Team in the #external-comms Slack channel.
Whether you're an intern or our CEO, protecting the GitLab brand, the company, and our entire team is a part of your job description.
Sharing information that would be considered confidential or a part of legal situations could negatively impact your team member status, and depending on the severity of the information, be considered a legal issue itself.
In case you want to connect with fellow team members of GitLab on social media you have to keep it professional. With this communication we would want you to consider GitLab’s Communication Guidelines at all times. Aligned with our Anti-Harrassment Policy it is expected that everyone will contribute to an inclusive and collaborative working environment and respect each other at all times.
Please keep your identify clear on your social media channels by not using the GitLab logo as your profile image, not adding GitLab to your @handle, and not adding the company to your display names. It should be clear to everyone that you are a team member of GitLab, but not GitLab the company. Use common sense when selecting pictures and names to use. We'll always work to get profile names and visuals updated to reflect who runs the account, but if we come across profiles that don't respond to these requests, we will report them for impersonating our brand.
As a Team Member of GitLab, you aren't authorized to create company/brand social media profiles to use for your work. If promoting content should come from the company, you'll need to open a request issue with the organic social team. If the corporate marketing team encounters unauthorized profiles, they will be treated as external threats and reported for impersonation. Currently, there is no formal method for requesting new brand channels nor is there an outline for managing to do so. It's best to use personally identied social media profiles to share your posts.
As part of your role at GitLab, you may be responsible for a contest or a sweepstakes with social media elements. It's important to follow legal guidelines. Essentially, as a representative of GitLab, if you're promoting the contest on your social media channels, it will need to follow the same rules as what the GitLab brand channels will need to follow. You can learn more about legal and contests in the handbook here.
If you've reviewed the policies above, you're ready to start using social media. We've included some best practices and what to avoid below. Don't hesitate to reach out to the social media team for any assistance or with questions in the #social_media_action Slack channel.
If you've written a blog for our site, contributed to our latest release, or joined a webinar/webcast, you should want to tell your networks about it. Not only does this provide a way to build your own following and expertise in the public domain, it's also a great way to add critical promotion to your work. Promoting on social media isn't just about the GitLab brand channels, it's an orchastra of efforts, which includes team member support and advocacy.
When responding to posts from your personal account, feel free to incorporate your own style and voice. Talk to people as if you were talking to them in person. Be sure to speak with “we” and not "I" (as often as appropriate) to represent the company and the community.
Someone doesn’t like something? Ask them to tell us more in the issue tracker. Someone thinks GitLab could be better? Invite them to submit a feature proposal. Any criticism is an opportunity to improve in our next iteration.
When responding to posts from your personal account, feel free to incorporate your own style and voice. Talk to people as if you were talking to them in person.
Please do not engage in competitor bashing. Instead, highlight positive differences — it's best to focus on the ways that GitLab outperforms other solutions.
You may come across angry users from time to time. When dealing with people who are confrontational, it’s important to remain level-headed. Sometimes, the best course of action is to walk away and not engage with the person at all. Use your judgment in how you approach rude or off-putting comments from strangers in real life to help you decide.
For a foundational understanding of these nuances, read GitLab's guide to communicating effectively and responsibly through text.
If you are unsure of how or if to respond to someone who has responded to your posts, join the #social_media_action Slack channel and ask for feedback.
Profile assets for social media can be found in the corporate marketing repository
Please do not use the GitLab logo as the avatar for your personal accounts on social. You are welcome to use our branded banners, but it is important that your profile avatar does not lead users to confuse your account with the official GitLab accounts.
While you should display the fact that you work at GitLab in your bio if you intend to advocate for GitLab on social, we suggest that you avoid including the word
gitlab in your handle. Team member advocacy is incredibly valuable and we are lucky to have so many engaged team members, but creating an account to solely post about GitLab is not effective. The reason team member advocacy is so powerful is because people trust employees more than brands and executives. Your advocacy is powerful when it is authentic, and having an account that only exists to promote GitLab will not ring true to others who browse your tweets.