Add license and open source FAQ

LICENSE.md

@@ -0,0 +1,43 @@
+# License
+
+## Acceptance
+
+By using the software, you agree to all of the terms and conditions below.
+
+The licensor is committed to releasing all of the codebase source under a Creative Commons license in the event that active maintenance of this software is discontinued. This license will remain in effect until a public statement is made acknowledging the discontinuity of active maintenance and the codebase is released under the aforementioned open source license.
+
+## License grant
+
+The licensor grants you a non-exclusive, royalty-free, worldwide, non-sublicensable, non-transferable license to use, copy, distribute, make available, and prepare derivative works of the software, in each case subject to the limitations below.
+
+This software is licensed for use in both private and public settings, for both commercial and non-commercial purposes, subject to the limitations below.
+
+## Limitations
+
+You may not provide the software to third parties as a hosted or managed service, where the service provides users with access to any substantial set of the features or functionality of the software.
+
+You may not move, change, disable, or circumvent the license key functionality in the software, and you may not remove or obscure any functionality in the software that is protected by the license key. Additionally, you may not attempt to bypass or hack the licensing mechanism in any way to gain access to paid features without purchasing the appropriate license.
+
+You may not alter, remove, or obscure any licensing, copyright, or other notices of the licensor in the software. Any use of the licensor’s trademarks is subject to applicable law. 
+
+You may not reproduce any of the paid features included in this software, nor may you use any plugins or external tools that attempt to replicate or provide similar functionality as the paid features.
+
+## No Liability
+
+As far as the law allows, the software comes as is, without any warranty or condition, and the licensor will not be liable to you for any damages arising out of these terms or the use or nature of the software, under any kind of legal claim.
+
+## Other Terms and Conditions.
+
+The Licensor shall not be bound by any additional or different terms or conditions communicated by You unless expressly agreed.
+
+Any arrangements, understandings, or agreements regarding the software not stated herein are separate from and independent of the terms and conditions of this license.
+
+## Interpretation
+
+For the avoidance of doubt, this license does not, and shall not be interpreted to, reduce, limit, restrict, or impose conditions on any use of the software that could lawfully be made without permission under this License.
+
+To the extent possible, if any provision of this license is deemed unenforceable, it shall be automatically reformed to the minimum extent necessary to make it enforceable. If the provision cannot be reformed, it shall be severed from this license without affecting the enforceability of the remaining terms and conditions.
+
+No term or condition of this license will be waived and no failure to comply consented to unless expressly agreed to by the licensor.
+
+Nothing in this license constitutes or may be interpreted as a limitation upon, or waiver of, any privileges and immunities that apply to the licensor or you, including from the legal processes of any jurisdiction or authority.

SOURCE_CODE.md

@@ -0,0 +1,17 @@
+# FAQ about source code
+
+## Can we expect Luna Park's code to be open source in the future?
+
+We recognize the value of open source and we're definitely open to the idea of making the Luna Park visual scripting editor open source in the future. However, currently, the code is closely intertwined with our webapp, which won't be open source. Separating the code would require an immense amount of time and resources, which we're not able to commit to right now.
+
+## Can the git repo for Luna Park be made open source since the NPM package source is already available?
+
+We understand the desire for open source and appreciate the accessibility it provides. However, the NPM package source is only a transpiled version of the codebase, and tree-shaking is used to remove any irrelevant code that we're not ready to share. As a result, there is much more to our codebase than what is available through the NPM package.
+
+## How can we be assured of the security of Luna Park if the code is not open source?
+
+We understand the concerns regarding security, but it's important to note that reviewing the entire codebase of a package can be a daunting task. Even if Luna Park were open source, it's unlikely that every user would be able to thoroughly review the entire codebase. However, we ensure that our packages are not obfuscated, allowing for efficient analysis by automated security tools.
+
+## What happens if Luna Park is no longer maintained in the future?
+
+We take this concern seriously, and have addressed it in our licensing terms. If we ever cease active maintenance of Luna Park, we are committed to releasing the entire codebase under a Creative Commons license. This ensures that the code remains accessible and can continue to be used and developed by the community.