How engineering teams can collaborate remotely - 2021-02-09

Proposal

Blog post that looks into some best practices for engineers looking to collaborate remotely.

Featuring some videos from GitLab Commit sessions:

• Build incredible software products with a Remote DevOps culture
• How to successfully onboard engineers

On these overarching topics:

• Remote meetings (see https://about.gitlab.com/company/culture/all-remote/asynchronous/#async-30-at-gitlab)
• How to overcome common remote engineering challenges

Checklist

• If you have a specific publish date in mind (please allow 3 weeks' lead time)
  • Include it in the issue title and apply the appropriate milestone (e.g. Blogs October 2020)
  • Give the issue a due date of a minimum of 2 working days prior
  • If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior
• If time sensitive
  • Add ~"Blog: Priority" label and supplied rationale in description
  • Mention @rebecca to give her a heads up ASAP
• If wide-spread customer impacting or sensitive, mention @nwoods to give her a heads up ASAP, apply the sensitive label, and check the PR handbook in case you need to open an announcement request instead of a blog post issue
• If the post is about one of GitLab's Technology Partners, including integration partners, mention @TinaS, apply the Partner Marketing label, and see the blog handbook for more on third-party posts
• If the post is about one of GitLab's customers, mention @KimLock and @FionaOKeeffe, apply the Customer Reference Program label, and see the blog handbook for more on third-party posts
• Indicate if supporting an event or campaign
• Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment)