Does AGPL have any notion of boundary between AGPL and non-AGPL software components? Something like a lesser/library GPL seems more fair: the 'LAGPL' components people use is open sourced to them, so the I/O network flaw of the [L]GPL is fixed, but the other parts of the product have their own license.
A regular GPL with a constraint on number-of-users seems fine for protecting the openness of a product intended for personal (non-hosting-provider) use, and pinry can license a commercial version for hosting providers.
Comments
Does AGPL have any notion of boundary between AGPL and non-AGPL software components? Something like a lesser/library GPL seems more fair: the 'LAGPL' components people use is open sourced to them, so the I/O network flaw of the [L]GPL is fixed, but the other parts of the product have their own license.
A regular GPL with a constraint on number-of-users seems fine for protecting the openness of a product intended for personal (non-hosting-provider) use, and pinry can license a commercial version for hosting providers.