Engineering at GitLab - Topics on how we do engineering in a remote environment
Proposal
I'm currently part of the MIT TMRG mentorship program and as part of the program, each mentee is expected to select a project to complete.
As more companies are struggling to shift over to a remote environment because of COVID and as more companies start switching over to remote-first or all-remote, we are in a unique position to share our perspective on how we do all-remote engineering at GitLab.
We've had a lot of great content from @dmurph about how companies should go all remote and everything related to that but I was thinking it would be beneficial for us to create content specific to an engineering perspective.
Checklist
-
If you have a specific publish date in mind (please allow 3 weeks' lead time) -
Include it in the issue title -
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 -
Add sensitive label -
Mention @nwoods
to give her a heads up ASAP
-
-
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)