title: Seeking a naming convention for multiple Git repos under a single Team Project
body: <p>I'm an experienced developer, working solo and using VS 2015 together with on-premises TFS 2015. I'm just getting started with TFS, Git and Scrum, however, and so I have a lot to learn yet.</p>
  
  <p>After some discussion with my project manager I've decided to organize everything I do (including even home-related non-software projects) under a single TFS Team Project (as discussed <a href="http://nkdagility.com/one-team-project/" rel="nofollow">here</a> and <a href="http://haacked.com/archive/2014/06/30/github-issues-saved-my-marriage/" rel="nofollow">here</a>).</p>
  
  <p>I'm now trying to settle upon the best naming convention for my code repositories, as well as an appropriate storage folder hierarchy.</p>
  
  <p>Initially I'm considering adopting a standard such as this, with a left-to-right narrowing scope:</p>
  
  <pre><code>work.customers.joespizza.posapp
  work.customers.joespizza.hrmgr
  work.customers.billthebarber.emptychaircounter
  work.internal.products.whirlygigspinner
  work.internal.products.nostrilfitter
  work.internal.infrastructure.buildmanager
  home.music.trumpetpractice.scoretransposer
  home.household.toastercontroller
  </code></pre>
  
  <p>Source code storage would follow accordingly (e.g. <code>D:\Dev\Git\Work\Customers\JoesPizza\PosApp</code>).</p>
  
  <p>I have two questions:</p>
  
  <ol>
  <li>Does this seem like a sound approach, at least to get things started?</li>
  <li>Assuming I do go with this, is the TFS/VS/Git combination flexible enough to allow for a later restructuring, should it eventually prove to be troublesome?</li>
  </ol>