7 ms·

Hey Paul - All great notes. We believe in a single solution from idea to production. More about that here: https://about.gitlab.com/direction/#scope https://ab

Hey Paul - All great notes. We believe in a single solution from idea to production. More about that here: https://about.gitlab.com/direction/#scope https://about.gitlab.com/direction/#scope We hope to make it easy to go to a single place for everything needed for development from issue boards, CI, analytics, etc. The unified UX for this tool is key and we are hiring a great team to support that goal. Later today we're having a live event to talk more about that vision and answer questions. https://page.gitlab.com/20160913_unveilingmasterplan_landingpage.html https://page.gitlab.com/20160913_unveilingmasterplan_landing... Again, love the notes and how you're thinking about this. Happy we are aligned! Edit: Sorry! Removed the signature. Habit :)

mikepurvis 10y ago
Makes for a tough pitch at an established shop with existing tools already in place.
- sytse 10y ago
  We want to play nice with established tools and give people the option to use them. We have: 1. Extensive JIRA integration (and we're working on improving this) https://docs.gitlab.com/ee/project_services/jira.html https://docs.gitlab.com/ee/project_services/jira.html 2. Jenkins support https://docs.gitlab.com/ee/integration/jenkins.html https://docs.gitlab.com/ee/integration/jenkins.html via our commit status API https://docs.gitlab.com/ee/api/commits.html https://docs.gitlab.com/ee/api/commits.html 3. Slack integration https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/project_services/slack.md https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/proj... and we're working on a Slack bot https://gitlab.com/gitlab-org/gitlab-ce/issues/20799 https://gitlab.com/gitlab-org/gitlab-ce/issues/20799 We realize that we should allow other tools to integrate well and want to open up as much as we can via API's.
- theunquietone 10y ago
  We hope to create tools and resources to make that pitch and migration easier. Out of curiosity, what tools are you currently using? We think it'll be a piece by piece migration versus all at once. In a perfect world, we have a tool for an all at once migration but perhaps that will come with time.
  - mbreese 10y ago
    The problem with that approach is that you're limited by the quality of your weakest tool. Code review might be a strength, but if your CI tool is weak, that's what you'll be judged on. Integrations are a way to allow you to focus on what you do best and effectively outsource the rest. Ideally, the integration hooks would be well integrated, but I don't see an upside in trying to make a monolithic app in this market.
    - jobvandervoort 10y ago
      GitLab allows you to integrate with your existing tools if you please or require. But if you're fine using our tools (which are awesome, if you'd ask me), setup and cost will be zero.
    - cryptos 10y ago
      I agree. It is essentially the same vision like the old ALM tools had. They were beaten by better more specialized tools following the unix philosophy: do one thing and do it well.
  - Roritharr 10y ago
    We've just opted for GitLab EE, the True-Up Licensing Model won us over, but also the promise of a working Jira Integration. That's still very limited and a pita to setup, even harder when you use atlassians hosted Jira. I don't want to buy GitLab Licenses for non-developers, especially as our Jira is connected to Zendesk, something which doesn't make sense to connect directly to GitLab.
    - sytse 10y ago
      We already have an extensive JIRA integration https://docs.gitlab.com/ee/project_services/jira.html https://docs.gitlab.com/ee/project_services/jira.html But I agree we can do better. If something is unclear please email support@ our company domain to get help. But I agree with your comment that we should extend the scope of the integration and make it work better with hosted JIRA. Our VP of Engineering is assigning someone to this task. Feel free to email stan@ company domain with a link to this comment and with what you need so we can have an engineer look into it. Many companies use JIRA and it should work great with GitLab.
- omnibrain 10y ago
  But it's a great pitch for a shop with limited ressources that currently has nothing.
- Grangar 10y ago
  We're currently moving to the Atlassian stack, from Bitbucket to Jira to Confluence. I really want to switch over to Gitlab reading this but the sunk cost is too huge already...
- sytse 10y ago
  We want to play nice with existing tools. For example we're spending a lot of time improving our JIRA integration https://docs.gitlab.com/ee/project_services/jira.html https://docs.gitlab.com/ee/project_services/jira.html Most of our new users use only part of GitLab's functionality and we want to support that use case with extensive integrations and APIs.
  - harbottle 10y ago
    Hey Sid, have you seen this: https://github.com/dka23/gitlab-github-proxy https://github.com/dka23/gitlab-github-proxy. I packaged it up and I already use it successfully with GitLab EE on-site: https://gitlab.com/harbottle/glghproxy-packager https://gitlab.com/harbottle/glghproxy-packager The approach of including a GitHub -> GitLab API translation layer would allow GitLab to integrate with any application that can use GitHub. I've added this info to this ticket: https://gitlab.com/gitlab-org/gitlab-ce/issues/20418#note_15372111 https://gitlab.com/gitlab-org/gitlab-ce/issues/20418#note_15... Big fan of GitLab btw, keep up the good work!
shawnee_ 10y ago
"Please don't sign comments; they're already signed with your username. If other users want to learn more about you, they can click on it to see your profile. " Applies to job title, too. Yes, even at companies who are special enough to get millions of dollars from VCs. source: "In Comments" https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
- thedufer 10y ago
  I think it's important to take the bigger picture into account here. Letting us know who she is was a key part of that comment, since it's immediately relevant to the content.
- vmasto 10y ago
  Every rule has its exceptions. Sometimes it's nice to be able to quickly verify that the person answering a very specific comment about a specific company works at that company by avoiding the initial confusion or having to click anything. Let's not be overscrupulous.
dkn 10y ago
Doesn't that kind of lend itself towards the walled garden philosophy? Is there functionality being built-in to integrate with Gitlab instead of being forced to use everything Gitlab has to offer?
- sytse 10y ago
  We want to be open to other applications, I've elaborated on this in https://news.ycombinator.com/item?id=12493537 https://news.ycombinator.com/item?id=12493537

mikepurvis 10y ago

Makes for a tough pitch at an established shop with existing tools already in place.

sytse 10y ago
We want to play nice with established tools and give people the option to use them. We have: 1. Extensive JIRA integration (and we're working on improving this) https://docs.gitlab.com/ee/project_services/jira.html https://docs.gitlab.com/ee/project_services/jira.html 2. Jenkins support https://docs.gitlab.com/ee/integration/jenkins.html https://docs.gitlab.com/ee/integration/jenkins.html via our commit status API https://docs.gitlab.com/ee/api/commits.html https://docs.gitlab.com/ee/api/commits.html 3. Slack integration https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/project_services/slack.md https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/proj... and we're working on a Slack bot https://gitlab.com/gitlab-org/gitlab-ce/issues/20799 https://gitlab.com/gitlab-org/gitlab-ce/issues/20799 We realize that we should allow other tools to integrate well and want to open up as much as we can via API's.
theunquietone 10y ago
We hope to create tools and resources to make that pitch and migration easier. Out of curiosity, what tools are you currently using? We think it'll be a piece by piece migration versus all at once. In a perfect world, we have a tool for an all at once migration but perhaps that will come with time.
- mbreese 10y ago
  The problem with that approach is that you're limited by the quality of your weakest tool. Code review might be a strength, but if your CI tool is weak, that's what you'll be judged on. Integrations are a way to allow you to focus on what you do best and effectively outsource the rest. Ideally, the integration hooks would be well integrated, but I don't see an upside in trying to make a monolithic app in this market.
  - jobvandervoort 10y ago
    GitLab allows you to integrate with your existing tools if you please or require. But if you're fine using our tools (which are awesome, if you'd ask me), setup and cost will be zero.
  - cryptos 10y ago
    I agree. It is essentially the same vision like the old ALM tools had. They were beaten by better more specialized tools following the unix philosophy: do one thing and do it well.
- Roritharr 10y ago
  We've just opted for GitLab EE, the True-Up Licensing Model won us over, but also the promise of a working Jira Integration. That's still very limited and a pita to setup, even harder when you use atlassians hosted Jira. I don't want to buy GitLab Licenses for non-developers, especially as our Jira is connected to Zendesk, something which doesn't make sense to connect directly to GitLab.
  - sytse 10y ago
    We already have an extensive JIRA integration https://docs.gitlab.com/ee/project_services/jira.html https://docs.gitlab.com/ee/project_services/jira.html But I agree we can do better. If something is unclear please email support@ our company domain to get help. But I agree with your comment that we should extend the scope of the integration and make it work better with hosted JIRA. Our VP of Engineering is assigning someone to this task. Feel free to email stan@ company domain with a link to this comment and with what you need so we can have an engineer look into it. Many companies use JIRA and it should work great with GitLab.
omnibrain 10y ago
But it's a great pitch for a shop with limited ressources that currently has nothing.
Grangar 10y ago
We're currently moving to the Atlassian stack, from Bitbucket to Jira to Confluence. I really want to switch over to Gitlab reading this but the sunk cost is too huge already...
sytse 10y ago
We want to play nice with existing tools. For example we're spending a lot of time improving our JIRA integration https://docs.gitlab.com/ee/project_services/jira.html https://docs.gitlab.com/ee/project_services/jira.html Most of our new users use only part of GitLab's functionality and we want to support that use case with extensive integrations and APIs.
- harbottle 10y ago
  Hey Sid, have you seen this: https://github.com/dka23/gitlab-github-proxy https://github.com/dka23/gitlab-github-proxy. I packaged it up and I already use it successfully with GitLab EE on-site: https://gitlab.com/harbottle/glghproxy-packager https://gitlab.com/harbottle/glghproxy-packager The approach of including a GitHub -> GitLab API translation layer would allow GitLab to integrate with any application that can use GitHub. I've added this info to this ticket: https://gitlab.com/gitlab-org/gitlab-ce/issues/20418#note_15372111 https://gitlab.com/gitlab-org/gitlab-ce/issues/20418#note_15... Big fan of GitLab btw, keep up the good work!

shawnee_ 10y ago

"Please don't sign comments; they're already signed with your username. If other users want to learn more about you, they can click on it to see your profile. " Applies to job title, too. Yes, even at companies who are special enough to get millions of dollars from VCs. source: "In Comments" https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html

thedufer 10y ago
I think it's important to take the bigger picture into account here. Letting us know who she is was a key part of that comment, since it's immediately relevant to the content.
vmasto 10y ago
Every rule has its exceptions. Sometimes it's nice to be able to quickly verify that the person answering a very specific comment about a specific company works at that company by avoiding the initial confusion or having to click anything. Let's not be overscrupulous.

dkn 10y ago

Doesn't that kind of lend itself towards the walled garden philosophy? Is there functionality being built-in to integrate with Gitlab instead of being forced to use everything Gitlab has to offer?

sytse 10y ago
We want to be open to other applications, I've elaborated on this in https://news.ycombinator.com/item?id=12493537 https://news.ycombinator.com/item?id=12493537