-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
albyhub isn't open source - signing up for albyhub requires a EULA #823
Comments
Thanks for bringing this up! quite important actually. The account (which has some ToS) is optional and not required by the app actually. but I have to review if there that needs to be reflected here. |
Thanks for highlighting it. Which paragraphs of the EULA terms interfere with the Apache License? We could highlight more the original intention that that the EULA refers only to the combination of using Alby Hub together with an Alby account. |
All of them. The Apache license defines a set of licensing terms. If you add any other terms, such as a EULA, it is no longer the set of terms that is defined by the name “Apache license”, and it is longer “Apache licensed”. It is also thus not open source, as the definition of open source includes “no EULA”. EULAs are incompatible with open source software by their nature. Open source software, also known as free software, preserves the freedoms of a user of software. EULAs restrict those freedoms. |
Thanks. Is there a concrete example in the current EULA that restricts the use of the software? |
The AlbyHub EULA states:
These are incompatible with free software licenses. If one must agree to these terms to use the products, then they're not open source/free software. |
Further:
This means that these restrictions supersede the Apache license, and they are substantially more restrictive. AlbyHub is thus licensed under a proprietary and restrictive (i.e. nonfree) license. |
This is a contradiction. Either I have rights to the application under Apache 2.0, or I have to abide by these terms. The Apache 2.0 license is not "Subject to the following terms" - it is the complete license to the software.
If there are additional terms to which I am subject, then the application is NOT licensed under Apache 2.0, as the Apache 2.0 license does not have those additional terms.
The text was updated successfully, but these errors were encountered: