[License-review] For Approval: Convertible Free Software License, Version 1.1 (C-FSL v1.1)
Elmar Stellnberger
estellnb at elstel.org
Tue Oct 2 10:17:38 UTC 2018
The problem about dual licensing is that I can not be sure whether I may
use contributions made to the open source branch of the project. I would
have to reprogram every patch sent to the open source branch in order to
assimilate it in the proprietary branch. - and then there are patches so
tiny that you can not reprogram them. That is a problem although tiny
patches where there is no other way to achieve the same functionality
should not fall under copyright law.
On 10/1/18 11:30 PM, Bruce Perens wrote:
> Dual-licensing is a well-developed strategy for mixing pure Open Source
> licensing with paid licensing producing income, with both sides
> producing benefit for the other. It sounds like some of the people
> commenting haven't learned about it. It is legally much better
> structured than the submitted license, in part because of the use of a
> contributor license agreement. There is also the potential for a
> covenant back to the developer preventing the product from being taken
> entirely private.
>
> Thanks
>
> Bruce
>
> _______________________________________________
> License-review mailing list
> License-review at lists.opensource.org
> http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org
>
More information about the License-review
mailing list