Update the End User License Agreement to more clearly state the inten… #21
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…tion of the limited commercial use. The License limitation clause permitted the license for only personal and non-commercial use, however, I pointed out that any streamer or video produced using this application for a channel that receives monetary compensation via ads or subs or bits or superchats or donations was, in fact, actually commercial use that was prohibited by this license. I was talking with cyanidesugar, and, they communicated that their intention with the license was not to prevent a streamer or video maker from using the panel on their channel but to prevent people from taking the software and incorporating it into a cloud service commercially. I have modified the license with my suggestions that carve out exactly that use case in the License Limitation section and clarifies the conditions where the software is allowed to be used in a small but important business/commercial use case. This application is no longer being developed, so I'm not expecting this to be merged, it's simply a suggestion if ever this license was going to be re-used by a developer in the future.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…tion of the limited commercial use.
Following our recent discussion in the #lobby on October 30th, 2024 in Discord under the username RebootTech, I have created this pull request for your review as previously mentioned.
During our discussions, it was highlighted that the current licensing terms restrict usage to non-commercial purposes, potentially excluding streamers and video producers who generate revenue through ads, subscriptions, donations, and other monetization methods. After consulting with cyanidesugar, it became apparent that the original intent of the license was not to prevent such usage but to discourage the commercial exploitation of the software, such as integrating it into a commercial cloud service or reselling access to manage SAMMI.
To align the license with this intended use, I have proposed modifications to the License Limitation section. These changes specifically define and permit commercial use in the context of content creation for monetized channels while maintaining restrictions against broader commercial exploitation.
Given that development on this application has ceased, I understand this PR may not be merged. However, I believe these changes could be useful for any future reuse or development of the software, ensuring the license accurately reflects the intended usage scenarios. The revised wording aims to clearly articulate permissible uses without the ambiguities that negative phrasing often introduces. I tried to carve out that one specific use case while leaving the actual intent of the license intact and preserve the wording that was there with minimal changes. If I was going to re-write that section entirely, I would explicitly state the license grant rather than using negative phrasing because of the ambiguities that negative phrasing often introduces. In any case. This is what I said that I would do. I'm open to feedback and discussion if you would like to communicate about it. If not, that's OK too. Thank you! and have a fantastic day!