Commit 5fd6389a authored by Ashton Herrmann's avatar Ashton Herrmann

Change language in handbook from "remote only" to "all remote"

parent 1d206bc7
Pipeline #23172458 passed with stages
in 28 minutes and 34 seconds
......@@ -10,7 +10,7 @@ title: "GitLab Culture"
- [Internal Feedback](/culture/internal-feedback)
- [Inclusion and Development](/culture/inclusion)
- [Top Team Member](/culture/top-team-member)
- [Remote Only](/culture/remote-only/)
- [All Remote](/culture/remote-only/)
## Introduction
......
......@@ -156,7 +156,7 @@ Here is a summary of the responses from 91 team members (57%) who participated.
1. Positive atmosphere
1. Ability to help GitLab achieve the vision
1. Remote opportunity
1. Remote only - “I didn’t want to be the only one not in the office”
1. All remote - “I didn’t want to be the only one not in the office”
1. Open source community
1. Referred by a team member
1. Autonomy
......@@ -248,7 +248,7 @@ Here is a summary of the responses from 91 team members (57%) who participated.
1. Why is the pay gap between Support Engineers and Developers significant?
* The role and responsibility is different for these two roles, therefore, the market data indicates a difference in pay scales. We will review external market data again, during the upcoming merit administration process, to confirm the accuracy of our initial benchmark data.
1. Concern about relocating causing drop in pay
* Note the answer above. This is a relatively new policy in an organization that is helping form the playbook for remote only companies. We strive to find a balance between financially responsible decisions and what's fair to team members.
* Note the answer above. This is a relatively new policy in an organization that is helping form the playbook for all-remote companies. We strive to find a balance between financially responsible decisions and what's fair to team members.
1. Concern for lower pay scale outside the US/Europe based on a lower cost of living
* The [Global Compensation Calculator](/handbook/people-operations/global-compensation) applies a consistent approach to paying a fair wage to all team members. It is not a perfect solution and we aim to [make the model better](https://gitlab.com/gitlab-com/peopleops/issues/234) this spring.
1. Will we use the compensation calculator for non engineering roles?
......
---
layout: markdown_page
title: "Remote Only"
title: "All Remote"
---
## On this page
......@@ -27,7 +27,7 @@ How do we manage our entire [team](/team/) remotely? Sid Sijbrandij, CEO, shares
Our policy of remote work comes from our [value](/handbook/values/) of boring solutions and was a natural evolution of team members choosing to work from home. Remote work allowed for the development of our publicly viewable [handbook](/handbook/). We like efficiency and do not like having to explain things twice.
In on-site companies they take processes, camaraderie, and culture for granted and have it develop organically. In a remote-only company you have to organize it, this is hard to do but as you scale it becomes more efficient while the the on-site organic approach fizzles out.
In on-site companies they take processes, camaraderie, and culture for granted and have it develop organically. In an all-remote company you have to organize it, this is hard to do but as you scale it becomes more efficient while the the on-site organic approach fizzles out.
We have had success bonding with our coworkers in real life through our [Summits](/culture/summits/) that are organized every 9 months and our [Visiting Grants](/handbook/incentives/#sts=Visiting grant).
......
......@@ -15,10 +15,10 @@ extra_js:
## Introduction
We're a **distributed**, **remote-only** company where people work remotely without missing out.
We're a **distributed**, **all-remote** company where people work remotely without missing out.
For this, we use **asynchronous communication** and are as open as we can be by communicating through public issues, chat channels,
and placing an emphasis on ensuring that conclusions of offline conversations are written down.
These communication guidelines are meant to facilitate smooth communication in an ever-growing remote-only company.
These communication guidelines are meant to facilitate smooth communication in an ever-growing, all-remote company.
## External communication
......@@ -120,8 +120,8 @@ members:
1. If you _do_ need a Google Doc, create one with your company G Suite (formerly Google
Apps) account. By default, share it with the whole company using the _Anyone at GitLab can find and access_ link sharing permission
and the _Anyone within GitLab can edit_ access permission (preferred) or the _Anyone within GitLab can comment_ access permission.
Easily do this by creating Google Docs within a Shared Folder in Google Drive.
1. If you have content in a Google doc that is later moved to the website or handbook, [deprecate the Google doc](#how-to-deprecate-a-google-doc).
Easily do this by creating Google Docs within a Shared Folder in Google Drive.
1. If you have content in a Google doc that is later moved to the website or handbook, [deprecate the Google doc](#how-to-deprecate-a-google-doc).
1. When referring to a Google Doc or folder on the Google Drive in the handbook, refrain from directly linking it. Instead, indicate the name of the doc. If you link the url people from outside the organization can request access, creating workload and the potential for mistakes.
(In the past, linking a Google Doc has led to inadvertently opening the sharing settings beyond what was intended.)
This also helps prevent spam from people outside GitLab requesting access to a doc when clicking its link.
......@@ -295,7 +295,7 @@ team member to say "Hi".
1. In video calls everyone should own a camera and a headset, even when they are in the same room. This helps seeing and hearing the person that is talking. It also allows people to easily talk and mute themselves. Using a headset also prevents echo. You wouldn't share an office seat together, so don't share your virtual seat at the table.
1. Please speak up asap when someone on the call hasn't muted their mic to avoid disturbances to the person speaking
1. We start on time and do not wait for people. People are expected to join no later than the scheduled minute of the meeting (before :01 if it is scheduled for :00). The question 'is everyone here' is not needed.
1. It feels rude in video calls to interrupt people. This is because the latency causes you to talk over the speaker for longer than during an in-person meeting. We should not be discouraged by this, the questions and context provided by interruptions are valuable. This is a situation where we have to do something counter-intuitive to make remote-only meetings work. In GitLab everyone is encouraged to interrupt the speaker in a video call to ask a question or offer context. We want everyone to contribute instead of a monologue. Just like in-person meetings be cognizant of when, who, and how you interrupt, we don't want [manterrupting](http://time.com/3666135/sheryl-sandberg-talking-while-female-manterruptions/).
1. It feels rude in video calls to interrupt people. This is because the latency causes you to talk over the speaker for longer than during an in-person meeting. We should not be discouraged by this, the questions and context provided by interruptions are valuable. This is a situation where we have to do something counter-intuitive to make all-remote meetings work. In GitLab everyone is encouraged to interrupt the speaker in a video call to ask a question or offer context. We want everyone to contribute instead of a monologue. Just like in-person meetings be cognizant of when, who, and how you interrupt, we don't want [manterrupting](http://time.com/3666135/sheryl-sandberg-talking-while-female-manterruptions/).
1. We end on the scheduled time. It might feel rude to end a meeting, but you're actually allowing all attendees to be on time for their next meeting.
## Google Calendar
......@@ -347,7 +347,7 @@ There are several benefits and reasons to sharing your calendar with everyone at
1. Use the future version of words, just like we don't write internet with a capital letter anymore. We write frontend and webhook without a hyphen or space.
1. Our homepage is / (with the `about.` and with `https`).
1. Try to use the [active voice](https://writing.wisc.edu/Handbook/CCS_activevoice.html) whenever possible.
1. Refer to environments that are installed and run "on-premises" by the end-user as "self-hosted."
1. Refer to environments that are installed and run "on-premises" by the end-user as "self-hosted."
1. If you use headers, properly format them (`##` in Markdown, "Heading 2" in Google docs); start at the second header level because header level 1 is for titles. Do not end headers with a colon.
1. Always use an [Oxford comma](https://en.wikipedia.org/wiki/Serial_comma) in lists of three or more terms.
1. Always use a single space between sentences rather than two.
......@@ -427,7 +427,7 @@ Keep terms to one or at most two words to prevent people from introducing ambigu
1. Select the meeting and download the video recording to your computer (if you can't find the recording because it was a while ago check "Trash" in that menu on the top left and "Recover" the recording).
1. Go to [YouTube upload](https://www.youtube.com/upload) and log in to the GitLab account (read the secure note in 1Password called "YouTube" for instructions on how to get access).
1. Drag and drop your recording into the window to upload it (keep the privacy dropdown on the default 'Public' setting).
1. While it's uploading, edit the title and description. If the video is meant to be kept unlisted on our YouTube channel, place "Confidential:" at the beginning of the video's title.
1. While it's uploading, edit the title and description. If the video is meant to be kept unlisted on our YouTube channel, place "Confidential:" at the beginning of the video's title.
1. Be sure to include relevant links (for example a handbook page or presentation) in the description, and add the video to any relevant playlists.
1. When it is done uploading press publish and click on the Embed tab to get the code and place that in the relevant part of the handbook or documentation.
......
......@@ -87,11 +87,11 @@ The employment team will **always** publicize the vacancy through the following
1. Tweet the new vacancy post with the help of the content marketing manager and team.
1. Request "soft” referrals by encouraging all GitLab team members to post links to the jobs site on their LinkedIn profiles.
1. [Who's Hiring](https://news.ycombinator.com/ask): On the first of the month, include a comment for GitLab in the Hacker News thread of "Who's Hiring" . Template text:
`REMOTE ONLY GitLab - We're hiring production engineers, developers, designers, and more, see /jobs/ We're a remote only company so everyone can participate and contribute equally. GitLab Community Edition is an open-source Ruby on Rails project with over 1000 contributors.` [Example comment](https://news.ycombinator.com/item?id=16967553)
`ALL REMOTE GitLab - We're hiring production engineers, developers, designers, and more, see /jobs/ We're an all-remote company so everyone can participate and contribute equally. GitLab Community Edition is an open-source Ruby on Rails project with over 1000 contributors.` [Example comment](https://news.ycombinator.com/item?id=16967553)
**Note**: The employment team may advertise the vacancy through the following sites and is open to posting to more, in order to widely publish a variety of vacancies:
1. [Alumni post](https://news.ycombinator.com/jobs) as a Y Combinator alumni we can post directly to the front page of Hacker News. The EA vault has credentials so ask an EA to post. Template text: `GitLab (YC W15, Remote-only) is hiring XXX and more`. [Example](https://news.ycombinator.com/item?id=16854653)
1. [Alumni post](https://news.ycombinator.com/jobs) as a Y Combinator alumni we can post directly to the front page of Hacker News. The EA vault has credentials so ask an EA to post. Template text: `GitLab (YC W15, All-remote) is hiring XXX and more`. [Example](https://news.ycombinator.com/item?id=16854653)
1. [LinkedIn](https://www.linkedin.com/) (Able to post 3 vacancies simultaneously, please mention to employment team if you want your role listed here)
1. [StackOverflow](http://stackoverflow.com/jobs) (Able to post 3 vacancies simultaneously, please mention to employment team if you want your role listed here)
1. [TechLadies](https://www.hiretechladies.com/) (Able to post 4 roles simultaneously, please mention to employment team if you want your role listed here; at this time we are not posting engineering roles to TechLadies)
......
......@@ -34,7 +34,7 @@ to each team member for the purpose of evangelizing the GitLab story. You may u
1. Every now and then, individual GitLabbers really shine as they go above and beyond their regular responsibilities and tasks. We especially like to celebrate the moments where GitLabbers live our values.
* We recognize this through the #thanks channel, and sometimes also through a discretionary bonus.
* Managers can recommend their team members to the CEO for a [$1,000](/handbook/people-operations/global-compensation/#exchange-rates) bonus through a request in BambooHR. We are fixing this amount at $1,000 thoughtfully and purposefully. We want the focus to be on the values and the behaviors, not on the perceived monetary impact to GitLab. This is about recognition.
* Managers can recommend their team members to the CEO for a [$1,000](/handbook/people-operations/global-compensation/#exchange-rates) bonus through a request in BambooHR. We are fixing this amount at $1,000 thoughtfully and purposefully. We want the focus to be on the values and the behaviors, not on the perceived monetary impact to GitLab. This is about recognition.
* A general guideline is that 1 in 10 employees might receive a discretionary bonus each month. This can vary greatly as we don't give out bonuses just to hit a quota, nor would we hold one back because a certain number had already been awarded.
1. For values based bonuses please see [Tinggly](/handbook/incentives/#tinggly)
......@@ -189,7 +189,7 @@ Once the bonus has been processed, change the note in BambooHR to denote the ref
### Visiting grant
GitLab is a [remote-only company](http://www.remoteonly.org/) with GitLabbers all over the world (see the map on our [Team page](/team/). If you want to visit other team members to get to know them, GitLab will pay for your travel expenses. You don't need to work on the same project or team, either, so long as you discuss work for at least part of the time you're meeting. GitLab will pay for **flights, trains, and tranpsportation to and from the airport,** up to a total of [$150](/handbook/people-operations/global-compensation/#exchange-rates) per team member that you visit and work with.
GitLab is an [all-remote company](http://www.remoteonly.org/) with GitLabbers all over the world (see the map on our [Team page](/team/). If you want to visit other team members to get to know them, GitLab will pay for your travel expenses. You don't need to work on the same project or team, either, so long as you discuss work for at least part of the time you're meeting. GitLab will pay for **flights, trains, and tranpsportation to and from the airport,** up to a total of [$150](/handbook/people-operations/global-compensation/#exchange-rates) per team member that you visit and work with.
Note that lodging, meals, and local travel while visiting are not typically covered for anyone as that wouldn't really be fair to those being visited. It may be acceptable to cover a meal, however, if the meeting is pre-announced to other people in the region to encourage as many of them to attend as possible and there are four or more GitLabbers attending.
......
......@@ -370,8 +370,8 @@ How to spell and style commonly used words.
- always capitalized, never abbreviated to K8s (except on social)
- open source
- no hyphen, regardless of how it is used
- remote-only/remote only
- hyphenated only when appearing before a noun ("GitLab is a remote-only organization"/"GitLab is remote only")
- all-remote/all remote
- hyphenated only when appearing before a noun ("GitLab is an all-remote organization"/"GitLab is all remote")
- set up/setup
- two words for the verb, one for the noun ("How to set up a Kubernetes cluster"/"Let's walk through the Kubernetes cluster setup process")
- sign up/signup
......
......@@ -64,7 +64,7 @@ for sustained periods of time. If you feel yourself or notice someone on your te
To get ahead of a problem, be sure to communicate with your manager if one of the following statements ever applies to you:
* "I am losing interest in social interaction." - This is especially dangerous in a remote-only setting.
* "I am losing interest in social interaction." - This is especially dangerous in an all-remote setting.
* "I've lost the motivation to work." - Everyone has days when they don't want to work
but if you hear yourself saying this often, you're on the road to burnout.
* "I feel tired often." - Indicative of being overworked for prolonged periods of time.
......
......@@ -39,8 +39,8 @@ title: People Operations Vision
## Be a preferred employer
1. Leverage brand awareness, established channels and network to promote and communicate the successes and challenges of a fully distributed model.
1. Organize a remote only conference.
1. Be globally recognized as the first and the largest remote only company and the thought leader.
1. Organize an all-remote conference.
1. Be globally recognized as the first and the largest all-remote company and the thought leader.
1. Increase recognition and distinction from competitors.
## Effective onboarding
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment