Am I correct in thinking that what we're missing is an "ALGPL", a version of the AGPL that only requires modifications to be distributed and not everything linking to it? At the moment the AGPL seems to be the only common license that requires modifications behind a corporate firewall to be published but the copy left nature makes it corporate cancer.
You don't have to make it available to the public if you only use it internally. You only ever have to share it with the people who use it. If it's only internally used that means you don't have to share it.
Even if it's externally used that doesn't mean it has to be freely available. If you require a paid subscription to access the AGPLed software then you only have to provide the source to those that have paid for the subscription.
> If you require a paid subscription to access the AGPLed software then you only have to provide the source to those that have paid for the subscription.
While true, there's no restriction on the subscribers making the code public.
True (and one can't add it, as the license procludes doing so), but in my experience working for a company that distributed most of its software under the A/LGPL licenses to paying customers only, they aren't really interested in doing that. We never had one of our modules being publicly distributed by a third-party.
