The problem is that .qtz is a binary file and therefore, not conducive to this style of version control. It's fine for static artifacts like images, etc but not for things you'd want to see diffs of as time goes on. The problem with the <directory> element (I've said this like 3 times already) containing an absolute path is that you'd have to reconstruct your file system in the event of a recovery in order for the .mid files (and other artifacts) to be found.
As for the plugins, the README.md for a given "project" would just provide clear instructions on how to satisfy the requirements of the project (install foo and bar, etc).
The problem is that .qtz is a binary file and therefore, not conducive to this style of version control. It's fine for static artifacts like images, etc but not for things you'd want to see diffs of as time goes on. The problem with the
<directory>element (I've said this like 3 times already) containing an absolute path is that you'd have to reconstruct your file system in the event of a recovery in order for the .mid files (and other artifacts) to be found.As for the plugins, the
README.mdfor a given "project" would just provide clear instructions on how to satisfy the requirements of the project (install foo and bar, etc).