search

Dmitri-Sintsov / django-jinja-knockout

Django datatables and widgets, both AJAX and traditional. Display-only ModelForms. ModelForms / inline formsets with AJAX submit and validation. Works with Django templates.
https://django-jinja-knockout.readthedocs.org/
Other
144 stars 29 forks source link

Would you consider relicensing to a permissive license? #5

Closed techdragon closed 7 years ago

techdragon commented 7 years ago

Can the license be changed back to BSD or perhaps changed to Apache 2.0 if you no longer want to use the BSD license.

This library is awesome, but unfortunately the GPL is arguably the worst family in terms of legal risks. No joke, I was once told by a project manager it would be cheaper to hire a javascript developer to build a react app and just use Django Rest Framework, than it would be to get their lawyers to 'approve' the use of this library because its GPL.

If the GPL change was an deliberate copyright/copyleft ethics driven choice, fair enough, its your code, and I respect your choice. But I can't tell from the commit message so all I can do is ask. 😄

Dmitri-Sintsov commented 7 years ago

Is that really such a major issue? Linux is used thoroughly in many commercial projects and Linux is a mix of GNU / BSD / Apache license software, which works well together.

I chose GPL because I support Richard Stallman views that the software should be free in general. Original BSD license was auto-generated by cookiecutter template.

I will compare GPL to Apache 2.0 but knowing that Linux uses all of these licenses, your concerns seems too over-exaggerated.

techdragon commented 7 years ago

@Dmitri-Sintsov Understandable, and an admirable choice. Perhaps instead of Apache 2.0, you would prefer to use LGPLv3 to retain as much of the GPL as possible, but enable users of your wonderful library to use it in the widest range of possible applications. 😄

Dmitri-Sintsov commented 7 years ago

Switched to LGPLv3.