Re:Why we’re changing to the AGPL license
by kelnos on Tuesday October 13, 2020 @07:24PM
(#24771483)
Right, but if you accept outside contributions, and those contributors give you their changes under the AGPL as well, you cannot relicense their work under terms other than the AGPL.
You can get around this by requiring copyright assignment from all contributors, or by making contributors sign an agreement that allows you to do what you want to do.
Re:Why we’re changing to the AGPL license
by auggierose on Tuesday October 13, 2020 @05:58PM
(#24770811)
The problem is contributions by others, of course.
This is incorrect. If you own copyright on something you can transfer those rights to other people in any way you want.
I can give you a copy of my software under AGPL and another copy under a completely different license and the two things are independent from each other.
There isn't a "remove the copyleft restrictions" mechanism.
You can simply give out a new copy with a closed license that allows, for example, execution as a service, static linking, dynamic linking but no copy.