Matches in DBpedia 2016-04 for { <http://lucumr.pocoo.org/2013/7/23/licensing/> ?p ?o }
Showing triples 1 to 17 of
17
with 100 triples per page.
- licensing accessdate "2015-11-18".
- licensing date "2013-07-23".
- licensing first "Armin".
- licensing isCitedBy Business_models_for_open-source_software.
- licensing isCitedBy GNU_Affero_General_Public_License.
- licensing isCitedBy GNU_General_Public_License.
- licensing isCitedBy License_compatibility.
- licensing isCitedBy License_proliferation.
- licensing isCitedBy Multi-licensing.
- licensing isCitedBy Permissive_free_software_licence.
- licensing last "Ronacher".
- licensing publisher "lucumr.pocoo.org".
- licensing quote "The AGPLv3 was a terrible success, especially among the startup community that found the perfect base license to make dual licensing with a commercial license feasible. MongoDB, RethinkDB, OpenERP, SugarCRM as well as WURFL all now utilize the AGPLv3 as a vehicle for dual commercial licensing. The AGPLv3 makes that generally easy to accomplish as the original copyright author has the rights to make a commercial license possible but nobody who receives the sourcecode itself through the APLv3 inherits that right. I am not sure if that was the intended use of the license, but that's at least what it's definitely being used for now.".
- licensing quote "The License Compatibility Clusterfuck - When the GPL is involved the complexities of licensing becomes a non fun version of a riddle. So many things to consider and so many interactions to consider. And that GPL incompatibilities are still an issue that actively effects people is something many appear to forget. For instance one would think that the incompatibility of the GPLv2 with the Apache Software License 2.0 should be a thing of the past now that everything upgrades to GPLv3, but it turns out that enough people are either stuck with GPLv2 only or do not agree with the GPLv3 that some Apache Software licensed projects are required to migrate. For instance Twitter's Bootstrap is currently migrating from ASL2.0 to MIT precisely because some people still need GPLv2 compatibility. Among those projects that were affected were Drupal, WordPress, Joomla, the MoinMoin Wiki and others. And even that case shows that people don't care that much about licenses any more as Joomla 3 just bundled bootstrap even though they were not licenses in a compatible way . The other traditional case of things not being GPL compatible is the OpenSSL project which has a license that does not go well with the GPL. That license is also still incompatible with the GPLv3. The whole ordeal is particularly interesting as some not so nice parties have started doing license trolling through GPL licenses.".
- licensing title "Licensing in a Post Copyright World".
- licensing url licensing.
- licensing url "http://lucumr.pocoo.org/2013/7/23/licensing/".