title: Is using a central repository going against GIT's purpose?
body: <p>If you are in a <em>corporate</em> setting with many people working on a particular application, is it going against the grain of a <a href="http://en.wikipedia.org/wiki/Distributed_revision_control" rel="noreferrer">distributed version control</a> system to have an official central repository?</p>
  
  <p>Sometimes I struggle to understand the concept of a distributed version control system such as <a href="http://git-scm.com/" rel="noreferrer">GIT</a> in a corporate environment.  If you didn't have a central repository, wouldn't it be a PITA to figure out who had the latest updated version to pull from, who has feature x or bug fix y that everyone needs to grab, etc, etc.</p>
  
  <p>Is it defeating the purpose of <a href="http://git-scm.com/" rel="noreferrer">GIT</a> to use it in a similar fashion to <a href="http://subversion.tigris.org/" rel="noreferrer">SVN</a>, with a central repository that everyone pushes/pulls from?  Every time I think about doing that I feel like I'm missing the point of everything.</p>
  
  <p>Could someone enlighten me?</p>