Commit 7ee47d1e authored by Takuya Noguchi's avatar Takuya Noguchi 🇯🇵

Eliminate duplicated words

Signed-off-by: Takuya Noguchi's avatarTakuya Noguchi <takninnovationresearch@gmail.com>
parent 6aa8d43f
......@@ -5042,7 +5042,7 @@ features:
description: |
Connect your projects hosted on GitHub and leverage
the power of GitLab CI/CD pipelines to build, test, and deploy your applications easily.
link_description: "Learn more about CI/CD for for GitHub"
link_description: "Learn more about CI/CD for GitHub"
link: /solutions/github/
screenshot_url: 'images/feature_page/screenshots/cicd_project.png'
category:
......
......@@ -57,7 +57,7 @@
- name: Cowboy Jake & Lucy Lulu
picture: jakeandlucy.jpg
human: brittany
story: Cowboy Jake loves to to cuddle, bark at stuff, but mostly swim. Lucy Lulu loves to lay on the couch, watch TV, and bug Cowboy Jake.
story: Cowboy Jake loves to cuddle, bark at stuff, but mostly swim. Lucy Lulu loves to lay on the couch, watch TV, and bug Cowboy Jake.
- name: Roshi
picture: roshi.jpg
human: jared
......
......@@ -43,7 +43,7 @@ self_managed:
answer: |
Yes. You have a few options. You can add users to your subscription any time during the subscription period. You can log in to your account via the
<a href="https://customers.gitlab.com">GitLab Customer Portal</a> and add more seats or by either contacting <a href="mailto:renewals@gitlab.com">renewals@gitlab.com</a> for a quote. In either case,
the cost will be prorated from the date of quote/purchase through the end end of the subscription period. You may also pay for the additional licences per
the cost will be prorated from the date of quote/purchase through the end of the subscription period. You may also pay for the additional licences per
our true-up model.
- question: The True-Up model seems complicated, can you illustrate?
answer: |
......
......@@ -232,7 +232,7 @@ features:
your limitations and lets you act within them or request escalated privileges when appropriate.
Now you can see your permission level on the GitLab Project Dashboard next
to the project name. You no longer have have to click into each project and
to the project name. You no longer have to click into each project and
dig into the users page to find this info.
- name: 'Customize "New Project" page'
......
......@@ -197,7 +197,7 @@ features:
In GitLab 10.5 we added the ability to [include external CI/CD configuration files](https://about.gitlab.com/2018/02/22/gitlab-10-5-released/#include-external-files-in-cicd-pipeline-definition)
into the main `.gitlab-ci.yml` for your project. This feature was available only to Premium users on self-hosted Gitlab and Silver users on GitLab.com.
We received a lot of feedback from customers asking us to move this to to a lower tier and we are excited
We received a lot of feedback from customers asking us to move this to a lower tier and we are excited
to bring this feature to even more users in this release by making it now availabe to Starter users on self-hosted Gitlab and Bronze users on GitLab.com.
The ability to have a centralized control over the pipeline configuration
and to reuse the same definition in multiple projects is something that is valuable for enterprises and smaller businesses as well.
......
......@@ -37,7 +37,7 @@ features:
software, and you can now check the CI status of the current commit
at a glance by checking the status bar at the bottom left of the Web IDE. Even
better, you can view the status of each job and the logs for each job
on the right. This makes makes it easy to fix a merge request with CI
on the right. This makes it easy to fix a merge request with CI
failures by opening the failed job side by side with the file you're
working on.
......
......@@ -5194,7 +5194,7 @@
departments:
- Marketing
story: |
Antonio is a passionate marketer and is well known for his talent to to connect people with brands, products and services. In his free time he likes to learn something new every day and to produce music.
Antonio is a passionate marketer and is well known for his talent to connect people with brands, products and services. In his free time he likes to learn something new every day and to produce music.
- slug: john-jeremiah
type: person
......@@ -8736,7 +8736,7 @@
- Engineering
- Support
story: |
David is a a software developer with a passion for backend engineering,
David is a software developer with a passion for backend engineering,
automation, learning and teaching others. Prior to GitLab, he worked in
several roles ranging from front-line support to infrastructure engineering. In
his free time, he likes to code/develop (primarily in Ruby and Go), cook,
......
......@@ -122,7 +122,7 @@ How do we manage our entire [team](/company/team/) remotely? Sid Sijbrandij, CEO
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 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.
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 on-site organic approach fizzles out.
We have had success bonding with our coworkers in real life through our [Summits](/company/culture/contribute/) that are organized every 9 months and our [Visiting Grants](/handbook/incentives/#sts=Visiting grant).
......
......@@ -73,7 +73,7 @@ Our plan is to become the most popular tool for people’s own git hosting servi
## How open source benefits from open core
GitLab Inc. has an open core business model that includes source-available code and selling subscriptions.
This benfits the the open source part of GitLab in the following ways:
This benfits the open source part of GitLab in the following ways:
1. New features being made by GitLab Inc. that are open source
1. [Responsible disclosure](/security/disclosure/) process and security fixes
......
......@@ -36,7 +36,7 @@ The executive layer is structured as follows. There are two primary processes, p
## Manager in title doesn't imply manager in structure
Some of individual contributors (without any direct reports) have manager in their title but are not considered a manager in our company structure structure nor salary calculator, examples are product manager, accounting manager, account manager, channel sales manager, technical account manager, field marketing managers, online marketing manager, and product marketing manager.
Some of individual contributors (without any direct reports) have manager in their title but are not considered a manager in our company structure nor salary calculator, examples are product manager, accounting manager, account manager, channel sales manager, technical account manager, field marketing managers, online marketing manager, and product marketing manager.
## Wider community
......
......@@ -62,4 +62,4 @@ extra_css:
%div
%h2 Questions from visitors
%p
Most visitors have questions about our #{link_to "team size and distribution", "/company/team"}, how people are #{link_to 'spread among departments', "/company/team/org-chart/"}, our #{link_to "strategy", "/company/strategy/"}, and other things for which it helps to have a quick walk through through our #{link_to "handbook", "/handbook"} and general pages mentioned on our #{link_to "About page", "/about"}
Most visitors have questions about our #{link_to "team size and distribution", "/company/team"}, how people are #{link_to 'spread among departments', "/company/team/org-chart/"}, our #{link_to "strategy", "/company/strategy/"}, and other things for which it helps to have a quick walk through our #{link_to "handbook", "/handbook"} and general pages mentioned on our #{link_to "About page", "/about"}
......@@ -76,7 +76,7 @@ SheetLoad is the process by which a GoogleSheet can be ingested into the data wa
How to use SheetLoad
1. Add file to [SheetLoad Google Drive Folder](https://drive.google.com/drive/u/0/folders/1F5jKClNEsQstngbrh3UYVzoHAqPTf-l0) with appropriate naming convention, described below
2. Share the sheet with with the SheetLoader runner => Doc with email ([GitLab internal](https://docs.google.com/document/d/1m8kky3DPv2yvH63W4NDYFURrhUwRiMKHI-himxn1r7k/edit))
2. Share the sheet with the SheetLoader runner => Doc with email ([GitLab internal](https://docs.google.com/document/d/1m8kky3DPv2yvH63W4NDYFURrhUwRiMKHI-himxn1r7k/edit))
3. Add the full file name to the [`extract-ci.yml`](https://gitlab.com/meltano/analytics/blob/master/extract/extract-ci.yml#L90) file
4. Create dbt base models
5. Add to [data quality test](https://gitlab.com/meltano/analytics/tree/master/transform/cloudsql-dbt/tests) that helps ensure these files are updated monthly.
......
......@@ -1472,12 +1472,12 @@ There are three things that can be new or existing:
- Subscription (linked to a GitLab instance)
- Amount (dollars paid for the subscription)
That gives 4 types of of opportunities:
That gives 4 types of opportunities:
1. New account (new account, new subscription, new amount) This type should be used for any new subscription who signs up either through the sales team or via the web portal. Paid training also falls under this type if the organization does not have an enterprise license.
1. New subscription (existing account, new subscription, new amount) If an existing account is purchasing a new license for another GitLab instance, this will be new business.
1. Add-on business (existing account, existing subscription, new amount) This type should be used for any incremental/upsell business sold into an existing subscription division mid term, meaning not at renewal. This may be additional seats for their subscription or an upgrade to their plan. If an existing account is adding a new subscription, this would be new business, not an add-on.
1. Renewal (existing subscription, existing subscription, existing amount) This type should be used for an existing account renewing their license with GitLab. Renewals can have their value increased, decreased, or stay the same. We capture incremental annual contract value growth/loss as a field in Salesforce.com. Renewal business can be a negative amount if renewed at less than the previous dollars paid for the subscription (renewal rate). Only the part that is more or less than the old amount is IACV, the rest is part of the the renewal opportunity.
1. Renewal (existing subscription, existing subscription, existing amount) This type should be used for an existing account renewing their license with GitLab. Renewals can have their value increased, decreased, or stay the same. We capture incremental annual contract value growth/loss as a field in Salesforce.com. Renewal business can be a negative amount if renewed at less than the previous dollars paid for the subscription (renewal rate). Only the part that is more or less than the old amount is IACV, the rest is part of the renewal opportunity.
**New business** is the combination of new account and new subscription
......
......@@ -467,7 +467,7 @@ If the customer wishes to change the contacts for either the license (Sold To Co
### Zuora Supporting 4 types of Amendments –
1. Terms and Conditions amendment – The sales rep will be able to change the terms and conditions of an existing subscription;
1. Remove product Amendment – The sales rep will be be able to perform a Remove a product Amendment;
1. Remove product Amendment – The sales rep will be able to perform a Remove a product Amendment;
* In this case, sales rep will have to Set the Start date (Contract effective date in Zuora terms) when the remove product amendment should happen
* Click on Next
* This will take them to the product selector page and displays the original product that was purchased within the subscription
......
......@@ -14,7 +14,7 @@ title: "Account Planning Objects in Salesforce"
**Note:** The Account Plan object is currently in a testing phase now with the US East Team. Updates will be provided as this object is rolled out to the rest of the sales team.
## Account Plan
The Account Plan object in Salesforce is used to document the strategy around selling to a strategic prospect or customer account. Here, you will enter the the plan status, IACV bookings goals, notes, any business or technical problems that you plan to highlight, the solutions or goals that you plan to present, the GitLab strengths that you plan to leverage, and finally any potential barriers you foresee with this account.
The Account Plan object in Salesforce is used to document the strategy around selling to a strategic prospect or customer account. Here, you will enter the plan status, IACV bookings goals, notes, any business or technical problems that you plan to highlight, the solutions or goals that you plan to present, the GitLab strengths that you plan to leverage, and finally any potential barriers you foresee with this account.
### Components of an Account Plan
Once you've added this information to the Account Plan object, you will then start to add various components related to the account plan, such as the Team, Key Contacts, and the Opportunities.
......
......@@ -95,7 +95,7 @@ As [Stripe documented](https://stripe.com/atlas/guides/business-of-saas#hybrid-s
## Combining features in plans
We tried selling one feature at a time but this was was not feasible.
We tried selling one feature at a time but this was not feasible.
An improved version of that would be selling 7 main features instead of 3 plans.
Examples of main features would be High Availability, Security, Service Desk, etc.
......@@ -162,7 +162,7 @@ Arguments to at least make them equal:
1. Self-managed pricing in general tends to be higher.
1. There is more market demand for self-managed.
1. No incentive for sales to sell SaaS over self-managed.
1. Self-managed tends be be a better experience.
1. Self-managed tends to be a better experience.
1. We want to incentivize customers to move to SaaS with us.
Not sure what is normal in the market, Adobe did a good job but they moved from perpetual licensing to subcriptions but it is hard to [compare the two prices](http://blogs.adobe.com/acrolaw/2015/05/a-new-way-to-buy-acrobat-dc-subscription/).
......
......@@ -90,7 +90,7 @@ members:
1. They don't have a subject, so everyone has to remember the topic of each private group based on the participants, or open the group again to read the content.
1. History is lost when leaving the group.
1. It is perfectly fine to create a channel, even for a single customer meeting. These channels should be named "a_<customer-name>-internal" to indicate their "internal" nature (not shared with customers).
1. Use [low-context communications](https://en.wikipedia.org/wiki/High-context_and_low-context_cultures) by being explicit in your communications. We are are a remote-only company, located all over the world. Provide as much context as possible to avoid confusion. For example, consider introducing yourself and your function when addressing the company during the company call, since not everyone may know who you are. Relatedly, we use [ubiquitous language](#ubiquitous-language) for communication efficiency.
1. Use [low-context communications](https://en.wikipedia.org/wiki/High-context_and_low-context_cultures) by being explicit in your communications. We are a remote-only company, located all over the world. Provide as much context as possible to avoid confusion. For example, consider introducing yourself and your function when addressing the company during the company call, since not everyone may know who you are. Relatedly, we use [ubiquitous language](#ubiquitous-language) for communication efficiency.
### Asking "is this known"
......@@ -167,7 +167,7 @@ This also helps prevent spam from people outside GitLab requesting access to a d
1. Add 'Deprecated: ' to the start of the title.
1. Remove the content you moved.
1. Add a link to the the new location at the beginning of the doc/first slide/first tab.
1. Add a link to the new location at the beginning of the doc/first slide/first tab.
1. Add a link to the merge request or commit that moved it (if applicable).
## Presentations
......
......@@ -38,7 +38,7 @@ There are two roles assigned to account coverage - Account Manager (AM) and [Tec
4. **Education** — (20-30 days) Create a task in Salesforce for product education. Remind your customer that our releases are on the 22nd of each month per our [Direction](/direction/). Depending on your timing of this correspondence you may inform them of any major enhancements that have been released or are about to be released.
5. **Discovery** — (60 days) Now that your customer has had some time and experience using GitLab, set out to discover the need for GitLab commercial features and functionality ([Bronze, Silver, Gold, Starter, Premium, and Ultimate](/pricing/)) by running through [Sales Qualification Questions](/handbook/sales-qualification-questions/).
6. **Check-in** — (90 days) Create a task in salesforce for check-in with customer. Ask if the customer has any outstanding issues. Do they have any feature requests? This is also an opportunity to identify if there has been any changes in the organization, or an opportunity for further user adoption for their goals. For a status check, also identify that key decision makers and license contacts are still current.
7. **Outlook** — (6 months) Same as 90 day Check-in task, additionally discuss what the customer roadmap and outlook looks like for the next 6 months. What can we expect in terms terms of growth, what does the customer expect in terms of our product and offerings.
7. **Outlook** — (6 months) Same as 90 day Check-in task, additionally discuss what the customer roadmap and outlook looks like for the next 6 months. What can we expect in terms of growth, what does the customer expect in terms of our product and offerings.
8. **Renewal/Expansion** — (10 months) Check in with the customer and let them know they are soon due for renewal. Are there any changes to who is responsible for the renewal or otherwise? Good time to ask about their team growth to see if they need more seats. Good time to educate and develop need for GitLab Products.
9. **Renewal** — (11 months) Check in with the customer if they have not yet renewed, if there are any blockers to renewal or any changes to expect.
10. **Renewal** — (12 months) Follow up with the customer, if we have lost their renewal discover the reasons why we did not succeed and if any changes can be made or improved. If they have moved to another solution, which and why?
......
......@@ -139,7 +139,7 @@ In order to evangelize and grow the use of GitLab in existing accounts, the [Opt
* [Account Planning Template for Large/Strategic Accounts](https://docs.google.com/presentation/d/1yQ6W7I30I4gW5Vi-TURIz8ZxnmL88uksCl0u9oyRrew/edit?ts=58b89146#slide=id.g1c9fcf1d5b_0_24))
* [Sales Demo](/handbook/marketing/product-marketing/demo/)
* [Sales Development Group Handbook](/handbook/sales/sdr)
* [Who to go to to ask Questions or Give Feedback on a GitLab feature](/handbook/product/#who-to-talk-to-for-what)
* [Who to go to ask Questions or Give Feedback on a GitLab feature](/handbook/product/#who-to-talk-to-for-what)
* [CEO Preferences when speaking with prospects and customers](/handbook/people-operations/ceo-preferences/#sales-meetings)
### Customer Success & Market Segmentation
......
......@@ -86,11 +86,11 @@ In order to appropriately track and create Executive Business Review Objects ple
* If it is the first EBR for an account you can navigate to the EBR Tab. This can be located on the either the 'Sales' or the 'Service' App within Salesforce
* On the top of the list shown, you click on the 'New' button. This will enable you to create the new EBR object where you can provide the following. `Executive Business Review Name` is the name that you give this EBR. Select the `EBR Date` that the EBR is scheduled to occur on.
Note: If the EBR Date changes, please see below for handling this situation in order relate the EBR to the appropriate account. This is done using the search functionality provided by the `Account` field. `EBR Status` should be set to either 'Not Started' or 'Scheduled' depending on the current state of the EBR. All other fields should be left alone. Please refer to the section below on if you should link the EBR to any Opportunities.
Note: If the EBR Date changes, please see below for handling this situation in order relate the EBR to the appropriate account. This is done using the search functionality provided by the `Account` field. `EBR Status` should be set to either 'Not Started' or 'Scheduled' depending on the current state of the EBR. All other fields should be left alone. Please refer to the section below on if you should link the EBR to any Opportunities.
#### Creating any successive EBR's and handling "Declined" or "Cancelled" EBR's
* In order to create any successive EBR's (anything besides the first EBR), DO NOT us the the 'New' button as this will cause errors with tracking. Instead, after the completion, cancellation or declined invite of an EBR, update the `EBR Success` to the appropriate value. This will automatically create the next EBR for the account 90 days after the `EBR Date` for the current EBR (ensuring that there is one EBR per quarter).
* In order to create any successive EBR's (anything besides the first EBR), DO NOT us the 'New' button as this will cause errors with tracking. Instead, after the completion, cancellation or declined invite of an EBR, update the `EBR Success` to the appropriate value. This will automatically create the next EBR for the account 90 days after the `EBR Date` for the current EBR (ensuring that there is one EBR per quarter).
A number of fields will also auto populate making the creation process of new EBR's much more efficient.
......
......@@ -47,7 +47,7 @@ We are not simply runnig GitLab.com: we are also building a team we love to work
put it](https://www.quietrev.com/powerful-building-culture-freedom-responsibility/), we want to create a team where
"Oh, I’d want to come to work every day and solve *these* problems with *these* people".
There are three cultural aspects to focus on as we continue to to develop and polish the team:
There are three cultural aspects to focus on as we continue to develop and polish the team:
* Focus on **observable availability** at every turn and watch each other's back. Read and embrace Richard Cook’s
seminal paper
......
......@@ -452,6 +452,6 @@ is reached it will block pgbouncer connections until a PostgreSQL connection bec
cost of having more servers).
- Analogy: pgbouncer is a bartender serving drinks to many customers. Instead of making the drinks himself she instructs 1 out of 20 “backend” bartenders to do so. While one of these bartenders is working on a drink the other 19 (including the “main” one) are available for new orders. Once a drink is done one of the 20 “backend” bartenders gives it to the main bartender, which in turn gives it to the customer that requested the drink. In this analogy, the _N_ incoming connections are the patrons of the bar, and there are _M_ "backend"
bartenders.
- Pgbouncer frontend connections (= incoming ones) are very cheap, and you have have lots of these (e.g. thousands). Typically you want _N_ >= _A_ with _N_ being the pgbouncer connection limit, and _A_ being the number of connections needed for your application.
- Pgbouncer frontend connections (= incoming ones) are very cheap, and you have lots of these (e.g. thousands). Typically you want _N_ >= _A_ with _N_ being the pgbouncer connection limit, and _A_ being the number of connections needed for your application.
- PostgreSQL connections are much more expensive resource wise, and ideally you have no more than the number of CPU cores available per server (e.g. 32). Depending on your load this may not always be sufficient, e.g. a primary in our setup will need to allow 100-150 connections at peak.
- Pgbouncer can be configured to terminate PostgreSQL connections when idle for a certain time period, conserving resources.
......@@ -156,7 +156,7 @@ We work closely with bounty programs, as well as security assessment and penetra
- [@gitlab-com/gl-security](https://gitlab.com/gitlab-com/gl-security/) is the primary group for @'mentioning the Security Department.
- [public (!) Security Engineering](https://gitlab.com/gitlab-com/gl-security/engineering/) for Security Department initiatives, `~meta` and backend tasks, and catch all for anything
not covered by other other projects.
not covered by other projects.
- [public (!) Security Compliance](https://gitlab.com/gitlab-com/gl-security/compliance) for
- [Security Operations (private)](https://gitlab.com/gitlab-com/gl-security/operations) for
- [runbooks (private)](https://gitlab.com/gitlab-com/gl-security/runbooks) -
......
......@@ -190,7 +190,7 @@ For stage transition and new scorecards, it is possible to select `Candidate's R
Greenhouse allows Job Admins to grant other Job Admins the permissions to send out emails on their behalf. This is helpful, for example, when a recruiter is sending out an availability request email but wants the responding email with the times to go to the coordinator so they can schedule next interviews, they could send the email from the coordinator's email address to ensure that happens. In Greenhouse, the activity feed on the candidate's profile shows who actually sent it and who it came from, so that it is clear.
In order to set up these permissions, the person allowing another person to send emails on their behalf should log in to Greenhouse, hover over their name in the top right corner, and click "Account Settings". Then scroll down to the section called "Email Permissions". You can select the first option option to allow any Job Admin or Site Admin to send emails on your behalf, or you can select the second option and choose specific people (who are Job Admins or Site Admins) only who are able to send emails on your behalf. You can remove these users or this functionality at any time.
In order to set up these permissions, the person allowing another person to send emails on their behalf should log in to Greenhouse, hover over their name in the top right corner, and click "Account Settings". Then scroll down to the section called "Email Permissions". You can select the first option to allow any Job Admin or Site Admin to send emails on your behalf, or you can select the second option and choose specific people (who are Job Admins or Site Admins) only who are able to send emails on your behalf. You can remove these users or this functionality at any time.
Once you have the permissions to send emails on someone else's behalf, when you are sending an email to a candidate, you can click the "From" button at the top of the email pop up and choose from the list of available email addresses. If you are using an email template, remember to choose the template and then change the sender, or the template will override any changes you've made.
......
......@@ -47,7 +47,7 @@ celebrate that but instead address the question: How can we unblock in the futur
1. When someone says they are considering quitting, drop everything and listen to them. Ask questions to find out what their concerns are. If you delay, the person will not feel valued and the decision will be irreversible.
1. In addition to announcing new team member arrivals, departures are also announced in the #general chat channel (but only after the Google/Slack accounts are revoked, see the [offboarding page](/handbook/offboarding) and the [offboarding checklist](https://gitlab.com/gitlab-com/people-ops/employment/blob/master/.gitlab/issue_templates/offboarding.md) for details). We must respect the privacy of the individual concerned. If you are asked why someone has left or is leaving, please refer that person to the [general guidelines](/handbook/general-guidelines/#not-public) section of the handbook where we describe what can and cannot be shared.
1. People should not be given a raise or a title because they ask for it or threaten to quit. We should pro-actively give raises and promote people without people asking. If you do it when people ask, you are being unfair to people that don't ask and you'll end up with many more people asking.
1. Don't refer to GitLab [as a family](https://hbr.org/2014/06/your-company-is-not-a-family). It is great that our team feels like a close-knit group and we should encourage that, as this builds a stronger team. But _families_ and _teams_ are different. _Families_ come together for the relationship and do what is critical to retain it. _Teams_ are assembled for the task and do what is required to complete it. Don't put the relationship above the task. Besides, families don't have an an [offboarding process](/handbook/offboarding/). Families should have unconditional love, while teams have conditional love. [The best companies are supporters of families.](https://twitter.com/myriadwill/status/917772249624702976)
1. Don't refer to GitLab [as a family](https://hbr.org/2014/06/your-company-is-not-a-family). It is great that our team feels like a close-knit group and we should encourage that, as this builds a stronger team. But _families_ and _teams_ are different. _Families_ come together for the relationship and do what is critical to retain it. _Teams_ are assembled for the task and do what is required to complete it. Don't put the relationship above the task. Besides, families don't have an [offboarding process](/handbook/offboarding/). Families should have unconditional love, while teams have conditional love. [The best companies are supporters of families.](https://twitter.com/myriadwill/status/917772249624702976)
1. Praise and credit the work of your reports to the rest of the company, never present it as your own. This and many other great lessons can be found in an [Ask MetaFilter thread](http://ask.metafilter.com/300002/My-best-manager-did-this) worth reading.
1. Try to be aware of your [cognitive biases](https://betterhumans.coach.me/cognitive-bias-cheat-sheet-55a472476b18).
1. Combine [consistency and agility](https://hbr.org/2017/01/the-best-strategic-leaders-balance-agility-and-consistency).
......@@ -64,7 +64,7 @@ celebrate that but instead address the question: How can we unblock in the futur
1. We don't have explicit 20% time at GitLab. We measure results and not hours. If people are getting good results in the work that is assigned to them they are free to contribute to other parts of the company or work on a pet project. Don't say "your work on that pet project is hurting your performance". Instead say "we agreed to get X done but it is delayed, what happened and how can I help?"
1. Pick a metric before launching something new. 9 out of 10 launches fail. If a project is not working out shut it down completely. Starving a team of headcount to have it die a slow death is not frugal nor motivating. Fund the winners which will still take years to break even.
1. Do not discuss raises in advance because the salary calculator may change before the amount of the raise is decided.
1. Instead of prescribing a direction to your reports, it is best to ask ask questions following the [Socratic method](https://en.wikipedia.org/wiki/Socratic_method) until you're happy with the direction. Your reports will have deeper knowledge in a more narrow area, so it is easy to draw different conclusions because they base theirs on different data. That is why the questions are so important.
1. Instead of prescribing a direction to your reports, it is best to ask questions following the [Socratic method](https://en.wikipedia.org/wiki/Socratic_method) until you're happy with the direction. Your reports will have deeper knowledge in a more narrow area, so it is easy to draw different conclusions because they base theirs on different data. That is why the questions are so important.
1. Follow [Berkshire's common injunction](https://www.hb.org/the-psychology-of-human-misjudgment-by-charles-t-munger/): "Always tell us the bad news promptly. It is only the good news that can wait.". Make sure to inform your manager of bad news as quickly as possible. Promptly reporting bad news is essential to preserving the trust that is needed to recover from it.
1. Try to avoid military analogies. We're not an army, we're not at war, there is no battle, we're not killing anyone, and we don't have weapons. Military language is [not inclusive](https://www.london.edu/faculty-and-research/lbsr/killing-the-competition) and can lead to zero sum thinking. We take competing and winning very seriously, but there is no need to describe things using vocabulary of physical violence. Similarly, non-collaborative and aggressive terms like "rockstar" and "badass" put up walls between people. If a term is standard in the industry, for example [killing a Unix process](https://shapeshed.com/unix-kill/#how-to-kill-a-process), it is acceptable to use it because that is more efficient. Do use "primary-secondary" instead of "master-slave" for replication mechanisms.
......
......@@ -470,7 +470,7 @@ The new classes are grouped into:
`.wrap-text`: Only applies to images that are positioned left or right. Makes text wrap around the image.
These classes are only applied for screens 992px wide and and wider.
These classes are only applied for screens 992px wide and wider.
If a Position class is used without an Effect class then there will simply be empty space where the image isn't. Similarly, using a Position class without a Size class will have little-to-no effect.
......
......@@ -125,7 +125,7 @@ no merge conflicts (do not rebase, please do `git pull origin master`, then `:wq
and the packages published)
- Posting on Social Media (Twitter/Facebook) or, in case you don't have access,
coordinating with someone who has (e.g. Marcia, Erica, Rebecca, Emily vH, JJ)
- Adding any updates on the the release post process to the handbook
- Adding any updates on the release post process to the handbook
- Delivering the release post as whole.
<i class="fas fa-exclamation-triangle" aria-hidden="true" style="color: red"></i>
......@@ -583,7 +583,7 @@ extras:
Describe the deprecations happening on that release or in upcoming releases. Let our community know about a future deprecation as soon as possible.
The due date is defined by the the removal of that feature. The field is required, and should be set as:
The due date is defined by the removal of that feature. The field is required, and should be set as:
- The date of the removal, e.g., "May 22nd, 2017", or
- An upcoming release (_only_ if the release date in unknown), e.g., "GitLab 12.0", or
......
......@@ -23,7 +23,7 @@ The [#hn-mentions](https://gitlab.slack.com/messages/hn-mentions) Slack channel
![Hacker News channel workflow](/images/handbook/marketing/community-relations/hn-mentions.png){: .shadow}
1. React to notifications and go to the [#hn-mentions](https://gitlab.slack.com/messages/hn-mentions) channel when you see them them appear
1. React to notifications and go to the [#hn-mentions](https://gitlab.slack.com/messages/hn-mentions) channel when you see them appear
1. Read every new message in the channel and make a decision for each one: does it need a response?
1. Respond to the message if necessary, or [involve an expert](/handbook/marketing/community-relations/community-advocacy/#involving-experts) using the template
1. Ping `@sytse` in the `#community-relations` Slack channel if you judge his input is required, or in case of doubt
......
......@@ -448,7 +448,7 @@ Note, while important, the above measurements do not impact your quota attainmen
Handover to SDRs
For an inbound lead that which is the correct contact with interest but requires further touches and qualifications the the following process should occur:
For an inbound lead that which is the correct contact with interest but requires further touches and qualifications the following process should occur:
*BDR confirms all details, including the telephone number, company and email address
*BDR passes the lead to SDR working in that territory or account as a Pre-Qualified Lead
......
......@@ -235,7 +235,7 @@ We hosted a dinner for customers and prospects to mingle with each other and sha
#### Deliver value faster
Pinterest is not a GitLab customer, but uses Kubernetes together with Jenkins. Because there's no [native kubernetes integration](/kubernetes) for Jenkins they needed to dedicate a [team of 4 spending 6 months](https://kubernetes.io/case-studies/pinterest/) to build a custom system to control access managment and allow teams to to self-serve builds. This is functionality that comes out of the box on day one with GitLab.
Pinterest is not a GitLab customer, but uses Kubernetes together with Jenkins. Because there's no [native kubernetes integration](/kubernetes) for Jenkins they needed to dedicate a [team of 4 spending 6 months](https://kubernetes.io/case-studies/pinterest/) to build a custom system to control access managment and allow teams to self-serve builds. This is functionality that comes out of the box on day one with GitLab.
#### Adoption at an incredible pace
......
......@@ -138,7 +138,7 @@ Now let's check if our `gitlab` service is up, and wait for it if not.
**Optional filler**
> * `kubectl proxy`
> * Go the the Kubernetes Dashboard at [http://localhost:8001/ui](http://localhost:8001/ui)
> * Go the Kubernetes Dashboard at [http://localhost:8001/ui](http://localhost:8001/ui)
> * Change the `Namespace` drop-down on the left. Change it from `default` to `All Namespaces`
> * Click on `Workloads` on the left.
......
......@@ -592,7 +592,7 @@ And then memory usage:
## Conclusion
So that's it. In less than 10 minutes, we took an an idea through the complete
So that's it. In less than 10 minutes, we took an idea through the complete
DevOps lifecyle, with issue tracking, planning with an issue board, committing
to the repo, testing with continuous integration, reviewing with a merge request
and a review app, debugging in the terminal, deploying to production, scaling
......
......@@ -85,7 +85,7 @@ Marketing decks linked on this page are the latest approved decks from Product M
The [Pitch Deck](https://docs.google.com/presentation/d/1dVPaGc-TnbUQ2IR7TV0w0ujCrCXymKP4vLf6_FDTgVg/) contains the GitLab narrative and pitch.
### SDR presentation deck
The [SDR deck](https://docs.google.com/presentation/d/1679lQ7AG6zBjQ1dnb6Fwj5EqScI3rvaheIUZu1iV7OY/edit#slide=id.g42cc3032dd_1_1903) is is a condensed version of the company pitch deck. It copies linked slides from the pitch deck (so they can stay in sync.) SDR Managers own responsibility for keeping the deck in sync.
The [SDR deck](https://docs.google.com/presentation/d/1679lQ7AG6zBjQ1dnb6Fwj5EqScI3rvaheIUZu1iV7OY/edit#slide=id.g42cc3032dd_1_1903) is a condensed version of the company pitch deck. It copies linked slides from the pitch deck (so they can stay in sync.) SDR Managers own responsibility for keeping the deck in sync.
This deck can be used on occasions where the SDRs feel they should or could prequalify a prospect before setting a discovery meeting with the SAL. This could for example be someone who isn't our typical target persona but who might have an interest in what we do.
......
......@@ -26,7 +26,7 @@ Various verticals and industries face specific challenges as they address their
| --------- | ------------ |
| **Security** | GitLab’s single platform controls and manages access to the SDLC tool chain helping them to increase confidence in their development process. The ability to audit, review and automate security scans as a core part of the development lifecycle further helps to ensure that every application they build is more secure. |
| **Aging infrastructure** | GitLab simplifies move to modern cloud native (kubernetes) |
| **Compliance** | A single platform that controls and manages access to the the SDLC tool chain. Built in audits, reviews and automation help to create a trusted pipeline. |
| **Compliance** | A single platform that controls and manages access to the SDLC tool chain. Built in audits, reviews and automation help to create a trusted pipeline. |
| **New technology (business disruption / digital transformation)** | This will demand rapid and responsive design, development and iteration from the software teams building the transportation as a service platform and infrastructure. GitLab and concurrent devops can help teams to dramatically decrease cycle times to ship software. |
- [8 challenges for Financial Svcs CIOs](https://www.cio.com/article/3128314/financial-it/8-challenges-that-keep-financial-services-ctos-and-cios-up-at-night.html)
......@@ -52,9 +52,9 @@ Various verticals and industries face specific challenges as they address their
| Challenge | GitLab Helps |
| --------- | ------------ |
| **Security & Data Protection** Ensuring that their systems and data are secure is critical in health care. This is an issue across the entire lifecycle of health care systems from development to production and is a top issue for most all healthcare IT leaders. | A single platform that controls and manages access to the the SDLC tool chain. Built in audits, reviews and automation help to create a trusted pipeline. |
| **Security & Data Protection** Ensuring that their systems and data are secure is critical in health care. This is an issue across the entire lifecycle of health care systems from development to production and is a top issue for most all healthcare IT leaders. | A single platform that controls and manages access to the SDLC tool chain. Built in audits, reviews and automation help to create a trusted pipeline. |
| **Patient Experience** The healthcare market is being dramatically transformed around improving patient experience, making it easier for patients to participate in their care. Ranging from mobile applications to electronic health records and other innovation, healthcare IT leaders are trying to accelerate delivery and iteration are to improve patient experience. | Rapid delivery and iteration are the hallmarks of improving patient experience. Innovation in UX is only possible if IT teams are able to rapidly learn and innovate. Concurrent Devops and GitLab help to streamline delivery and enable IT teams to focus on improving patient experience. |
| **HIPAA** | A single platform that controls and manages access to the the SDLC tool chain. Built in audits, reviews and automation help to create a trusted pipeline. |
| **HIPAA** | A single platform that controls and manages access to the SDLC tool chain. Built in audits, reviews and automation help to create a trusted pipeline. |
- [PWC - Health Industry Issues](https://www.pwc.com/us/en/health-industries/top-health-industry-issues.html)
- [PWC - Top Issues 2018](https://www.pwc.com/us/en/health-industries/assets/pwc-health-research-institute-top-health-industry-issues-of-2018-report.pdf)
......
......@@ -31,7 +31,7 @@ and user persona types.
### User personas
User personas are people who actually use GitLab. They may or may not be the person in
the organization who has the authority and budget to purchase Gitlab, but they
are heavy influencers in the buying process. User personas are are kept in the [GitLab Design System](https://design.gitlab.com/getting-started/personas).
are heavy influencers in the buying process. User personas are kept in the [GitLab Design System](https://design.gitlab.com/getting-started/personas).
- [Full-stack web developer](https://design.gitlab.com/getting-started/personas)
- [DevOps Engineer](https://design.gitlab.com/getting-started/personas)
......
......@@ -155,10 +155,10 @@ Here's a video that shows a typical workflow to update the website
To create a new page you for follow these steps:
1. Create an issue in the [website repo](https://gitlab.com/gitlab-com/www-gitlab-com/issues) **Note**: Don't branch from other repos like the marketing repo.
2. Create an MR from the issue by clicking on the "Create Merge Request" button. This will create a new branch for you and link it to your issue and label the the MR as `WIP:`.
2. Create an MR from the issue by clicking on the "Create Merge Request" button. This will create a new branch for you and link it to your issue and label the MR as `WIP:`.
3. Click on the name of your branch after "Request to Merge" to open that branch in the repository file view.
4. Open the `source` folder. This is where webpages are stored.
5. Click on the directory where you want your webpage to be. For example, if you put a page in the `source` folder it will show up at the "root" level, if you create the new directory inside of another directory it will will appear at that path.
5. Click on the directory where you want your webpage to be. For example, if you put a page in the `source` folder it will show up at the "root" level, if you create the new directory inside of another directory it will appear at that path.
5. Click to add a `New directory` from the plus sign drop down.
6. Name the directory in all lowercase with dashes-between-words for what you want the path of your page to be. For example if you want to create a page at [about.gitlab.com/solutions/cloud-native](/solutions/cloud-native) then click on the `solutions` directory and inside the `solutions` directory create a new directory called `cloud-native`.
7. Click to add a `New file` from the plus sign drop down
......@@ -456,6 +456,6 @@ The [`/resources`](/resources/) section of the website contains downloadable fil
If you'd like to propose new changes to the website and the update is more complicated that you can do on your own to either [create a new page](#creating-a-new-page) or [update and existing page](updating-an-existing-page) you can request help from the Website team. New changes or updates with a due date should be requested at least 2 weeks prior to that due date.
1. Before requesting help, create the content that you want to go live. E.g. draft the exact words that you want updated.
1. To request help from the website team to update the site, create an issue in the [www-gitlab-com](https://gitlab.com/gitlab-com/www-gitlab-com/issues) project
1. Add the specific content (exact wording and images) in the issue description that you want to put live on the website. Note: If the the content is unclear, the issue will be assigned back to you to clarify the content before the website team will begin development work.
1. Add the specific content (exact wording and images) in the issue description that you want to put live on the website. Note: If the content is unclear, the issue will be assigned back to you to clarify the content before the website team will begin development work.
1. add the `Website` label
1. ping @gl-website in the MR or ping @website-team in the #website slack channel.
......@@ -29,7 +29,7 @@ We did a training on these subjects which you can find here:
**What is collaboration?**
Collaborate, according the the Merriam- Webster Dictionary, means “to work jointly with others or together especially in an intellectual endeavor.”
Collaborate, according the Merriam-Webster Dictionary, means “to work jointly with others or together especially in an intellectual endeavor.”
A workforce, also according to the Merriam-Webster Dictionary, is comprised of “the people engaged in a specific activity or enterprise.”
......
......@@ -61,7 +61,7 @@ GitLab uses Slack profiles as an internal team directory, where team members can
BambooHR should send an email to People Ops the day before and the day of a team member's birthday. Celebrate by sending the team member an email (template below) and post on the `#celebrations` channel on Slack so all team members can help them celebrate. GitLabbers with weekend birthdays will be wished a Happy Birthday on the following weekday.
Birthday Email Template: "Happy Birthday! Please use this link [insert link] to redeem your birthday swag! You will need to login or create an account with the swag store to receive your free birthday socks! The username will be your GitLab email. Once you are are in the store you should see your options to order GitLab birthday socks. Please let People Ops know if you have any questions."
Birthday Email Template: "Happy Birthday! Please use this link [insert link] to redeem your birthday swag! You will need to login or create an account with the swag store to receive your free birthday socks! The username will be your GitLab email. Once you are in the store you should see your options to order GitLab birthday socks. Please let People Ops know if you have any questions."
The link for the swag store birthday campaign is located in the People Ops vault in 1Password.
......@@ -111,7 +111,7 @@ We don't have one contact person but can call BambooHR if we want any changes ma
Some changes or additions we make to BambooHR require action from our team members.
Before calling the whole team to action, prepare a communication to the team that is approved by the Chief Culture Officer.
Team Members have employee access to their profile in BambooHR and should update any data that is out-dated or incorrect. If there is a field that cannot be updated, please reach out the the People Ops Analyst with the change.
Team Members have employee access to their profile in BambooHR and should update any data that is out-dated or incorrect. If there is a field that cannot be updated, please reach out to the People Ops Analyst with the change.
## Using RingCentral
......
......@@ -80,7 +80,7 @@ We prefer to offer a single application instead of a network of services or
offering plugins for the following reasons:
1. We think a single application provides a better user experience than a modular approach, as detailed by [this article from Stratechery](https://stratechery.com/2013/clayton-christensen-got-wrong/).
1. The open source nature of GitLab ensures that that we can combine great open source products.
1. The open source nature of GitLab ensures that we can combine great open source products.
1. Everyone can contribute to create a feature set that is [more complete than other tools](/devops-tools/). We'll focus on making all the parts work well together to create a better user experience.
1. Because GitLab is open source the enhancements can become [part of
the codebase instead](https://docs.gitlab.com/ee/project_services/project_services.html) of being external. This ensures the automated tests for all
......
......@@ -241,7 +241,7 @@ The Create team is working to significantly improve the depth of support for cod
Andreas: On the Manage team, we are planning the same. While we are extending our range of [product categories in 2019](https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/14277/diffs), improving the experience and details of our product is a major part of our plans moving forward.
Jason: We are focusing on this this year for [release](https://about.gitlab.com/direction/release)/[verify](https://about.gitlab.com/direction/verify); both have the below theme for the coming year to try to focus on how we solve problems in deeper ways not just be adding more breadth.
Jason: We are focusing on this year for [release](https://about.gitlab.com/direction/release)/[verify](https://about.gitlab.com/direction/verify); both have the below theme for the coming year to try to focus on how we solve problems in deeper ways not just be adding more breadth.
❤️ **More Complete (Minimally Lovable) Features to Solve Complex Problems**
......
......@@ -107,7 +107,7 @@ Calls may be recorded with customer consent, and recordings may be stored in the
##### Agenda
* Screen share with the the customer to discuss the below agenda items
* Screen share with the customer to discuss the below agenda items
* Collaboratively review customer success project README to ensure everything is correct
* Agree on due dates for POC completion, add to project POC milestone
* Review project POC issues - add new issues if necessary with agreed due dates
......
......@@ -82,7 +82,7 @@ Configure the Docker daemon with an insecure registry parameter of `172.30.0.0/1
sudo systemctl restart docker
```
- In Ubuntu edit `/lib/systemd/system/docker.service` and edit edit the `ExecStart` line:
- In Ubuntu edit `/lib/systemd/system/docker.service` and edit the `ExecStart` line:
```
sudo vi /lib/systemd/system/docker.service
......
......@@ -523,7 +523,7 @@ If you want to associate emails to Opportunities using Outreach, follow these st
### Salesforce Lightning for Gmail
If you want to associate emails to Opportunities or other records using the the Salesforce Lightning for Gmail plug in, follow these steps:
If you want to associate emails to Opportunities or other records using the Salesforce Lightning for Gmail plug in, follow these steps:
1. Visit the Chrome Store to download the [Salesforce Lightning for Gmail](https://chrome.google.com/webstore/detail/salesforce-lightning-for/jjghhkepijgakdammjldcbnjehfkfmha) plug in.
1. Click `Add to Chrome`
......
......@@ -396,7 +396,7 @@ This mechanism works the same way, and supports Touch ID to login.
While the above 1Password default recommendation applies to all GitLabbers, there are alternative,
although more complex solutions that can also be used. Google Authentication is a TOTP solution
that can be used to store tokens, for those who want to have separate application for password storage
and token storage. However, be aware that that using two applications is more complex, and not necessary. If
and token storage. However, be aware that using two applications is more complex, and not necessary. If
unsure which mechanism to use, we recommend using 1Password as a TOTP for 2FA.
Follow this [guideline](https://gizmodo.com/how-to-easily-switch-your-two-factor-security-to-a-new-1821808681) when getting a new mobile device, if you are using Google Authenticator as a TOTP mechanism.
......
......@@ -30,7 +30,7 @@ When a customer reports problems when registering their license key, please chec
> During the year before this license started, this GitLab installation had 0 active users, exceeding this license's limit of 5 by -5 users. Please upload a license for at least 0 users or contact sales at renewals@gitlab.com
That usually means that that GitLab instance has more active users than the number allowed by the license key. Please ask the customer for the number of active users and suggest to buy more seats if required.
That usually means that GitLab instance has more active users than the number allowed by the license key. Please ask the customer for the number of active users and suggest to buy more seats if required.
That validation error [has been fixed](https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/4961) but the fix will be included in the `10.7` version of GitLab.
......
......@@ -57,7 +57,7 @@ Also note that users may be using generic mail providers you might not be famili
![Selecting an organization in ZD](/images/handbook/support/zendesk_needs_org-finding-org.png)
### Finding the existing organization in SFDC
1. Log in to to SalesForce using the shared credentials in 1Password.
1. Log in to SalesForce using the shared credentials in 1Password.
1. Enter a domain or full email address into the search bar at the top
![Search bar, in repose](/images/handbook/support/zendesk_needs_org-sfdc-search.png)
......
......@@ -2,7 +2,7 @@
### Performance
A Performance Specialist is a Developer who focuses on ensuring that
GitLab and associated applications are as fast as possible. The Performance Specialist works in in the Performance team that is one of the backend teams.
GitLab and associated applications are as fast as possible. The Performance Specialist works in the Performance team that is one of the backend teams.
The team sets goals for overall performance of GitLab. This means measuring how long a certain task (creating an account, making an MR, doing a code view) takes. This is done with the UX team and focuses on the most used functionality.
......
......@@ -8,6 +8,6 @@
* Continually improve the quality of about.GitLab.com by using discretion of where you think changes are needed.
* Focus on mobile responsiveness for about.gitlab.com and all marketing assets.
* Create high quality frontend code.
* Improve the [static website of GitLab](/) based on the collaborations with the the Designer and CMO.
* Improve the [static website of GitLab](/) based on the collaborations with the Designer and CMO.
* Needs to have extensive knowledge of Rails
* Relevant link: [Marketing Handbook](/handbook/marketing)
......@@ -7,4 +7,4 @@
* Continually improve the quality of GitLab by using discretion of where you think changes are needed.
* Create high quality frontend code.
* Frontend Design Specialist: Implement the interfaces in GitLab proposed by UX Engineers and contributors.
* Frontend Design Specialist: Improve the [static website of GitLab](/) based on the collaborations with the the Designer and CMO.
* Frontend Design Specialist: Improve the [static website of GitLab](/) based on the collaborations with the Designer and CMO.
......@@ -13,7 +13,7 @@ title: "Frontend Engineer"
* Continually improve the quality of GitLab by using discretion of where you think changes are needed.
* Create high quality frontend code.
* Frontend Design Specialist: Implement the interfaces in GitLab proposed by UX Engineers and contributors.
* Frontend Design Specialist: Improve the [static website of GitLab](/) based on the collaborations with the the Designer and CMO.
* Frontend Design Specialist: Improve the [static website of GitLab](/) based on the collaborations with the Designer and CMO.
## Workflow
......
......@@ -8,7 +8,7 @@ title: "Data Analyst"
* Ensure the Company’s cloud and on-premise data is centralized into a single data warehouse that can support data analysis requirements from all functional groups of the Company. See our bizops effort, [Meltano](https://gitlab.com/meltano/meltano/).
* Be the data expert supporting cross-functional teams, gather data from various sources, and build automated reporting to democratize data across the company.
* Provide analyses to identify opportunities and explain trends
* Implement a set of processes that that ensure any changes in transactional system architecture are documented and their impact on the company’s overall data integrity are considered prior to changes being made.
* Implement a set of processes that ensure any changes in transactional system architecture are documented and their impact on the company’s overall data integrity are considered prior to changes being made.
* Build close partnerships with functional owners to help them optimize their resources for allocation, and work with cross-functional teams to help them use insights that will direct their efforts towards the largest impact.
* Create a common data framework so that all company data can be analyzed in a unified manner.
* This position reports to the Manager, Data & Analytics.
......@@ -20,7 +20,7 @@ title: "Data Analyst"
* 2+ years hands on experience in a data analytics role
* 2+ years experience with Python analytics tools suites (pandas, numpy, Jupyter notebooks, etc.)
* Demonstrably deep understanding of SQL and relational databases (Snowflake preferred)
* Hands on experience working with with Python, R, and/or SQL to generate business insights and drive better organizational decision making.
* Hands on experience working with Python, R, and/or SQL to generate business insights and drive better organizational decision making.
* Experience building reports and dashboards in a data visualization tool like Tableau, Birst, or Looker
* Be passionate about data, analytics and automation.
* Experience working with large quantities of raw, disorganized data
......
......@@ -24,7 +24,7 @@ title: "Manager, Data and Analytics"
* 2+ years managing a team of 2 or more data analysts/engineers/scientists
* Demonstrably deep understanding of SQL and relational databases (Snowflake preferred)
* Ability to reason holistically about end-to-end data systems: from ETL to Analysis to Reporting
* Hands on experience working with with Python
* Hands on experience working with Python
* Experience building and maintaining data pipelines (Airflow, Luigi, GitLab CI)
* Experience building reports and dashboards in a data visualization tool like Tableau, Birst, or Looker
* Experience with open source data warehouse tools
......
......@@ -15,7 +15,7 @@ title: "Director of Business Operations"
* Ensure that each metric in the Company’s dashboard has a single source of Truth and that data ownership and validation are incorporated on a consistent basis.
* Determine the level of integration necessary between transactional systems to deliver the right data in the right context to users.
* Develop a roadmap for system expansion, evaluate existing systems and ensure future systems are aligned with the Company’s data architecture plan which you will largely help develop.
* Implement a set of processes that that ensure any changes in transactional system architecture are documented and their impact on the company’s overall data integrity are considered prior to changes being made.
* Implement a set of processes that ensure any changes in transactional system architecture are documented and their impact on the company’s overall data integrity are considered prior to changes being made.
* Collaborate with all functions of the company to ensure data needs are addressed and system.
* Hold regular 1:1’s with all direct reports
* This position reports directly to the CFO and works closely with the executive team to develop an organization plan that addresses company wide analytic resources in either a direct report or matrix model.
......
......@@ -3,7 +3,7 @@ layout: job_family_page
title: "Employment Branding Lead"
---
The Employment Branding Lead will help advance our recruitment and employer brand. They will will work cross-functionally to tell the story of what it's like to work at GitLab and build our reputation as an extraordinary workplace. They will play an important role through their experience in building content for brands across social channels and other platforms to help enable our rapid growth.
The Employment Branding Lead will help advance our recruitment and employer brand. They will work cross-functionally to tell the story of what it's like to work at GitLab and build our reputation as an extraordinary workplace. They will play an important role through their experience in building content for brands across social channels and other platforms to help enable our rapid growth.
## Responsibilities
......
......@@ -3,7 +3,7 @@ layout: job_family_page
title: "Solutions Architect"
---
Solution Architects are the trusted advisors to GitLab prospects and clients, showing how the GitLab solutions address clients business requirements. Solution Architects are responsible for actively driving and managing the technology evaluation and validation stages of the sales process. Solution Architects are the product advocates for GitLab’s Enterprise Edition, serving as a trusted advisor to the client, focusing on the the technical solution while also understanding the business challenges the customer is trying to overcome.
Solution Architects are the trusted advisors to GitLab prospects and clients, showing how the GitLab solutions address clients business requirements. Solution Architects are responsible for actively driving and managing the technology evaluation and validation stages of the sales process. Solution Architects are the product advocates for GitLab’s Enterprise Edition, serving as a trusted advisor to the client, focusing on the technical solution while also understanding the business challenges the customer is trying to overcome.
The Solution Architect for Customer Success Initiatives provides the opportunity to help drive value and change in the world of software development for one of the fastest growing platforms. By applying your solution selling and architecture experience from planning to monitoring, you will support and enable successful adoption of the GitLab platform. You will be working directly with our top enterprise customers. You will be working collaboratively with our sales, engineering, product management and marketing organizations.
......
......@@ -28,4 +28,4 @@ To achieve the first goal of encouraging usage I propose we have** unlimited f
- The business edition plan, which has groups and teams, is** $9 per additional user** (i.e. 10 collaborators are $72 per month).
- There will be a 1 month** free trail**.
What do you think we should do for our **beta users?** Maybe a discount, a free period or something else, please let me know what you think. We also want to encourage people to **participate** in the the Gitlab open source project. Maybe we can give [ everyone that committed to the project](https://github.com/gitlabhq/gitlabhq/graphs/contributors) a credit of $100? Please let me know what you think about the pricing plans, the amounts, the naming, the goals, the free tier, the beta user discount, etc. Please **comment on this post**.
\ No newline at end of file
What do you think we should do for our **beta users?** Maybe a discount, a free period or something else, please let me know what you think. We also want to encourage people to **participate** in the Gitlab open source project. Maybe we can give [ everyone that committed to the project](https://github.com/gitlabhq/gitlabhq/graphs/contributors) a credit of $100? Please let me know what you think about the pricing plans, the amounts, the naming, the goals, the free tier, the beta user discount, etc. Please **comment on this post**.
......@@ -20,7 +20,7 @@ Today we present a new major GitLab version. There are a lot of improvements to
![gitlab](/images/6_0/group_members.png)
From now on a group is not just a directory for projects. It also allows you to add users. After user is added to group - it automatically get access to all existing and new projects inside group.
You can also have have multiple owners for a group who can manage members/projects. With this GitLab becomes more group oriented. That is why we no longer support global namespaces. Project can be part of group or user only.
You can also have multiple owners for a group who can manage members/projects. With this GitLab becomes more group oriented. That is why we no longer support global namespaces. Project can be part of group or user only.
### Merge requests are now possible between a fork and the original project.
......
......@@ -23,4 +23,4 @@ GitLab Enterprise Edition 6.3.1 is available for subscribers at [GitLab Cloud](h
Update instructions can be [found](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/update/patch_versions.md) [here](https://github.com/gitlabhq/gitlabhq/blob/master/doc/update/patch_versions.md).
### Workarounds
Users who cannot upgrade can address address the DoS vulnerability by applying [this patch based on the workaround provided by Rails](/files/0001-Monkey-patch-for-CVE-2013-6414.patch) in `/home/git/gitlab` with `git am` and restarting GitLab.
Users who cannot upgrade can address the DoS vulnerability by applying [this patch based on the workaround provided by Rails](/files/0001-Monkey-patch-for-CVE-2013-6414.patch) in `/home/git/gitlab` with `git am` and restarting GitLab.
......@@ -45,7 +45,7 @@ hard-coded command would be executed by OpenSSH:
/path/to/gitlab-shell key-123
```