title: Organizing a project in git
body: <p>I have a closed-source project (processing texts in various languages) that I want to open-source, probably by uploading it to bitbucket. But I am not sure how/if I should split it into subprojects.</p>
  
  <p>Currently the whole project is in svn as one big structure:</p>
  
  <ul>
  <li>the main system (a set of tools in java)</li>
  <li>ant plugins (requires a particular version of the system; ant is a build system, we use it to load a language resource, build and test it)</li>
  <li>documentation (how to run, develop resources, ..)</li>
  <li>language resource 1</li>
  <li>:</li>
  <li>language resource n</li>
  </ul>
  
  <p>The language resources might have different licences and possibly be contributed by third parties.</p>
  
  <p>I am wondering: should I keep this project together (only removing language resources with a more restrictive license) or should I split it into individual project. The latter seems more like the thing to do, but how do I keep the versions in sync? Just manually, using readme files?</p>
  
  <p>(More details based on answer below:)
  Usually, the user would download the system, the ant plugins and one language resources. They would need to be mutually compatible. But sometimes he would download it without the scripts (if he does not do any experimenting but integrate it into a production system). Sometimes, on the other hand they might want to download multiple or even all resources with it.</p>
  
  <p>Thanks for any suggestions</p>