Re:Authlib: Python Authentication
by malkarouri on Monday June 26, 2023 @11:29AM
(#36481001)
Exactly. Should be GPL licensed, and commercial projects can always buy commercial licenses.
That might be his intention; at least force an intermediary OSS app before commercial use. else-payup.
I could create a fork that differs only in name and maybe changes one or two default settings. See also: Chromium forks that disable telemetry and nothing else.
Re:Authlib: Python Authentication
by OkayPhysicist on Monday June 26, 2023 @12:57PM
(#36482421)
The commercial license comes with some added functionality, and support. I suspect the "for open source projects" and "for commercial software" labels aren't meant as restrictions (i.e., "Only these kinds of projects can use this license") but rather as suggestions ("If you have this kind of project, you'll probably want to use this license"). Though as it stands, it's definitely ambiguous, which is the last thing anyone wants from their licensing agreement.
And even if the licensing of this project holds up as the author intends: If I make an Open Source project based on this, and someone else uses that in a commercial product, it would be 100% legal according to the BSD license.