Commit 93b2873a authored by Marcia Ramos's avatar Marcia Ramos 🔴

Merge branch 'master' of gitlab.com:gitlab-com/www-gitlab-com into world-tour-blog-post1

parents 018bc6b8 7dc4b3b8
......@@ -125,8 +125,8 @@
- title: "Junior Designer"
description: /jobs/junior-designer/
apply: https://gitlab.workable.com/jobs/296974
open: true
apply:
open: false
- title: "Director of Developer Relations"
description: /jobs/director-developer-relations/
......
......@@ -33,4 +33,8 @@
- title: "GitLab Announces YubiKey U2F Support"
link: http://mobileidworld.com/gitlab-yubikey-u2f-106243/
date: 2016-06-24
- title: "GitLab adds Instruct to Global Partnership Program"
link: http://instruct.com.br/gitlab-parceria-brasil/
date: 2016-07-14
\ No newline at end of file
......@@ -21,7 +21,7 @@
content: |
ALMtoolbox provides services and add-on solutions focused on ALM, DevOps, SCM, IT and Continuous Integration for a variety of customers in many industries, including finance, IT, telecom, security, medical devices and more. The company was founded in 2009 and has won 6 international awards for its contributions to the software community.
החברה מפתחת ומספקת מגוון פתרונות לבעיות נפוצות במחזור חיי הפיתוח, באמצעות מוצרי מדף, פיתוח מותאם, שירותי יעוץ ומכירת כלים. החברה נוסדה בשנת 2009 ולה נסיון רב בעבודה מול מאות לקוחות בארץ ובחו"ל, בתחומי בנקאות, טלקום, IT, בטחון, מכשור רפואי ועוד. במהלך השנים זכתה החברה ב- 6 פרסים בינ"ל על תרומתה לקהילת מפתחי התוכנה בעולם.
<p class="text-right">החברה מפתחת ומספקת מגוון פתרונות לבעיות נפוצות במחזור חיי הפיתוח, באמצעות מוצרי מדף, פיתוח מותאם, שירותי יעוץ ומכירת כלים. החברה נוסדה בשנת 2009 ולה נסיון רב בעבודה מול מאות לקוחות בארץ ובחו"ל, בתחומי בנקאות, טלקום, IT, בטחון, מכשור רפואי ועוד. במהלך השנים זכתה החברה ב- 6 פרסים בינ"ל על תרומתה לקהילת מפתחי התוכנה בעולם.</p>
email: GitLab@almtoolbox.com
contact:
- address: פתח תקווה, ישראל
......
......@@ -227,12 +227,12 @@
picture: rspeicher.jpg
twitter: rspeicher
gitlab: rspeicher
speciality: Backstage
maintains: |
<li>Merge request <a href="http://www.urbandictionary.com/define.php?term=endboss&defid=5331178">endboss</a></li>
<li>Maintainer of <a href="https://gitlab.com/gitlab-com/marketo-tools">Marketo tools</a></li>
<li>Trained <a href="https://gitlab.com/gitlab-org/release-tools/blob/master/doc/release-manager.md">Release Manager</a></li>
<li><a href="http://docs.gitlab.com/ce/markdown/markdown.html">GitLab Flavored Markdown</a> <a href="/jobs/expert/">expert</a></li>
<li>Backstage specialist</li>
story: |
Before joining GitLab the company in 2015, Robert was
already an active member of the GitLab community beginning in 2012,
......@@ -347,9 +347,9 @@
picture: picture_yorick.jpg
twitter: yorickpeterse
gitlab: yorickpeterse
specialty: Performance
maintains: |
<li>Trained <a href="https://gitlab.com/gitlab-org/release-tools/blob/master/doc/release-manager.md">Release Manager</a></li>
<li>Performance specialist</li>
<li><a href="http://docs.gitlab.com/ce/markdown/markdown.html">GitLab Flavored Markdown</a> <a href="/jobs/expert/">expert</a></li>
story: |
Yorick first started working as a professional software developer in
......@@ -370,11 +370,11 @@
picture: gabriel.jpg
twitter: brodock
gitlab: brodock
specialty: Packaging
maintains: |
<li>Merge request <a href="http://www.urbandictionary.com/define.php?term=mini-boss&defid=605674">miniboss</a></li>
<li><a href="https://about.gitlab.com/handbook/support/#support-turbo">Support Turbo</a></li>
<li><a href="http://doc.gitlab.com/ee/gitlab-geo/README.html">Geo</a> <a href="/jobs/expert/">expert</a></li>
<li>Packaging specialist</li>
story: |
Gabriel is the first Brazillian in the team, before joining GitLab,
he was fighting the scalability and performance battle on a
......@@ -426,10 +426,9 @@
picture: grzegorz.png
twitter: GrzegorzBizon
gitlab: grzesiek
specialty: <a href="https://about.gitlab.com/gitlab-ci/">GitLab CI</a>
maintains: |
<li><a href="https://about.gitlab.com/gitlab-ci/">GitLab CI</a> specialist</li>
<li>Merge request <a href="http://www.urbandictionary.com/define.php?term=mini-boss&defid=605674">miniboss</a></li>
<li>Backstage specialist</li>
story: |
Grzegorz is a developer who has worked on open-source projects since 2002.
He enjoys creating software that people actually love using, so GitLab was an obvious choice for his next company to work at.
......@@ -511,6 +510,7 @@
picture: tomasz.jpg
twitter: TomaszMaczukin
gitlab: tmaczukin
specialty: <a href="https://about.gitlab.com/gitlab-ci/">GitLab CI</a>
maintains: |
<li>On-call hero!</li>
<li>Maintainer of <a href="https://gitlab.com/gitlab-org/gitlab-ci-multi-runner">GitLab Runner</a></li>
......@@ -769,6 +769,8 @@
picture: felipe_artur.jpg
twitter: FelipeArtur
gitlab: felipe_artur
maintains: |
<li><a href="http://docs.gitlab.com/ce/project_services/jira.html">JIRA</a> <a href="/jobs/expert/">expert</a></li>
story: |
Software enthusiast who started his career developing desktop applications. Former member of a repositories/task management company who is here to make GitLab better. Likes playing RTS video games and boxing in his free time.
......@@ -780,9 +782,9 @@
picture: dj.png
twitter: twk3
gitlab: twk3
specialty: Packaging
maintains: |
<li>Packaging specialist</li>
<li><a href="https://gitlab.com/gitlab-org/omnibus-gitlab/">Omnibus GitLab</a> specialist</li>
<li><a href="https://gitlab.com/gitlab-org/omnibus-gitlab/">Omnibus GitLab</a> expert</li>
<li><a href="https://about.gitlab.com/handbook/support/#support-turbo">Support Turbo</a></li>
story: |
DJ grew up on a farm in the Canadian Prairies where it is common to have to fix your own tools and equipment. This didn't change when computers became the tools, and he discovered the joy of development while pursuing a career in IT. He has been working as a developer at various sized companies since 2008 and is excited to be able to finally work in the open source community with GitLab.
......@@ -941,8 +943,7 @@
reports_to: VP of Engineering
picture: logo-extra-whitespace.png
gitlab: markglenfletcher
maintains: |
<a href="https://about.gitlab.com/jobs/specialist/issue-triage/"><li>Issue triage specialist</li></a>
specialty: <a href="https://about.gitlab.com/jobs/specialist/issue-triage/">Issue Triage</a>
picture: mark.jpg
story: |
Mark's experience within the technology sector has been varied, including various Web Development and Technical Support roles.
......@@ -958,8 +959,7 @@
picture: christiancouder.jpg
twitter: ChristianCouder
gitlab: chriscool
maintains: |
<a>git command-line specialist</a>
specialty: Git Command-line
story: |
Based near Paris, France, Christian has been developing Git since 2006. He is passionate about open source projects, especially development tools.
......@@ -1034,8 +1034,8 @@
picture: jen-shin.jpg
twitter: godfat
gitlab: godfat
specialty: <a href="https://about.gitlab.com/gitlab-ci/">GitLab CI</a>
maintains: |
<li><a href="https://about.gitlab.com/gitlab-ci/">GitLab CI</a> specialist</li>
<li><a href="http://docs.gitlab.com/ce/incoming_email/README.html">Reply by Email</a> <a href="/jobs/expert/">expert</a></li>
story: |
Jen-Shin is a Taiwanese who is also known as @godfat on the Internet. He learned Ruby from 2006 and has built a ton of stuffs with it including open source libraries. He's also passionate about functional programming, particularly Haskell. Other than programming, Jen-Shin loves computer games, especially some indie games. At some point he would really like to write one indie game as well, combining two major interests.
......@@ -1078,9 +1078,9 @@
picture: alejandro.jpg
twitter: eReGeBe
gitlab: eReGeBe
specialty: Performance
maintains: |
<li>On-call hero!</li>
<li>Performance specialist</li>
story: |
From Venezuela, now in Chile, Alejandro has been passionate about
computers from the moment he once actually deleted System32 and tried
......@@ -1097,8 +1097,7 @@
picture: paco.jpg
twitter: pacoguzman
gitlab: pacoguzman
maintains: |
<li>Performance specialist</li>
specialty: Performance
story: |
Paco started developing Ruby on Rails Web applications on the university.
Since then he has been working on different companies on different sectors,
......@@ -1151,9 +1150,6 @@
picture: hazel.jpg
twitter: hazelyuyang
gitlab: hazelyang
maintains: |
<li>Interaction design specialist</li>
<li>Visual design specialist</li>
story: |
Hazel comes from Taiwan. She is passionate about product design, interaction design,
and illustration. Before joining GitLab, she worked for a digital agency and worked
......@@ -1195,7 +1191,7 @@
locality: Austin, TX
country: USA
role: <a href="https://about.gitlab.com/jobs/production-engineer/">Junior Production Engineer</a>
reports_to: Senior Production Engineer and Infrastructure lead
reports_to: Infrastructure lead
picture: alex.jpg
twitter: purrdeta
gitlab: ahanselka
......@@ -1265,9 +1261,9 @@
picture: ahmad.jpg
twitter: ahmadsherif
gitlab: ahmadsherif
specialty: Performance
maintains: |
<li>On-call hero!</li>
<li>Performance specialist</li>
story: |
Ahmad has been passionate about web development since he laid his eyes
on web forums back in 2003, hasn't stopped coding ever since. He's interested
......
......@@ -126,6 +126,18 @@ GitLab allows you to restrict pushes very carefully, but does not have this opti
> [GitLab issue to implement the same feature](https://gitlab.com/gitlab-org/gitlab-ce/issues/21975)
### Cycle Analytics
GitLab provides a dashboard that lets teams measure the time it takes to go from an idea to production. GitLab can provide this data because it has all the tools built-in: from the idea, to the CI, to code review, to deploy to production.
> [Feature Highlight: Cycle Analytics](https://about.gitlab.com/2016/09/21/cycle-analytics-feature-highlight/)
### Prevent committing secrets in the repositories
GitLab provides a way to avoid committing sensitive files to your repositories automatically.
> [Documentation on push rules](https://docs.gitlab.com/ee/push_rules/push_rules.html#prevent-pushing-secrets-to-the-repository)
## GitLab EE vs. GitHub Enterprise
### Cost
......
......@@ -16,6 +16,8 @@ Please use <a href="https://gitlab.com/gitlab-com/www-gitlab-com/issues">issues<
{: .no_toc}
* [Engineering](/handbook/engineering)
* [Support](/handbook/support)
* [Infrastructure](/handbook/infrastructure)
* [Marketing](/handbook/marketing)
* [Social Media Guidelines](/handbook/marketing/social-media-guidelines)
* [Blog](/handbook/marketing/blog)
......@@ -80,7 +82,7 @@ help and advice. Anyone can chime in on any subject, including people who don't
1. **Directness**<a name="directness"></a>: We try to channel our inner Ben Horowitz by being [both straightforward
and kind, an uncommon cocktail of no-bullshit and no-asshole](https://medium.com/@producthunt/ben-horowitz-s-best-startup-advice-7e8c09c8de1b). Although the feedback is always about your work and not your person it will not be easy to receive it.
1. **Kindness**<a name="kindness"></a>: We don't want [jerks](http://bobsutton.typepad.com/my_weblog/2006/10/the_no_asshole_.html) in our team.
Some companies say [Evaluate People Accurately, Not "Kindly"](http://www.bwater.com/Uploads/FileManager/Principles/Bridgewater-Associates-Ray-Dalio-Principles.pdf).
Some companies say [Evaluate People Accurately, Not "Kindly"](https://www.principles.com/).
We're all for accurate assessment but we think it must be done in a kind way.
Give as much positive feedback as you can and do it in a public way. Give negative
feedback in the smallest setting possible, one-on-one video calls are preferred.
......
......@@ -26,6 +26,7 @@ title: Leadership
- We avoid meetings because those aren't supporting the asynchronous work flow, are hard to conduct due to timezone differences and are limited only to those attending them, making it harder to share.
- 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 in [an ask metafilter thread worth reading](http://ask.metafilter.com/300002/My-best-manager-did-this).
- Try to be aware of your [cognitive biases](https://betterhumans.coach.me/cognitive-bias-cheat-sheet-55a472476b18).
- Great article about [how to think about PIPs](https://mfbt.ca/how-i-talk-to-leaders-about-firing-people-8149dfcb035b), although our time scales are short.
## Articles
......
......@@ -14,7 +14,7 @@ In written communication, I appreciate the top-down approach. Set the subject he
I get many email on which I am only cc'd on, I would very much appreciate if you started emails intended specifically for me with "Sid," or some other salutation that makes it clear that the message is for me.
I have accounts on LinkedIn and Facebook, and I am happy to connect with you on both networks. On LinkedIn, I sometimes send a friend request to you, but on Facebook I will not. I will happily accept your LinkedIn and Facebook friend request, but given that I am the CEO, I don’t want to impose myself on anyone. You can also find me on twitter @sytses.
I have accounts on [LinkedIn](https://www.linkedin.com/in/sijbrandij) and [Facebook](https://www.facebook.com/sytse). I will not send invites to team members on those networks since as the CEO I don't want to impose myself on anyone. But I would love to connect and I will happily accept your LinkedIn and Facebook friend request. You can also find me on Twitter as [@sytses](https://twitter.com/sytses).
## Pick your brain meetings
......
This diff is collapsed.
......@@ -416,7 +416,7 @@ the case.
- [GitLab CE](https://gitlab.com/gitlab-org/gitlab-ce/issues)
- [Omnibus](https://gitlab.com/gitlab-org/omnibus-gitlab/issues)
See [the issue triage policies](/handbook/engineering/issues/issue-triage-policies.html) for the above trackers for more information on how issues should be handled.
See [the issue triage policies](/handbook/engineering/issues/issue-triage-policies) for the above trackers for more information on how issues should be handled.
### Spam
......
......@@ -84,27 +84,49 @@ A [Zap](https://zapier.com/app/editor/9938098/overview) is used to add ticket de
### Create issues
During your interaction with the customers you will most likely need to create an
During your interaction with the customers you will most likely need to create or update an
issue, either for a feature request, for a bug, or for further documentation.
Since we do everything in the open, it is good practice to send the link of the
issue to the requesting customer, so that they can also keep an eye on the discussion
there, and weigh in if necessary.
Workflow for creating an issue:
- Visit the issues page of the project, [CE example here](https://gitlab.com/gitlab-org/gitlab-ce/issues)
- Search to make sure the issue doesn't already exist
- Click **New Issue**
- Choose a template from the **Choose a template** dropdown and take a look at the
**Typical kinds of issues created** below.
- Fill in all the relevant sections
- Assign it to someone, choose an expert [here](https://about.gitlab.com/team/) or feel free to ask
in the #support channel on slack who it should be assigned to. Do not worry that you are assigning
someone a job when you don't even know them and they might be much more senior than you,
if it's not appropriate for them, they will know the right person to assign it to and do that.
Typical kinds of issues created:
- **Bug**
- Make sure it looks like a bug - otherwise ping one of the developers to confirm.
- Reproduce the bug
- Assign the bug fix to the next milestone
- Report back to customer
- **Unpaid feature request**
- Report back to customer with a link to the issue
- **Proposed feature request**
- Provide maximum information and use case from customer in the issue,
mention any alternatives, how badly the customer wants it.
- Ask a developer for opinion (do we want this feature in GitLab: yes/no, the
developer might ask more questions before answer)
- **Paid feature request**
- Follow some process as for an unpaid feature request, AND
- Ask for an estimate
- Report back to customer with a link to the issue
Typical workflow for updating an existing issue:
1. Comment on the issue that another customer is having a problem, adding relevant details
and a link to the ZenDesk ticket. Also if it is an EE customer, add the `~customer`
label to the ticket.
1. Send the customer a link to the issue and invite them to comment.
1. If the customer replies with satisfaction that their concern is
being addressed after seeing the issue, ask them if it would be okay to mark
the ticket as resolved and to instead continue the conversation on the issue.
Sometimes it is helpful to create an issue on the [support issue tracker](https://gitlab.com/gitlab-com/support/issues)
when dealing with a **tough ticket**. Creating an issue allows more people within
......
......@@ -3,30 +3,31 @@ layout: markdown_page
title: "Underperformance"
---
At GitLab, we strive to hire smart people who can get things done, and the bar
At GitLab, we strive to hire smart people who can get things done and the bar
to entry is already high with our interview process. However, the interview
process is imperfect, and people may not live up to expectations. We want
people to be successful and give every opportunity to each individual to work
effectively. At the same time, we need to balance the company’s needs and move
quickly to handle underperformance.
process is imperfect and later on we may find that someone is not living up to expectations. We want people to be successful and give every opportunity for each individual to work effectively but at the same time, we need to balance the company’s needs and move quickly to manage areas of underperformance.
In a scenario when it's clear to a manager that someone isn't accomplishing
enough or working well with others, here is a guideline for how to handle
underperformance. Note that this is only a guideline, and people may be let
go without undertaking these steps--something we wish to avoid if possible.
When it becomes clear to a manager that an individual isn't accomplishing
enough or working well with others, here are guidelines for how to handle
underperformance. Note that someone may be terminated without undertaking these steps if the damage caused by their actions is irreparable or goes against our core values and expected code of conduct. Please work with People Operations on all cases of underperformance to protect the organization and equally consider the side of the individual involved.
1) Manager communicates to direct report during one-on-one that team member
needs to improve. If there are extenuating circumstances, some leeway is
granted, depending on the situation.
needs to improve. If there are extenuating circumstances some leeway may be
granted depending on the situation. This is an area that People Operations can provide a sounding board / voice of reason on.
2) Otherwise, manager documents a [performance improvement plan (PIP)](https://www.shrm.org/templatestools/howtoguides/pages/performanceimprovementplan.aspx) and
shares with direct report. This plan includes:
2) If the lack of performance persists, the manager moves to documenting clear expectations for improvement
in a performance improvement plan (PIP). The intention of a PIP is to support the individual in any way required
to make their time at GitLab a positive experience but also to make clear that immediate and sustained improvement
is required. The Society for Human Resources Management (SHRM) has a [helpful guide](https://www.shrm.org/templatestools/howtoguides/pages/performanceimprovementplan.aspx) to review when
you this step is needed to push past the current performance issues.
* Evaluation of current work by manager(s)
* Clear metrics and concrete goals to improve (e.g. finish X before Y)
A performance improvement plan includes the following:
* Evaluation of current work
* Clear direction including metrics and concrete goals to improve (e.g. finish X before Y)
* Resources/coaching necessary to achieve goals
The manager should consider involving People Ops to help ensure consistency in the PIP process for any affected team member, and also to help protect GitLab should legal claims arise at some point in the future. People Ops does not need to be involved in the creation of the PIP (although People Ops can help), but People Ops should be notified of what is happening.
This [basic PIP template](https://docs.google.com/document/d/1AsVwUikcUofl58eLWhiEEUFJqtwgUQNdDo5lM98bP7o/edit) will provide a good start to creating the document. The template should be customized to fit the particular situation. All PIPs should be forwarded to the People Ops Generalist or Director for a final review and approval before delivery. This step will help ensure consistency in the PIP process for any affected team member and to protect GitLab should legal claims arise as a result of termination.
3) Team member gets time (e.g. 2-4 weeks; this can be longer or shorter and depends on the role and the circumstances) to demonstrate improvements and meet the goals that are outlined in the performance improvement plan. If insufficient improvements are made, the period for the performance improvement plan may be extended, at the discretion of the manager.
......
......@@ -10,6 +10,10 @@
= member.name
%h4
= member.role
- if member.specialty
%h5
= member.specialty
Specialist
- if member.reports_to
%h5
Reports to
......
......@@ -105,5 +105,5 @@ supported by a level 3 or 4 SLA, per the definitions on the [Support](/handbook/
* Affinity for (and experience with) providing customer support
* Excellent spoken and written English
* You share our [values](/handbook/#values), and work in accordance with those values
* [A technical interview](/jobs/#technical-interview) is part of the hiring process for this position.
* A technical interview is part of the hiring process for this position.
* A customer scenario interview is part of the hiring process for this position.
---
layout: job_page
title: "Backstage Specialist"
---
A Backstage Specialist handles behind-the-scenes development that
helps improve the productivity of other developers.
## Responsibilities
* Develops internal tools to streamline processes and automate repetitive tasks (e.g. release tools)
* Identifies major sources of technical debt and propose solutions for them
* Reduces merge conflicts (e.g. in CE/EE merges, CHANGELOG improvements)
* Improves overall test coverage
* Improves error reporting and exception handling
In addition, see the [Developer job description](/jobs/developer).
......@@ -7,5 +7,6 @@ Specialists carry responsibility for a certain topic.
They keep track of issues in this topic and/or spend the majority of their time there.
Commonly there is a lead in this topic that makes the final calls.
- [Backstage Specialist](backstage)
- [Issue Triage Specialist](issue-triage)
- [Database Specialist](database)
......@@ -13,7 +13,7 @@ GitLab Inc. has at most five layers in the team structure:
1. Individual contributors (IC's), which can be a [specialist](/jobs/specialist/) in one things and be an [expert](/jobs/expert/) in multiple things.
The indentation below reflects the reporting relations.
You can see our complete team and who reports to who on the [team page](https://about.gitlab.com/team/).
You can see our complete team and who reports to whom on the [team page](https://about.gitlab.com/team/).
If there is one individual for a role this person is named here, if there are multiple there only is a link to a function description in order to reduce the duplication with the team page.
If there is a hyphen (-) in a line the part before hyphen is the name of the department and sometimes links to the relevant part of the [handbook](https://about.gitlab.com/handbook/).
The job titles link to the job descriptions.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment