title: Symfony2 - creating own vendor bundle - project and git strategy
body: <p>We're considering creating our own <code>common</code> bundle for entity mapping and services for use within few separate apps. A bundle should be easy to modify, run, include and test. I know about <a href="http://symfony.com/doc/current/cookbook/bundles/best_practices.html" rel="noreferrer">Best Practices for Structuring Bundles</a>, but I don't know what <code>git</code> strategy to use when it comes to development.</p>
  
  <p>Should we create <code>common</code> bundle as a whole project and commit whole repository to our git server, or is it better to start source control only for root of <code>common</code> bundle and push only its contents? I see this approach in bundles available on <code>github</code>, but I don't know easy and comfortable way to develop bundles that way.</p>