License duplicity #4
Description
@sofarrar @bambooforest In review of the repo I noticed that there are several projects with different licenses across the repo. This is not unlike an edited volume with different chapters with different licenses on the chapters. However, for clarity and simplicity each separately licensed project should be given its own license.
The different sub-projects could be related back to a shell project via the git-submodule method. If you want me to do this then please assign this task to me.
The situation is not as simple as adding a new license file to the project root.