In a message dated Fri, 7 May 2010, Edward Ned Harvey writes:

>> From: discuss-boun...@lopsa.org [mailto:discuss-boun...@lopsa.org] On
>> Behalf Of Trey Harris
>>
>> assuming you already have SSH access to machines; just set up a
>> pseudouser with a restricted login shell to own the repositories and
>> give
>> your programmers' ssh keys access to that pseudouser's account.)
>
> Um ... Doesn't that make it no-longer decentralized?
> The pseudouser's directory becomes the central repository.

Every git repository is the same, but I'm just talking about a 
first-among-equals.  It doesn't make it less decentralized any more than 
hosting your project on github makes git centralized.

At its base level, it just allows your site to store the source code in a 
secure place controlled and managed by the sysadmin rather than on 
developers' working machines.

It also improves the efficiency of ordinary collaboration--it's nice that 
with git I can send you any private set of changes in an email without 
bothering the other developers (many sites have policy about the quality 
of code that can be pushed up to the server, so if you have a broken 
branch you want to share with someone else, in most systems you can only 
send others a tarball, it's hard to share the full history of changes). 
But it would suck if those p2p contacts were the ordinary way that 
developers had to share their changes.

Having a git server you give everyone in your firm access to also allows 
you to pick the best source management model for the task, even if it's 
one that's centralized.  For instance, if you have a project managing, 
say, image files that can't be reasonably merged, then for that project 
you treat the git server as you would a Subversion server, and all the 
designers go through a pull and push at the times they might do svn co and 
svn commit.

Having a canonical server also lets you use more exotic management models 
like area lieutenants, integration managers, etc. etc. etc.--but a site 
with only a few developers wouldn't care about that.

Trey
_______________________________________________
Discuss mailing list
Discuss@lopsa.org
http://lopsa.org/cgi-bin/mailman/listinfo/discuss
This list provided by the League of Professional System Administrators
 http://lopsa.org/

Reply via email to