| > AGPL doesn't cover internal software if you don't expose it outside of the company. What about "internal" users of the company modified AGPL software (eg. employees)? I would be surprised if they are not entitled to having access to the source code under the very same AGPL terms (which gives them the right to distribute the software as well). GPL and related licenses do allow personal use of modified software without publishing or distributing it, but company internal is not "personal" use: you are exposing some users to modified AGPL software. I haven't read AGPL in detail so I could very well be wrong: can you point to the exact clauses which allow this exception? (Or rather, exact language that does not forbid it) Note that users (in case of AGPL) or recipients (in case of GPL) of the software might decide not to exercise their rights, which could be pretty common for employees. To quote AGPLv3 from https://www.gnu.org/licenses/agpl-3.0.html: > 13. Remote Network Interaction; Use with the GNU General Public License.
> Notwithstanding any other provision of this License, if you modify the Program, your modified version must prominently offer all users interacting with it remotely through a computer network (if your version supports such interaction) an opportunity to receive the Corresponding Source of your version by providing access to the Corresponding Source from a network server at no charge, through some standard or customary means of facilitating copying of software. This Corresponding Source shall include the Corresponding Source for any work covered by version 3 of the GNU General Public License that is incorporated pursuant to the following paragraph.
I don't see how this "protects" company from offering the software to all the "internal" users under AGPLv3, allowing them to distribute it along freely under the same license. |