3 ms·
I don't think that's a fair statement of the FSF's position. From the horse's mouth: > Early drafts of GPLv3 allowed licensors to add an Affero-like requireme
by jacques_chester 8y ago
I don't think that's a fair statement of the FSF's position.
From the horse's mouth:
> Early drafts of GPLv3 allowed licensors to add an Affero-like requirement to publish source in section 7. However, some companies that develop and rely upon free software consider this requirement to be too burdensome. They want to avoid code with this requirement, and expressed concern about the administrative costs of checking code for this additional requirement. By publishing the GNU Affero GPLv3 as a separate license, with provisions in it and GPLv3 to allow code under these licenses to link to each other, we accomplish all of our original goals while making it easier to determine which code has the source publication requirement.
https://www.gnu.org/licenses/gpl-faq.html#SeparateAffero https://www.gnu.org/licenses/gpl-faq.html#SeparateAffero
The "administrative burden" is not academic, by the way. Where I work we spend a lot of time and money checking that we are compliant with every license pulled in directly or indirectly into our products.
- kemitchell 8y agoAdministrative burden isn't academic, but it's not peculiar to AGPL, either. GPLv2/3-style copyleft gets forgone all the time on pure process grounds. It's nontrivial to identify which permissive licenses apply to some bag of artifacts an engineer dug up online. FSF faced fork threats when it floated AGPL-GPL merger in GPLv3.
- jacques_chester 8y ago> Administrative burden isn't academic, but it's not peculiar to AGPL, either. I didn't mean to imply that. The AGPL however greatly expands the scope of folks to whom the burden applies. Some companies can basically just look for AGPL to exclude because they don't distribute anything. Others (like us) must check everything.