<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Git Enterprise Requirements</title>
	<atom:link href="http://gitguru.com/2009/03/18/git-enterprise-requirements/feed/" rel="self" type="application/rss+xml" />
	<link>http://gitguru.com/2009/03/18/git-enterprise-requirements/</link>
	<description>meditations on scm using git</description>
	<lastBuildDate>Fri, 03 Feb 2012 09:18:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: facebook login</title>
		<link>http://gitguru.com/2009/03/18/git-enterprise-requirements/comment-page-1/#comment-83</link>
		<dc:creator>facebook login</dc:creator>
		<pubDate>Sun, 25 Sep 2011 00:39:29 +0000</pubDate>
		<guid isPermaLink="false">http://gitguru.com/?p=220#comment-83</guid>
		<description>Nice post about gitguru &#187; Git Enterprise Requirements. I am very impressed with the time and effort you have put into writing this story. I will give you a link on my social media blog. All the best!</description>
		<content:encoded><![CDATA[<p>Nice post about gitguru &raquo; Git Enterprise Requirements. I am very impressed with the time and effort you have put into writing this story. I will give you a link on my social media blog. All the best!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Gietzen</title>
		<link>http://gitguru.com/2009/03/18/git-enterprise-requirements/comment-page-1/#comment-82</link>
		<dc:creator>John Gietzen</dc:creator>
		<pubDate>Wed, 21 Sep 2011 17:38:42 +0000</pubDate>
		<guid isPermaLink="false">http://gitguru.com/?p=220#comment-82</guid>
		<description>I am putting together a Git solution for the Windows Enterprise at: https://github.com/otac0n/WebGitNet

We are adding access control in the coming releases, and workflow in the next.  It would be great if your could take a look and tell us what you think!</description>
		<content:encoded><![CDATA[<p>I am putting together a Git solution for the Windows Enterprise at: <a href="https://github.com/otac0n/WebGitNet" rel="nofollow">https://github.com/otac0n/WebGitNet</a></p>
<p>We are adding access control in the coming releases, and workflow in the next.  It would be great if your could take a look and tell us what you think!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Addyson Cleveland</title>
		<link>http://gitguru.com/2009/03/18/git-enterprise-requirements/comment-page-1/#comment-75</link>
		<dc:creator>Addyson Cleveland</dc:creator>
		<pubDate>Wed, 27 Jul 2011 06:40:21 +0000</pubDate>
		<guid isPermaLink="false">http://gitguru.com/?p=220#comment-75</guid>
		<description>Good feed No wonder why Christian Dillstrom had a book mark to this blog post, so you are doing a great job as mobile and social media marketing whiz provides a hyperlink to you.</description>
		<content:encoded><![CDATA[<p>Good feed No wonder why Christian Dillstrom had a book mark to this blog post, so you are doing a great job as mobile and social media marketing whiz provides a hyperlink to you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin</title>
		<link>http://gitguru.com/2009/03/18/git-enterprise-requirements/comment-page-1/#comment-74</link>
		<dc:creator>Martin</dc:creator>
		<pubDate>Thu, 09 Jun 2011 16:14:30 +0000</pubDate>
		<guid isPermaLink="false">http://gitguru.com/?p=220#comment-74</guid>
		<description>1. Security and Access Control
Using a distributed version control system like git, you need write access to your own remotes (ssh) and others need read access (git protocol or possibly http). It is as simple as that. 
All other wishes are just based on a misunderstanding of the distributed concept and that is very common. Eclipse project and their hooks for validating committers is an extreme example... sad...

In a corporate environment you need to protect all data that you don&#039;t want to share with the world. The protection of secret data in most places is usually a joke and there is no real point in asking for more in the DVCS so putting the git: and http: servers behind the corp firewall would keep the data in the DVCS repos as (un)protected as the rest of the secret data. Local repos should be on encrypted drives if you care.

2. Integration with the “typical” Development Environment
Plugins are typically something that you should avoid. It creates extra work because most people are using DVCS for many different kinds of projects. That means, either you learn you DVCS once an for all or  you learn how to use it in a variety of different ways depending on what IDE or other environment you are using or what plugins you currently like.
  
3. Repository Visualization
Use gitk and git-gui or install a git server somewhere. Gitorious works well and is reasonably easy to install on your own servers if you follow the instructions.

4. Example Workflows
Use the same as Linus... Why would you mess up things by using a non distributed workflow just because you are in a corporate environment... Except from start using Git, projects leaders must make is clear to the subordinates that the work is not done until they have pushed it to their public remote so that the project leaders can pull. And this is the most difficult thing in the whole chain... to make project leaders understand why they need to use a DVCS at all...

5. Simplified Administration
I have installed a gitorious server... It works wonderfully well but it contain lots of features that you really don&#039;t need, like multiple committers for one repo and teams etc... Administrative effort is basically zero... Users are registering themselves and they create repos or clone existing repos by themselves.</description>
		<content:encoded><![CDATA[<p>1. Security and Access Control<br />
Using a distributed version control system like git, you need write access to your own remotes (ssh) and others need read access (git protocol or possibly http). It is as simple as that.<br />
All other wishes are just based on a misunderstanding of the distributed concept and that is very common. Eclipse project and their hooks for validating committers is an extreme example&#8230; sad&#8230;</p>
<p>In a corporate environment you need to protect all data that you don&#8217;t want to share with the world. The protection of secret data in most places is usually a joke and there is no real point in asking for more in the DVCS so putting the git: and http: servers behind the corp firewall would keep the data in the DVCS repos as (un)protected as the rest of the secret data. Local repos should be on encrypted drives if you care.</p>
<p>2. Integration with the “typical” Development Environment<br />
Plugins are typically something that you should avoid. It creates extra work because most people are using DVCS for many different kinds of projects. That means, either you learn you DVCS once an for all or  you learn how to use it in a variety of different ways depending on what IDE or other environment you are using or what plugins you currently like.</p>
<p>3. Repository Visualization<br />
Use gitk and git-gui or install a git server somewhere. Gitorious works well and is reasonably easy to install on your own servers if you follow the instructions.</p>
<p>4. Example Workflows<br />
Use the same as Linus&#8230; Why would you mess up things by using a non distributed workflow just because you are in a corporate environment&#8230; Except from start using Git, projects leaders must make is clear to the subordinates that the work is not done until they have pushed it to their public remote so that the project leaders can pull. And this is the most difficult thing in the whole chain&#8230; to make project leaders understand why they need to use a DVCS at all&#8230;</p>
<p>5. Simplified Administration<br />
I have installed a gitorious server&#8230; It works wonderfully well but it contain lots of features that you really don&#8217;t need, like multiple committers for one repo and teams etc&#8230; Administrative effort is basically zero&#8230; Users are registering themselves and they create repos or clone existing repos by themselves.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marina</title>
		<link>http://gitguru.com/2009/03/18/git-enterprise-requirements/comment-page-1/#comment-73</link>
		<dc:creator>Marina</dc:creator>
		<pubDate>Tue, 07 Jun 2011 16:17:57 +0000</pubDate>
		<guid isPermaLink="false">http://gitguru.com/?p=220#comment-73</guid>
		<description>Пишите больше!</description>
		<content:encoded><![CDATA[<p>Пишите больше!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chaser Cruz</title>
		<link>http://gitguru.com/2009/03/18/git-enterprise-requirements/comment-page-1/#comment-71</link>
		<dc:creator>Chaser Cruz</dc:creator>
		<pubDate>Thu, 26 May 2011 13:15:31 +0000</pubDate>
		<guid isPermaLink="false">http://gitguru.com/?p=220#comment-71</guid>
		<description>Installation of Git is an advantage though it is a blank state. You can do whatever you want with it. It is a great idea for those dreamers to have a flexibility but still having problems and needs to clean up what have done wrong. Another thing about Git is that you can import and connect your users organization, Whatever you think is in properly place.</description>
		<content:encoded><![CDATA[<p>Installation of Git is an advantage though it is a blank state. You can do whatever you want with it. It is a great idea for those dreamers to have a flexibility but still having problems and needs to clean up what have done wrong. Another thing about Git is that you can import and connect your users organization, Whatever you think is in properly place.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vasya</title>
		<link>http://gitguru.com/2009/03/18/git-enterprise-requirements/comment-page-1/#comment-69</link>
		<dc:creator>vasya</dc:creator>
		<pubDate>Thu, 05 May 2011 16:48:48 +0000</pubDate>
		<guid isPermaLink="false">http://gitguru.com/?p=220#comment-69</guid>
		<description>Hi !</description>
		<content:encoded><![CDATA[<p>Hi !</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stewart</title>
		<link>http://gitguru.com/2009/03/18/git-enterprise-requirements/comment-page-1/#comment-68</link>
		<dc:creator>Stewart</dc:creator>
		<pubDate>Wed, 04 May 2011 02:24:17 +0000</pubDate>
		<guid isPermaLink="false">http://gitguru.com/?p=220#comment-68</guid>
		<description>I got some points of you. I know this distributed revision control system really helpful but for me it&#039;s a little difficult to use this software. Let alone I am only an individual developer so I won&#039;t use Git.

Anyway, thanks for sharing it although I don&#039;t use Git, I got some points of there.

Regards,
Stewart</description>
		<content:encoded><![CDATA[<p>I got some points of you. I know this distributed revision control system really helpful but for me it&#8217;s a little difficult to use this software. Let alone I am only an individual developer so I won&#8217;t use Git.</p>
<p>Anyway, thanks for sharing it although I don&#8217;t use Git, I got some points of there.</p>
<p>Regards,<br />
Stewart</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: diy solar</title>
		<link>http://gitguru.com/2009/03/18/git-enterprise-requirements/comment-page-1/#comment-66</link>
		<dc:creator>diy solar</dc:creator>
		<pubDate>Thu, 14 Apr 2011 10:38:38 +0000</pubDate>
		<guid isPermaLink="false">http://gitguru.com/?p=220#comment-66</guid>
		<description>Are you a solo web developer or maybe you work as a team? Well, if that’s the case, you would want to use Git. So what difference does it have from all the other installers out there? Well, for one, once you install Git. It’s standard installation is a blank slate. You are very much free to do whatever you please with it. what does every developer dream of? It could be the liberty and the flexibility that can be offered to them while using the said program.</description>
		<content:encoded><![CDATA[<p>Are you a solo web developer or maybe you work as a team? Well, if that’s the case, you would want to use Git. So what difference does it have from all the other installers out there? Well, for one, once you install Git. It’s standard installation is a blank slate. You are very much free to do whatever you please with it. what does every developer dream of? It could be the liberty and the flexibility that can be offered to them while using the said program.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: david miller</title>
		<link>http://gitguru.com/2009/03/18/git-enterprise-requirements/comment-page-1/#comment-65</link>
		<dc:creator>david miller</dc:creator>
		<pubDate>Fri, 08 Apr 2011 17:58:01 +0000</pubDate>
		<guid isPermaLink="false">http://gitguru.com/?p=220#comment-65</guid>
		<description>Ok our IT team in Stockholm say the gitolite is extremely interesting and will be in touch for more specifications. thanks again for this info
DM</description>
		<content:encoded><![CDATA[<p>Ok our IT team in Stockholm say the gitolite is extremely interesting and will be in touch for more specifications. thanks again for this info<br />
DM</p>
]]></content:encoded>
	</item>
</channel>
</rss>

