<story><title>GitLab Master Plan</title><url>https://about.gitlab.com/2016/09/13/gitlab-master-plan/</url></story><parent_chain><item><author>mikepurvis</author><text>Makes for a tough pitch at an established shop with existing tools already in place.</text></item><item><author>theunquietone</author><text>Hey Paul - All great notes. We believe in a single solution from idea to production. More about that here:  &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;about.gitlab.com&amp;#x2F;direction&amp;#x2F;#scope&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;about.gitlab.com&amp;#x2F;direction&amp;#x2F;#scope&lt;/a&gt;&lt;p&gt;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.&lt;p&gt;Later today we&amp;#x27;re having a live event to talk more about that vision and answer questions. &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;page.gitlab.com&amp;#x2F;20160913_unveilingmasterplan_landingpage.html&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;page.gitlab.com&amp;#x2F;20160913_unveilingmasterplan_landing...&lt;/a&gt;&lt;p&gt;Again, love the notes and how you&amp;#x27;re thinking about this. Happy we are aligned!&lt;p&gt;Edit: Sorry! Removed the signature. Habit :)</text></item><item><author>PaulRobinson</author><text>It&amp;#x27;s interesting to me how much effort is being spent on adding tools like issue tracking, build pipelines, deploy management, etc. vs just providing good hooks for standalone tools that do all those things.&lt;p&gt;We have discussions about Jenkins vs Concourse, where to keep ansible vault passwords, should documentation live in Github wiki or in Confluence (apparently &amp;quot;tech&amp;quot; documentation in the form, &amp;quot;business&amp;quot; documentation in the latter - what if it&amp;#x27;s both? Who decides?), and so on.&lt;p&gt;There is something nice about being able to go to a single place and saying &amp;quot;OK, it&amp;#x27;s all here in this box&amp;quot;. Github has made inroads with some of this stuff, but not quite enough. Gitlab could try and do all this, but then people will moan (&amp;quot;I prefer JIRA&amp;#x2F;Trello&amp;#x2F;whatever&amp;quot;).&lt;p&gt;Most of the pain around developer&amp;#x2F;business workflow around us at the moment actually comes down to the fact that nobody has _really_ thought about providing a great unified UX for all of this.&lt;p&gt;Part of the concern is people want to be &amp;quot;flexible&amp;quot;. No, dictate, just make sure what you dictate is a better solution to what people have.&lt;p&gt;If GitLab get it right, github could be a minor player (unless they keep up) in a few years time.</text></item></parent_chain><comment><author>sytse</author><text>We want to play nice with established tools and give people the option to use them.&lt;p&gt;We have:&lt;p&gt;1. Extensive JIRA integration (and we&amp;#x27;re working on improving this) &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;docs.gitlab.com&amp;#x2F;ee&amp;#x2F;project_services&amp;#x2F;jira.html&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;docs.gitlab.com&amp;#x2F;ee&amp;#x2F;project_services&amp;#x2F;jira.html&lt;/a&gt;&lt;p&gt;2. Jenkins support &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;docs.gitlab.com&amp;#x2F;ee&amp;#x2F;integration&amp;#x2F;jenkins.html&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;docs.gitlab.com&amp;#x2F;ee&amp;#x2F;integration&amp;#x2F;jenkins.html&lt;/a&gt; via our commit status API &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;docs.gitlab.com&amp;#x2F;ee&amp;#x2F;api&amp;#x2F;commits.html&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;docs.gitlab.com&amp;#x2F;ee&amp;#x2F;api&amp;#x2F;commits.html&lt;/a&gt;&lt;p&gt;3. Slack integration &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;gitlab.com&amp;#x2F;gitlab-org&amp;#x2F;gitlab-ce&amp;#x2F;blob&amp;#x2F;master&amp;#x2F;doc&amp;#x2F;project_services&amp;#x2F;slack.md&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;gitlab.com&amp;#x2F;gitlab-org&amp;#x2F;gitlab-ce&amp;#x2F;blob&amp;#x2F;master&amp;#x2F;doc&amp;#x2F;proj...&lt;/a&gt; and we&amp;#x27;re working on a Slack bot &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;gitlab.com&amp;#x2F;gitlab-org&amp;#x2F;gitlab-ce&amp;#x2F;issues&amp;#x2F;20799&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;gitlab.com&amp;#x2F;gitlab-org&amp;#x2F;gitlab-ce&amp;#x2F;issues&amp;#x2F;20799&lt;/a&gt;&lt;p&gt;We realize that we should allow other tools to integrate well and want to open up as much as we can via API&amp;#x27;s.</text></comment>
<story><title>GitLab Master Plan</title><url>https://about.gitlab.com/2016/09/13/gitlab-master-plan/</url></story><parent_chain><item><author>mikepurvis</author><text>Makes for a tough pitch at an established shop with existing tools already in place.</text></item><item><author>theunquietone</author><text>Hey Paul - All great notes. We believe in a single solution from idea to production. More about that here:  &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;about.gitlab.com&amp;#x2F;direction&amp;#x2F;#scope&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;about.gitlab.com&amp;#x2F;direction&amp;#x2F;#scope&lt;/a&gt;&lt;p&gt;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.&lt;p&gt;Later today we&amp;#x27;re having a live event to talk more about that vision and answer questions. &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;page.gitlab.com&amp;#x2F;20160913_unveilingmasterplan_landingpage.html&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;page.gitlab.com&amp;#x2F;20160913_unveilingmasterplan_landing...&lt;/a&gt;&lt;p&gt;Again, love the notes and how you&amp;#x27;re thinking about this. Happy we are aligned!&lt;p&gt;Edit: Sorry! Removed the signature. Habit :)</text></item><item><author>PaulRobinson</author><text>It&amp;#x27;s interesting to me how much effort is being spent on adding tools like issue tracking, build pipelines, deploy management, etc. vs just providing good hooks for standalone tools that do all those things.&lt;p&gt;We have discussions about Jenkins vs Concourse, where to keep ansible vault passwords, should documentation live in Github wiki or in Confluence (apparently &amp;quot;tech&amp;quot; documentation in the form, &amp;quot;business&amp;quot; documentation in the latter - what if it&amp;#x27;s both? Who decides?), and so on.&lt;p&gt;There is something nice about being able to go to a single place and saying &amp;quot;OK, it&amp;#x27;s all here in this box&amp;quot;. Github has made inroads with some of this stuff, but not quite enough. Gitlab could try and do all this, but then people will moan (&amp;quot;I prefer JIRA&amp;#x2F;Trello&amp;#x2F;whatever&amp;quot;).&lt;p&gt;Most of the pain around developer&amp;#x2F;business workflow around us at the moment actually comes down to the fact that nobody has _really_ thought about providing a great unified UX for all of this.&lt;p&gt;Part of the concern is people want to be &amp;quot;flexible&amp;quot;. No, dictate, just make sure what you dictate is a better solution to what people have.&lt;p&gt;If GitLab get it right, github could be a minor player (unless they keep up) in a few years time.</text></item></parent_chain><comment><author>omnibrain</author><text>But it&amp;#x27;s a great pitch for a shop with limited ressources  that currently has nothing.</text></comment>