Commit b5388993 authored by John Jarvis's avatar John Jarvis

/GitLabbers/GitLab team-members/g

parent ca2323ed
......@@ -10081,7 +10081,7 @@
Based in Wellington, New Zealand, he enjoys the local coffee, reading fiction books, and watching Studio Ghibli movies. A cat person.
remote_story: |
Working with other GitLabbers around the
Working with other GitLab team-members around the
world asynchronously means that I can schedule my work around
family time, which I truly appreciate.
......
......@@ -114,7 +114,7 @@
url: https://about.gitlab.com/handbook/values/
- desc: How working at GitLab has changed my view on work and life
url: https://about.gitlab.com/2018/03/15/working-at-gitlab-affects-my-life/
- desc: GitLabbers share how to recognize burnout (and how to prevent it)
- desc: GitLab team-members share how to recognize burnout (and how to prevent it)
url: https://about.gitlab.com/2018/03/08/preventing-burnout/
- desc: GitLab & Buffer CEOs talk transparency at scale
url: https://about.gitlab.com/2017/03/14/buffer-and-gitlab-ceos-talk-transparency/
......
......@@ -52,7 +52,7 @@ extra_js:
%img.evangelist-logo{ src: "/images/evangelists/gitlab-logo.svg", alt: "GitLab logo svg" }
%p Invite a GitLab speaker to your event.
%p
= "Are you planning a tech event? We can help you find a great speaker. We have a global network of GitLabbers and community members who want to share their experience and expertise with tech meetups and conferences."
= "Are you planning a tech event? We can help you find a great speaker. We have a global network of GitLab team-members and community members who want to share their experience and expertise with tech meetups and conferences."
%a{ href: "/events/find-a-speaker/" }
Find a GitLab speaker
%i.fas.fa-arrow-right
......
......@@ -36,7 +36,7 @@ title: "Remote-work resources"
- [Transition to remote work - one month in](https://www.linkedin.com/pulse/transition-remote-work-1-month-casey-allen-shobe/)
- [Remote work, done right](https://about.gitlab.com/2018/03/16/remote-work-done-right/)
- [How working at GitLab has changed my view on work and life](https://about.gitlab.com/2018/03/15/working-at-gitlab-affects-my-life/)
- [Gitlabbers share how to recognize burnout and how to prevent it](https://about.gitlab.com/2018/03/08/preventing-burnout/)
- [GitLab team-members share how to recognize burnout and how to prevent it](https://about.gitlab.com/2018/03/08/preventing-burnout/)
- [How we stay connected as a remote company](https://about.gitlab.com/2016/12/05/how-we-stay-connected-as-a-remote-company/)
- [How to become the best distributed software development team](https://about.gitlab.com/2017/09/15/pick-your-brain-interview-kwan-lee/)
- [How to keep remote (volunteer) teams engaged](https://about.gitlab.com/2016/12/21/how-to-keep-remote-teams-engaged/)
......
......@@ -55,7 +55,7 @@ random, open-for-all channel but a conversation between two teammates.
Team members can join the #donut_be_strangers Slack channel to be paired with a random team member for a coffee chat. The "Donut" bot will automatically send a message to two people in the channel every other Monday.
Please schedule a chat together, and Donut will follow up for feedback.
Of course, you can also directly reach out to your fellow GitLabbers to schedule a coffee chat in the #donut_be_strangers Slack channel or via direct message.
Of course, you can also directly reach out to your fellow GitLab team-members to schedule a coffee chat in the #donut_be_strangers Slack channel or via direct message.
#### Coworking calls
......
......@@ -57,7 +57,7 @@ extra_js:
plan a different location for each GitLab Contribute.
Contribute is not a mandatory trip or a department offsite, nor is it a vacation or incentive trip.
It's a chance for everyone to meet fellow GitLabbers across all departments and regions:
It's a chance for everyone to meet fellow GitLab team-members across all departments and regions:
part team building, part education, part customer interaction, and hopefully all fun.
## Goal
......@@ -76,7 +76,7 @@ extra_js:
## Registering
Current GitLabbers have 1 week from signing their contract to register. Registration cuts off on May 5th. New GitLabbers who are scheduled to start in the weeks and days before Contribute will be sent communications and instructions on getting ready for Contribute, with the template found in the Employment project. New GitLabbers may purchase flights and prepare to submit reimbursement Day 1. On their first day, they may register for the event and workshops through the invitation that will have been sent to their GitLab email. Hotel rooms are being held for these new hires. They will be able to access the Contribute App to see the full schedule and information without logging in.
Current GitLab team-members have 1 week from signing their contract to register. Registration cuts off on May 5th. New GitLab team-members who are scheduled to start in the weeks and days before Contribute will be sent communications and instructions on getting ready for Contribute, with the template found in the Employment project. New GitLab team-members may purchase flights and prepare to submit reimbursement Day 1. On their first day, they may register for the event and workshops through the invitation that will have been sent to their GitLab email. Hotel rooms are being held for these new hires. They will be able to access the Contribute App to see the full schedule and information without logging in.
%section.flex-container
.full-width.column
......@@ -183,11 +183,11 @@ extra_js:
#### Team sessions/time
Most sessions can, and should, have diverse group of folks attending like GitLabbers from different teams, SOs, customers, etc. There should also be scheduled time for teams to have team-only time to discuss their work, strategize, and problem solve.
Most sessions can, and should, have diverse group of folks attending like GitLab team-members from different teams, SOs, customers, etc. There should also be scheduled time for teams to have team-only time to discuss their work, strategize, and problem solve.
1. Functional groups meet together (e.g. East Sales, Pipe-to-Spend, Site Reliability Engineering, etc.)
2. Cross-functional groups meet together (e.g. Plan, Create, Verify, etc.)
3. Customers meet together without any GitLabbers in the room to talk freely to each other.
3. Customers meet together without any GitLab team-members in the room to talk freely to each other.
%h2 Workshops
:markdown
......@@ -218,7 +218,7 @@ extra_js:
1. Presentations are one-way, one-to-many communication mode (one person speaking many people listening.)
2. One-way, one-to-many communication is easy to do remote while Unconference-style, many-to-many discussion is harder to do remote.
3. If a GitLabber has an idea for a presentation they should do this outside of Contribute (e.g. schedule a remote call, livestream or upload the recording to YouTube, link it in the training section of the handbook, etc.)
4. Customers and Users presentations are good for Contribute so that more GitLabbers can hear from our customers and experience greater customer empathy.
4. Customers and Users presentations are good for Contribute so that more GitLab team-members can hear from our customers and experience greater customer empathy.
#### Keynotes and interviews
{: #Keynotes, Interviews}
......
......@@ -13,7 +13,7 @@ title: "Leaders at Contribute"
<small>
For the context of this video, please see the [project challenges in the Greece recap](https://about.gitlab.com/2017/10/25/gitlab-summit-greece-recap/#summit-challenges)</small>
[Company leaders](/handbook/leadership/) who attend Gitlab Contribute should take the opportunity to engage with GitLabbers across the organization and should be mindful of silos and favoritism as they observe team dynamics.
[Company leaders](/handbook/leadership/) who attend Gitlab Contribute should take the opportunity to engage with GitLab team-members across the organization and should be mindful of silos and favoritism as they observe team dynamics.
### Be conscious
......
......@@ -17,13 +17,13 @@ Before we evolved to our community event - [GitLab Contribute](https://about.git
At the end of August, in 2018, our team had grown to about 320 people. Over 260 of them came to Cape Town, South Africa. We had over 85 SOs present and were also joined by a handful of customers, our advisors, and investors.
![GitLab Summit - South Africa - 2018](/images/summits/2018_south-africa_team.jpg){: .illustration}*<small>In August 2018, the whole team had grown to 320 GitLabbers!</small>*
![GitLab Summit - South Africa - 2018](/images/summits/2018_south-africa_team.jpg){: .illustration}*<small>In August 2018, the whole team had grown to 320 GitLab team-members!</small>*
### Summit in Crete, Greece
By October 2017 we had 200 team members and 65 significant others getting together in Greece to enjoy the beautiful islands of Crete and Santorini.
![The GitLab Team in October 2017](/images/summits/2017_greece_team.png){: .illustration}*<small>When October 2017 came around, the whole team already counted 200 GitLabbers!</small>*
![The GitLab Team in October 2017](/images/summits/2017_greece_team.png){: .illustration}*<small>When October 2017 came around, the whole team already counted 200 GitLab team-members!</small>*
### Summit in Cancun, Mexico
......@@ -31,7 +31,7 @@ By October 2017 we had 200 team members and 65 significant others getting togeth
In January 2017, we met in Cancun, Mexico, where roughly 150 team members and 50
significant others flew in from 35 different countries.
![The GitLab team in January 2017](/images/summits/2017_mexico_team.jpg){: .illustration}*<small>In January 2017, the whole team had grown to 150 GitLabbers!</small>*
![The GitLab team in January 2017](/images/summits/2017_mexico_team.jpg){: .illustration}*<small>In January 2017, the whole team had grown to 150 GitLab team-members!</small>*
<figure class="video_container">
<iframe src="https://www.youtube.com/embed/XDfTj8iv9qw" frameborder="0" allowfullscreen="true"> </iframe>
......@@ -46,7 +46,7 @@ awesome as they seemed on Google Hangout.
Here's some footage our team put together to show how much fun we had:
![The GitLab team in May 2016](/images/summits/2016_austin_team.jpg){: .illustration}*<small>Back in May 2016, the whole team was a total of 85 GitLabbers</small>*
![The GitLab team in May 2016](/images/summits/2016_austin_team.jpg){: .illustration}*<small>Back in May 2016, the whole team was a total of 85 GitLab team-members</small>*
<figure class="video_container">
<iframe src="https://player.vimeo.com/video/175270564" frameborder="0" allowfullscreen="true"> </iframe>
......@@ -58,7 +58,7 @@ Here's some footage our team put together to show how much fun we had:
Here are some impressions from our [second summit](/2015/11/30/gitlab-summit-2015/) in October 2015.
![The GitLab team in October 2015](/images/summits/2015_amsterdam_team.jpg){: .illustration}*<small>In October 2015, the whole team had grown to almost 30 GitLabbers!</small>*
![The GitLab team in October 2015](/images/summits/2015_amsterdam_team.jpg){: .illustration}*<small>In October 2015, the whole team had grown to almost 30 GitLab team-members!</small>*
<figure class="video_container">
<iframe src="https://www.youtube.com/embed/GJP-3BNyCXw" frameborder="0" allowfullscreen="true"> </iframe>
......
......@@ -3,7 +3,7 @@ layout: markdown_page
title: "Diversity and Inclusion"
---
![Our Global Team](/images/summits/2017_mexico_team.jpg){: .illustration}*<small>In January 2017, our team of 150 GitLabbers from around the world!</small>*
![Our Global Team](/images/summits/2017_mexico_team.jpg){: .illustration}*<small>In January 2017, our team of 150 GitLab team-members from around the world!</small>*
### Diversity and Inclusion at GitLab
......@@ -50,7 +50,7 @@ Diversity and Inclusion Goals:
* Empower employees with Employee Resource Groups
* Ensuring equal access to opportunities
* Create Diversity Team - A team of company influencers who can be instrumental in driving D&I efforts
* GitLab Safe Spaces - team wide opportunities for GitLabbers to share perspectives, concerns and different outlooks
* GitLab Safe Spaces - team wide opportunities for GitLab team-members to share perspectives, concerns and different outlooks
### Employee Training and learning opportunities
......@@ -66,11 +66,11 @@ Diversity and Inclusion Goals:
### Community
GitLabbers are distributed across the globe, giving us access to an array of opportunity. We encourage collaboration with global organizations and programs that support underrepresented individuals in the tech industry. GitLab also provides additional support through the Diversity Sponsorship program. [GitLab Diversity Sponsorship program](/community/sponsorship/). We offer funds to help support the event financially and, if the event is in a city we have a GitLab team member, we get hands-on by offering to coach and/or give a talk whenever possible.
GitLab team-members are distributed across the globe, giving us access to an array of opportunity. We encourage collaboration with global organizations and programs that support underrepresented individuals in the tech industry. GitLab also provides additional support through the Diversity Sponsorship program. [GitLab Diversity Sponsorship program](/community/sponsorship/). We offer funds to help support the event financially and, if the event is in a city we have a GitLab team member, we get hands-on by offering to coach and/or give a talk whenever possible.
### Mentorship
GitLabbers can benefit from a [mentoring program](https://docs.google.com/forms/d/e/1FAIpQLSc68PSMge0iVoDoVU19n0JycHMMkVpq55gXj59ykdJJkcM_rg/viewform) because they will contribute to the development of a better-trained and engaged community.
GitLab team-members can benefit from a [mentoring program](https://docs.google.com/forms/d/e/1FAIpQLSc68PSMge0iVoDoVU19n0JycHMMkVpq55gXj59ykdJJkcM_rg/viewform) because they will contribute to the development of a better-trained and engaged community.
Mentors will help mentees learn the ropes at the company, develop relationships across the organization and identify skills that could be strengthened.
#### Additional Training Opportunities
......
......@@ -62,7 +62,7 @@ Series A Funding was signed.
#### _October 10th, 2015_
Anniversary of our first ever summit in Amsterdam with 25 GitLabbers.
Anniversary of our first ever summit in Amsterdam with 25 GitLab team-members.
## Team Stories
......
......@@ -271,7 +271,7 @@ Here is a summary of the responses from 91 team members (57%) who participated.
1. Why are quizzes necessary?
* Quizzes reinforce that learning has occurred. When the courses were pulled from Grovo's content library, we were conscious to minimize or even eliminate this exercise for shorter courses. Confirming you understand and can apply the concepts covered is an important step in the learning process.
1. Will we have technical training for non-engineering GitLabbers?
1. Will we have technical training for non-engineering GitLab team-members?
* This is on the radar for 2017.
##### Lattice
......@@ -292,12 +292,12 @@ Here is a summary of the responses from 91 team members (57%) who participated.
Remote working environment, product development, challenge of working on the product, potential we have for
"making it big," great co-workers, the sense of a team, great culture, the feeling of being valued, personal
responsibility, willingness of GitLabbers to teach new GitLabbers, transparency, and team calls.
responsibility, willingness of GitLab team-members to teach new GitLab team-members, transparency, and team calls.
#### What you would like to change & what we are doing about it
1. Make the handbook easier to navigate.
* We have added an [Onboarding](/handbook/general-onboarding/onboarding-101/) guide for new GitLabbers. We also added Standard Operating Procedures for different departments to make what you are looking for easier to find. And don't forget, there is a search function at the top of the handbook that can help you find exactly what you are looking for! Update: This page has been moved to [Onboarding](/handbook/general-onboarding/)
* We have added an [Onboarding](/handbook/general-onboarding/onboarding-101/) guide for new GitLab team-members. We also added Standard Operating Procedures for different departments to make what you are looking for easier to find. And don't forget, there is a search function at the top of the handbook that can help you find exactly what you are looking for! Update: This page has been moved to [Onboarding](/handbook/general-onboarding/)
1. Spend more time learning the technical side of our product.
* Check out [GitLab University](https://docs.gitlab.com/ee/university/) to learn more about Git and GitLab. We will also be rolling out additional training on Git and GitLab during 2017 see [issue](https://gitlab.com/gitlab-com/peopleops/issues/126).
1. Refine the hiring process.
......@@ -306,24 +306,24 @@ responsibility, willingness of GitLabbers to teach new GitLabbers, transparency,
* Please check out our [Global Compensation Framework](/handbook/people-operations/global-compensation-framework/). If you have any questions or concerns about the compensation principles, please let People Ops know!
1. Focus on differentiating CE from EE.
* We plan to build features that are interesting for enterprises and replace existing products.
1. Focus on growth of GitLabbers within the organization.
* People Ops has instituted Grovo (individual contributor and management training), as well as Lattice (OKRs) to assist in the growth of GitLabbers within their position at GitLab. We will continue to strive to work with managers to develop GitLabbers at GitLab by drafting Professional Development Plans see [issue](https://gitlab.com/gitlab-com/peopleops/issues/170).
1. More face-to-face meetings and ability to meet up with GitLabbers close by.
* Please expense travel to visit GitLabbers as described in [Spending Company Money](/handbook/spending-company-money).
1. Focus on growth of GitLab team-members within the organization.
* People Ops has instituted Grovo (individual contributor and management training), as well as Lattice (OKRs) to assist in the growth of GitLab team-members within their position at GitLab. We will continue to strive to work with managers to develop GitLab team-members at GitLab by drafting Professional Development Plans see [issue](https://gitlab.com/gitlab-com/peopleops/issues/170).
1. More face-to-face meetings and ability to meet up with GitLab team-members close by.
* Please expense travel to visit GitLab team-members as described in [Spending Company Money](/handbook/spending-company-money).
1. Adjust the team call format to include more regular functional group updates.
* The [team call](/handbook/communication/#team-call) now has weekend updates every two weeks, a separate call for APAC GitLabbers to give their weekend update, and [functional group updates](/handbook/people-operations/group-conversations/) are separate events.
* The [team call](/handbook/communication/#team-call) now has weekend updates every two weeks, a separate call for APAC GitLab team-members to give their weekend update, and [functional group updates](/handbook/people-operations/group-conversations/) are separate events.
1. Have more employee agreements instead of contractor agreements.
* People Ops will be working to establish new entities/payrolls in more countries as we grow. Once this is completed we can transfer contractors to employees.
1. Hire in departments that need more GitLabbers.
* We understand that there is always a lot to do at GitLab and for some departments this means that we might need to hire more GitLabbers. If this is the case please communicate this to your manager and/or People Ops. If appropriate People Ops will [open the role](/handbook/hiring/#vacancy-creation-process), and add it to the [jobs page](/jobs/).
1. Hire in departments that need more GitLab team-members.
* We understand that there is always a lot to do at GitLab and for some departments this means that we might need to hire more GitLab team-members. If this is the case please communicate this to your manager and/or People Ops. If appropriate People Ops will [open the role](/handbook/hiring/#vacancy-creation-process), and add it to the [jobs page](/jobs/).
1. Refine onboarding to be less intense/intimidating.
* Onboarding can be overwhelming and sometimes confusing. To alleviate confusion about what you are doing and why, we created an [Onboarding](/handbook/general-onboarding/onboarding-101/) guide to explain each step. Update: This page has been moved to [Onboarding](/handbook/general-onboarding/).
1. Move unlimited vacation to a set amount so GitLabbers take their full vacation.
* We are taking a look at what the best option is in regards to a limited or unlimited vacation. We want to urge that GitLabbers take enough [time off](/handbook/paid-time-off) to recharge! Unlimited vacation/taking vacation is encourage at GitLab. For information on how these developments are going, check out the open [issue](https://gitlab.com/gitlab-com/www-gitlab-com/issues/952)
1. Move unlimited vacation to a set amount so GitLab team-members take their full vacation.
* We are taking a look at what the best option is in regards to a limited or unlimited vacation. We want to urge that GitLab team-members take enough [time off](/handbook/paid-time-off) to recharge! Unlimited vacation/taking vacation is encourage at GitLab. For information on how these developments are going, check out the open [issue](https://gitlab.com/gitlab-com/www-gitlab-com/issues/952)
1. Less downtime on GitLab.com.
* Our Infastructure team is always looking for new ways to improve the ownership of the things we ship. The team will look to have owners of services or features, and these services working will be the way they prove that they are actually delivering. Infrastructure has also increased uptime to 99.91% in [December 2016](http://stats.pingdom.com/81vpf8jyr1h9/1902794/2016/12).
1. Casual and social interaction.
* We have instituted [Coffee Breaks](/company/culture/all-remote/#coffee-break-calls) to promote catching up with GitLabbers. Also, all GitLabbers are just a click away on Slack or a call away on the [Random Hangout](/handbook/communication/#random-room).
* We have instituted [Coffee Breaks](/company/culture/all-remote/#coffee-break-calls) to promote catching up with GitLab team-members. Also, all GitLab team-members are just a click away on Slack or a call away on the [Random Hangout](/handbook/communication/#random-room).
1. Revise Lever Notifications.
* Sometimes it can be hard to manage Lever notifications. Here are some [guidelines](/handbook/hiring/#general-points-about-moving-applicants-through-the-process) to keep your inbox low.
......@@ -356,7 +356,7 @@ responsibility, willingness of GitLabbers to teach new GitLabbers, transparency,
1. Instructions on how to build a project on GitLab.
* Here is some [documentation](https://docs.gitlab.com/ee/gitlab-basics/create-project.html) on how to build a project within GitLab.
We also received a many responses stating we should not change or add anything, and that GitLab is an awesome place to work. This is great that GitLabbers feel this way, and People Ops will continue to strive to create a culture where GitLabbers are satisfied and engaged. Want to see where most of these changes were made? Check out the [issue](https://gitlab.com/gitlab-com/peopleops/issues/122)!
We also received a many responses stating we should not change or add anything, and that GitLab is an awesome place to work. This is great that GitLab team-members feel this way, and People Ops will continue to strive to create a culture where GitLab team-members are satisfied and engaged. Want to see where most of these changes were made? Check out the [issue](https://gitlab.com/gitlab-com/peopleops/issues/122)!
### Feedback from September 2016, and presentation of responses
......@@ -367,7 +367,7 @@ We also received a many responses stating we should not change or add anything,
#### "What do you wish we had / What are you wondering about"
1. "Contractor or employee? Worried about job security as a contractor."
* We value all GitLabbers equally, regardless of the legal arrangement that
* We value all GitLab team-members equally, regardless of the legal arrangement that
you have with GitLab. Due to legal restrictions and the difficulty of having
people be employees outside of the US or NL (where we have a legal entity), a
large portion of the team are contractors (21 out of 46). At GitLab, as everywhere
......@@ -421,7 +421,7 @@ quickly rejected as 'won't work' or 'not interested' without much explanation."
#### "What do you like about working here?"
1. A lot of love for the team
* Keywords people used to describe their fellow GitLabbers are: 'talented,
* Keywords people used to describe their fellow GitLab team-members are: 'talented,
caring, teamwork, approachable, honest, frank, smart, brilliant, skilled,
team spirit'.
1. Great product
......@@ -430,7 +430,7 @@ quickly rejected as 'won't work' or 'not interested' without much explanation."
1. Open Source
* Respondents value being involved in Open Source, with phrases such as: 'proving that open source is awesome and working with the rest of the community, working on open source while getting paid for it is a dream job!'
1. Freedom and opportunity
* We are a remote-first company and our GitLabbers like: 'being remote-first, working from home, having personal independence, the freedom to choose what to work on, the freedom that you don't get in a corporate office environment, flexibility to get things done, slim process, slack oriented'
* We are a remote-first company and our GitLab team-members like: 'being remote-first, working from home, having personal independence, the freedom to choose what to work on, the freedom that you don't get in a corporate office environment, flexibility to get things done, slim process, slack oriented'
* People also mentioned the opportunity to learn, and the massive opportunity that the project and the company has.
1. Team dynamic
* Several people mentioned that they really like the team dynamic, specifically: 'the support that you need is there, you have the ability to take on multiple hats and responsibilities, everyone and everything is open to constant improvement, ability to collaborate even though we're remote, we're remote but still have a great sense of "team", love the cross discipline collaboration that goes on every day'
......@@ -458,7 +458,7 @@ our work is public so we can talk about it, and our ability to create new proces
#### What we wish we had or what we want to be doing & What we’re doing about it
1. More GitLabbers.
1. More GitLab team-members.
* We’re hiring
1. Bigger feature gap between CE and EE.
* Current plan is to have one EE feature added per release, so over time the difference will grow.
......
......@@ -313,7 +313,7 @@ title: "Calendar Year 2018 Q1 OKRs"
* CCO-TA: Re-vamp and enhance our jobs page to help attract diverse quality talent enhance our employment brand and position ourselves as hi-tech company.
* CCO-TA: Establish level of effort metrics to ensure process efficiencies to include: recruiter screened/hiring manager review ratio, Interview/Offer ratio, and Offer Accept ratio.
* CCO: Provide consistent training to managers on how to manage effectively. Success will mean that there are at least 15 live trainings a year in addition to curated online trainings.
* CCO: Align recruiting to Functional Groups with Focus on Low Rent Regions. At least 50% of GitLabbers should be hired from a Rent Index location that less than 0.7.
* CCO: Align recruiting to Functional Groups with Focus on Low Rent Regions. At least 50% of GitLab team-members should be hired from a Rent Index location that less than 0.7.
* CCO: Implement actionable Recruiting Metrics, including the ability to track an accurate source of hire for the majority of all hires.
* CCO: Target 2 Diversity recruiting Events/sources to attend and recruit from. Measure success to determine future plan.
* CCO: Increase Employee Referrals by 5%.
......
......@@ -133,7 +133,7 @@ Some of individual contributors (without any direct reports) have manager in the
GitLab is a project bigger than GitLab the company.
It is really important that we see the community around GitLab as something that includes the people at the company.
When you refer to the community excluding the people working for the company please use: wider community.
If refer to both people at the company and outside of it use community or GitLabbers.
If refer to both people at the company and outside of it use community or GitLab team-members.
### Team and team-members
......
......@@ -99,7 +99,7 @@ Many users are interested in harmonizing epics and issues together. The want "ep
<!-- These are sourced from internal customers wanting to [dogfood](https://about.gitlab.com/handbook/product/#dogfood-everything)
the product.-->
GitLabbers also want to have flexible work breakdown structures and have more power to manipulate issues and epics together, to meet various cross-functional needs. So https://gitlab.com/groups/gitlab-org/-/epics/312 continues to be the most important improvement here.
GitLab team-members also want to have flexible work breakdown structures and have more power to manipulate issues and epics together, to meet various cross-functional needs. So https://gitlab.com/groups/gitlab-org/-/epics/312 continues to be the most important improvement here.
## Top Vision Item(s)
<!-- What's the most important thing to move your vision forward?-->
......
......@@ -72,7 +72,7 @@ So [Group board with custom workflow](https://gitlab.com/groups/gitlab-org/-/epi
<!-- These are sourced from internal customers wanting to [dogfood](https://about.gitlab.com/handbook/product/#dogfood-everything)
the product.-->
GitLabbers want more flexibility to do even more with boards. In particular, GitLabbers really want to take advantage of epics integrated in boards.
GitLab team-members want more flexibility to do even more with boards. In particular, GitLab team-members really want to take advantage of epics integrated in boards.
[Epic swimlanes](https://gitlab.com/groups/gitlab-org/-/epics/328) are thus crucial here.
## Top Vision Item(s)
......
......@@ -63,7 +63,7 @@ Similar to above, we need to figure out the requirements structure - see epic [h
<!-- These are sourced from internal customers wanting to [dogfood](https://about.gitlab.com/handbook/product/#dogfood-everything)
the product.-->
Currently, GitLabbers are not considering using Requirements Management.
Currently, GitLab team-members are not considering using Requirements Management.
## Top Vision Item(s)
<!-- What's the most important thing to move your vision forward?-->
......
......@@ -55,7 +55,7 @@ Automatically labeling issues is popular with users. See [Automatically label Se
<!-- These are sourced from internal customers wanting to [dogfood](https://about.gitlab.com/handbook/product/#dogfood-everything)
the product.-->
GitLabbers have found it difficult to use Service Desk since it is not powerful enough to do so currently. The legal team is using Service Desk and they are interested in [these issues](https://gitlab.com/groups/gitlab-org/-/issues?scope=all&utf8=%E2%9C%93&state=opened&label_name%5B%5D=Service%20Desk&author_username=jhurewitz).
GitLab team-members have found it difficult to use Service Desk since it is not powerful enough to do so currently. The legal team is using Service Desk and they are interested in [these issues](https://gitlab.com/groups/gitlab-org/-/issues?scope=all&utf8=%E2%9C%93&state=opened&label_name%5B%5D=Service%20Desk&author_username=jhurewitz).
We have engaged with the GitLab Support Team (Lee M in particular) in the past to ask if they can adopt Service Desk. Unfortunately, we haven't had enough bandwidth to support incremental improvements to make this realistic. As we scale our product development teams and can prioritize Service Desk again, a pivotal goal will be re-engage the GitLab Support Team and establish a list of issues/features they need to use GitLab Service Desk and work together on a migration plan to help them eventually move off of Zendesk.
......
......@@ -226,9 +226,9 @@ effort to identify and plan changes in upcoming milestones (monthly iterations).
and [upcoming planned improvements in detail](https://gitlab.com/groups/gitlab-org/-/boards/706864)
for the next few milestones (monthly releases).
All GitLabbers use Plan features, more so than other GitLab stages, so it's important
All GitLab team-members use Plan features, more so than other GitLab stages, so it's important
we are continuing to support GitLabber workflows and prioritizing them.
[See issues scheduled for the next few milestones that directly benefit GitLabbers.](https://gitlab.com/groups/gitlab-org/-/boards/1003901)
[See issues scheduled for the next few milestones that directly benefit GitLab team-members.](https://gitlab.com/groups/gitlab-org/-/boards/1003901)
## How we execute week to week
......
......@@ -58,7 +58,7 @@ title: Handbook Changelog
- [!23196](https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/23196) Trying to Fix Minor territory tables 2 + Adding 2 More Minor Cuts
- [!23195](https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/23195) Removing location factor link
- [!23190](https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/23190) Update source/handbook/general-guidelines/index.html.md
- [!23137](https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/23137) Add baseline entitlements for all GitLabbers
- [!23137](https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/23137) Add baseline entitlements for all GitLab team-members
### 2019-05-24
- [!23204](https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/23204) Update snowflake user provisioning
......
......@@ -58,24 +58,24 @@ We value opinions but ultimately People Operations/Leadership will make the deci
For the avoidance of doubt, the benefits listed below in the General Benefits section are available to contractors and employees, unless otherwise stated. Other benefits are listed by countries that GitLab has established an entity or co-employer and therefore are applicable to employees in those countries only. GitLab has also made provisions for Parental Leave which may apply to employees and contractors but this may vary depending on local country laws. If you are unsure please reach out to the People Operations team.
1. GitLab will pay for the items listed under [spending company money](/handbook/spending-company-money).
1. [Stock options](/handbook/stock-options/) are offered to most GitLabbers.
1. [Stock options](/handbook/stock-options/) are offered to most GitLab team-members.
1. Deceased team member:
In the unfortunate event that a GitLab team member passes away, GitLab will
provide a [$20,000](/handbook/people-operations/global-compensation/#exchange-rates) lump sum to anyone of their choosing. This can be a spouse,
partner, family member, friend, or charity.
* For US based employees of GitLab Inc., this benefit is replaced by the
[Basic Life Insurance](/handbook/benefits/inc-benefits-us/#basic-life-insurance-and-add).
* For all other GitLabbers, the following conditions apply:
* For all other GitLab team-members, the following conditions apply:
* The team member must be either an employee or direct contractor.
* The team member must have indicated in writing to whom the money
should be transferred. To do this you must complete this [expression of wishes](https://docs.google.com/document/d/1bBX6Mn5JhYuQpCXgM4mkx1BbTit59l0hD2WQiY7Or9E/edit?usp=sharing) form, email to People Ops, who will then file in BambooHR.
* For part-time GitLabbers, the lump sum is calculated pro-rata, so
* For part-time GitLab team-members, the lump sum is calculated pro-rata, so
for example for a team member that works for GitLab 50% of the time,
the lump sum would be [$10,000](/handbook/people-operations/global-compensation/#exchange-rates).
1. [Paid time off policy](/handbook/paid-time-off)
1. [Tuition Reimbursement](/handbook/people-operations/code-of-conduct/#tuition-reimbursement)
1. [GitLab Contribute](/company/culture/contribute)
* Every nine months or so GitLabbers gather at an exciting new location to [stay connected](/2016/12/05/how-we-stay-connected-as-a-remote-company/), at what we like to call GitLab Contribute. It is important to spend time face to face to get to know your team and, if possible, meet everyone who has also bought into the company vision. There are fun activities planned by our GitLab Contribute Experts, work time, and presentations from different functional groups to make this an experience that you are unlikely to forget! Attendance is optional, but encouraged. For more information and compilations of our past events check out our [previous Contributes (formerly called GitLab Summit)](/company/culture/contribute/previous).
* Every nine months or so GitLab team-members gather at an exciting new location to [stay connected](/2016/12/05/how-we-stay-connected-as-a-remote-company/), at what we like to call GitLab Contribute. It is important to spend time face to face to get to know your team and, if possible, meet everyone who has also bought into the company vision. There are fun activities planned by our GitLab Contribute Experts, work time, and presentations from different functional groups to make this an experience that you are unlikely to forget! Attendance is optional, but encouraged. For more information and compilations of our past events check out our [previous Contributes (formerly called GitLab Summit)](/company/culture/contribute/previous).
1. [Business Travel Accident Policy](https://drive.google.com/a/gitlab.com/file/d/0B4eFM43gu7VPVl9rYW4tXzIyeUlMR0hidWIzNk1sZjJyLUhB/view?usp=sharing)
* This policy provides coverage for team members who travel domestic and internationally for business purposes. This policy will provide Emergency Medical and Life Insurance coverage should an emergency happen while you are traveling. In accompaniment, there is coverage for security evacuations, as well a travel assistance line which helps with pre-trip planning and finding contracted facilities worldwide.
* Coverage:
......@@ -106,9 +106,9 @@ on that page._
## Parental Leave
Anyone (regardless of gender) at GitLab who becomes a parent through childbirth or adoption is able to take fully paid parental leave. GitLabbers will be encouraged to decide for themselves the appropriate amount of time to take and how to take it. We will offer everyone who has been at GitLab for a year up to 12 weeks of 100% paid time off during the first year of parenthood. We encourage parents to take 8-12 weeks.
Anyone (regardless of gender) at GitLab who becomes a parent through childbirth or adoption is able to take fully paid parental leave. GitLab team-members will be encouraged to decide for themselves the appropriate amount of time to take and how to take it. We will offer everyone who has been at GitLab for a year up to 12 weeks of 100% paid time off during the first year of parenthood. We encourage parents to take 8-12 weeks.
For many reasons, a team member may require more time off for parental leave. Many GitLabbers are from countries that have longer standard parental leaves, occasionally births have complications, and sometimes 12 weeks just isn't enough. Any GitLabber can request additional unpaid parental leave, up to 4 weeks. We are happy to address anyone with additional leave requests on a one-on-one basis. All of the parental leave should be taken in the first year.
For many reasons, a team member may require more time off for parental leave. Many GitLab team-members are from countries that have longer standard parental leaves, occasionally births have complications, and sometimes 12 weeks just isn't enough. Any GitLabber can request additional unpaid parental leave, up to 4 weeks. We are happy to address anyone with additional leave requests on a one-on-one basis. All of the parental leave should be taken in the first year.
If you have been at GitLab for a year your parental leave is fully paid. If you've been at GitLab for less than a year it depends on your jurisdiction. If applicale, commissions are paid while on parental leave based on the prior six months of performance with a cap at 100% of plan. For example, if in the six months prior to starting parental leave you attained 85% of plan, you will be compensated at the same rate while on leave. On the day you return from leave and going forward, your commissions will be based on current performance only.
......
......@@ -206,7 +206,7 @@ This helps verify that numbers are accurate and the original data source and the
##### Work
This umbrella term helps capture:
* inbound requests from GitLabbers that usually materialize into a dashboard
* inbound requests from GitLab team-members that usually materialize into a dashboard
* housekeeping improvements/technical debt from the data team
* goals of the data team
* documentation notes
......
......@@ -290,7 +290,7 @@ System owners will remain the point of contact for provisioning and issues invol
</tr>
<tr>
<td><strong><a href="/handbook/business-ops/tech-stack/#periscope">Periscope</a></strong></td>
<td>All GitLabbers</td>
<td>All GitLab team-members</td>
<td><strong>Taylor Murphy (primary)</strong><br>Emilie Schario<br></td>
<td>Taylor Murphy</td>
</tr>
......
......@@ -114,7 +114,7 @@ Should a laptop not be available to a new Gitlabber upon their start date, but i
GitLab approves the use of Apple and Linux operating systems, Windows is prohibited.
Apple hardware is the common choice for most GitLabbers, but if you are comfortable using and self-supporting yourself with Linux (Ubuntu usually) you may also choose from the Dell builds below.
Apple hardware is the common choice for most GitLab team-members, but if you are comfortable using and self-supporting yourself with Linux (Ubuntu usually) you may also choose from the Dell builds below.
Apple Hardware
......
......@@ -41,7 +41,7 @@ GitLab is using Okta for a few key goals :
GitLab is running an Open Beta through April and May 2019 - please sign up using [the Okta Beta signup form](https://forms.gle/6YHwYveJRipygS5r9).
After May 2019, all GitLabbers will have an Okta account set up as part of their onboarding process.
After May 2019, all GitLab team-members will have an Okta account set up as part of their onboarding process.
Follow the GitLab Okta [Getting Started Guide](https://docs.google.com/document/d/1x2NJan0job5nM5tT8HF6yofg-Y2aAsSVKc6qNnCuoxo/) and [FAQs](https://docs.google.com/document/d/1fRiWDmZd3BNu7dkr40h0eAWtE1KW5TifPRYXXUKh2a0/).
......
......@@ -10,7 +10,7 @@ title: "Business Operations - Salesforce Reference"
{:toc}
## Purpose
The purpose of this page is to provide insight into the internal workings of our Salesforce (SFDC) instance, how fields are populated, how fields are calculated, where they are used etc. This page does not serve to describe how the systems should be used by our internal stake holders. Instead it is meant to be used as a reference point for continual development by our internal ops teams as well as a reference point for all Gitlabbers as to the source of the information that is shown within SFDC. The goal of this document is not to document every field that exists within SFDC but instead to highlight the hidden process that affect fields that meet 1 or more of the following criteria
The purpose of this page is to provide insight into the internal workings of our Salesforce (SFDC) instance, how fields are populated, how fields are calculated, where they are used etc. This page does not serve to describe how the systems should be used by our internal stake holders. Instead it is meant to be used as a reference point for continual development by our internal ops teams as well as a reference point for all GitLab team-members as to the source of the information that is shown within SFDC. The goal of this document is not to document every field that exists within SFDC but instead to highlight the hidden process that affect fields that meet 1 or more of the following criteria
1. The main fields that are leveraged by the teams (Ex: IACV)
1. Fields that are updated via automation rules (Ex: Sales Segmentation)
......
......@@ -217,7 +217,7 @@ As such there are [sending limits built into the Outreach platform](https://supp
[Okta](https://about.gitlab.com/handbook/business-ops/okta/) is an Identity and Single Sign On solution for applications and Cloud entities. It allows GitLab to consolidate authentication and authorisation to Applications we use daily through a single dashboard and ensure a consistent, secure and auditable login experience for all our staff.
## Periscope
[Periscope](https://www.periscopedata.com/) is our Data Visualization and Business Intelligence tool. It is for reporting and can have its dashboards embedded into Salesforce, the Handbook, or other places where GitLabbers already do their work. Please read more in the [Periscope Directory](/handbook/business-ops/data-team/periscope-directory/)
[Periscope](https://www.periscopedata.com/) is our Data Visualization and Business Intelligence tool. It is for reporting and can have its dashboards embedded into Salesforce, the Handbook, or other places where GitLab team-members already do their work. Please read more in the [Periscope Directory](/handbook/business-ops/data-team/periscope-directory/)
## Salesforce
[Salesforce](https://www.salesforce.com/) is our CRM of record. It integrates with all of the other applications in our business tech stack. Salesforce stores prospect, customer, and partner information. This includes contact information, products purchased, bookings, support tickets, and invoices, among other information.
......
......@@ -244,7 +244,7 @@ The wireless mouse and keyboard are connected to the middle, bottom TV by defaul
In preparation for guests (customers, investors, etc.) who will be meeting with Sid at the Boardroom, please note the following prior to the meeting start:
1. All Gitlabbers sit on one side. This allows for easy communication to the guests
1. All GitLab team-members sit on one side. This allows for easy communication to the guests
1. Have drinks available on table (from the fridge)
## What is it like?
......
......@@ -15,7 +15,7 @@ title: "Ally resources"
## How to be an ally
It is not required to be an ally to work at GitLab. At GitLab it is required to [be inclusive](https://about.gitlab.com/handbook/values/#diversity). Being an ally goes a step beyond being inclusive to taking action to support marginalized groups. The first step in being an ally is self-educating. This is a page to list resources that GitLabbers have found helpful in learning how to act as an ally.
It is not required to be an ally to work at GitLab. At GitLab it is required to [be inclusive](https://about.gitlab.com/handbook/values/#diversity). Being an ally goes a step beyond being inclusive to taking action to support marginalized groups. The first step in being an ally is self-educating. This is a page to list resources that GitLab team-members have found helpful in learning how to act as an ally.
## Resources
......
......@@ -14,7 +14,7 @@ extra_js:
{:toc}
## Introduction
At GitLab, Slack is critical to our communication with each other. While it enables real-time communication, we also are careful to remain true to our asynchronous mindset, suggesting that GitLabbers set "do not disturb" and not expect real-time answers from others all the time.
At GitLab, Slack is critical to our communication with each other. While it enables real-time communication, we also are careful to remain true to our asynchronous mindset, suggesting that GitLab team-members set "do not disturb" and not expect real-time answers from others all the time.
There are groups of channels that can help with various areas of GitLab. This page speaks to a few subsets of those channel groups.
......@@ -26,8 +26,8 @@ There are a lot of general channels, just to name a few:
* **[`#company-announcements`](https://gitlab.slack.com/archives/general)**: General announcements and company-wide broadcasts
* **[`#questions`](https://gitlab.slack.com/archives/questions)**: Ask all of GitLab for help with any question you have... and then go document it after you find the answer :)
* **[`#thanks`](https://gitlab.slack.com/archives/thanks)**: Where GitLabbers can [say thanks](/handbook/communication/#say-thanks) to those GitLabbers who did a great job, helped a customer, or helped you!
* **[`#random`](https://gitlab.slack.com/archives/random)**: Socialize and share random snippets with your fellow GitLabbers.