search

Agalin / pidgin_macos_integration

Pidgin plugin adding macOS shell integration
BSD 2-Clause "Simplified" License
8 stars 1 forks source link

License #8

Closed kgraefe closed 5 years ago

kgraefe commented 5 years ago

I am no expert, but I think your licensing is not compatible with Pidgin/libpurple.

From what I understand, GPL code can call BSD code, but not the other way around. Therefore as Pidgin and libpurple are under GPL, plugins must be GPL as well.

Agalin commented 5 years ago

If I understand licenses correctly, GPL code can be used with any GPL-ompatible license. And GNU lists BSD (edit. 2: BSD 2-clause is listed as FreeBSD) as GPL-compatible. But I'm not a lawyer and if you have any sources that explain this, then I'll change license.

Edit. Pidgin itself says that plugin license should be GPL-compliant, not exactly GPL.

kgraefe commented 5 years ago

According to GNU compatible means that you can combine code released under the other license with code released under the GNU GPL in one larger program [...] provided the combination is released under the same GNU GPL version.

Agalin commented 5 years ago

And BSD allows that. It's actually MORE open than GNU/GPL. Combination in this case is Pidgin bundled with plugin - and BSD licensed plugin can be freely merged into GPL code.

Agalin commented 5 years ago

I think that this FAQ entry describes situation best. Plugin is an additional module and 2-clause BSD is compliant as more lax so it can be used there.

kgraefe commented 5 years ago

Sorry for wasting your time then ❤️

Agalin commented 5 years ago

No problem, I'm never sure about those. THat's one of the reasons I'm not a fan of GPL - license cooperation.