This one strikes the right balance between restriction and permissions. NC and ND are simply too restrictive.
Too restrictive. People should be able to make money from stuff.
The definition of "commercial" could also be taken in extremely broad senses, making serious reuse risky in many applications.
Notably, many university courses use it, notably MIT OpenCourseWare. Ciro wonders if it is because academics are wary of industry, or if they want to make money from it themselves. This reminds Ciro of a documentary he watched about the origins of one an early web browsers in some American university. And then that university wanted to retain copyright to make money from it. But the PhDs made a separate company nonetheless. And someone from the company rightly said something along the lines of:
The goal of universities is to help create companies and to give back to society like that. Not to try and make money from inventions.
TODO source.
The GNU project does not like it either www.gnu.org/licenses/license-list.en.html#CC-BY-NC:
This license does not qualify as free, because there are restrictions on charging money for copies. Thus, we recommend you do not use this license for documentation.
In addition, it has a drawback for any sort of work: when a modified version has many authors, in practice getting permission for commercial use from all of them would become infeasible.
Created by MongoDB, attempts to be even more restrictive than AGPL by more explicitly saying that indirect automatic requests are also included in the "you must give source" domain: opensource.stackexchange.com/questions/8025/difference-between-mongodb-sspl-and-gnu-agpl
The base use case is:
which is what MongoDB is trying to ensure, which sounds fair.
This is an interesting licensing model that might just scale.

Discussion (0)

Sign up or sign in create discussions.

There are no discussions about this article yet.