title: How can I make a decoupled component of an application into it's own package yet still maintain it in the parent application?
body: <p>If a particular component of an application is decoupled enough from the parent that it can be used by other applications, how would I go about making that component into it's own composer package yet still maintain it in the scope of the parent application?</p>
  <p>As an example, I'd like to achieve what Laravel did with it's database component: <a href="https://github.com/illuminate/database" rel="nofollow noreferrer">https://github.com/illuminate/database</a></p>
  <p>Since it says READ ONLY, I'm under the impression that that &quot;subtree&quot; is still maintained from the parent Laravel/framework git repository yet retain the characteristics of a regular git repo in order for it to be distributed as a Composer package.</p>
  <p>Is my impression accurate?  How do I achieve this sorcery?</p>
  <p>Thanks in advance.</p>