On licensing

[marceline-cramer]

For now, the source code will remain unlicensed. This does NOT place it in the public domain, so I'm explicitly saying here that it's alright to begin contributing, under the mutual agreement that the code will be properly licensed under an open source license in the near future.

The main option I'm considering is the Mozilla Public License (MPL) version 2.0. This is a free software license that protects closed-source code modifications, while not making it too difficult for proprietary developers to integrate it into their own application. I originally considered the LGPL-v3.0, but I decided that the steps that licensing under LGPL requires the application developers to take (dynamically linking, providing a way to modify the librarary) is too harmful to easy integration with other platforms... even proprietary ones, like VRChat or Neos.

@humbletim also suggested licensing each "layer" of the codebase (scripting API, shape primitives, input mapping, etc.) under different licenses depending on the needs for that layer. Personally, I believe that this is too complex, and that it would be too easy for a determined defendant to find loopholes allowing them to get away with acts we never intended if we ever run into any legal issues.

More thoughts and suggestions are welcome and encouraged.