> I think AGPL introduces some measurable adoption friction I agree, not just in principle but because I've seen it happen. Where we might disagree is that I

> I think AGPL introduces some measurable adoption friction I agree, not just in principle but because I've seen it happen. Where we might disagree is that I don't assume that's a bad thing. Who are the people/companies who will reject something because of AGPL? Would they have contributed under a different license? Overwhelmingly no. Whatever changes they made, if any, wouldn't have been available to the project anyway. If they want to pay for the software, or support etc., then they'd probably do so even if it's completely proprietary. For them there's dual licensing. Anyone who might have wanted to contribute still has a way to do so. Ditto for anyone who might have wanted to pay. So, who's left? Those who might use but neither contribute nor pay. Are such users a net positive? They're good for the ego, but the support load associated with such users can kill a resource-constrained project. I've seen that happen too. Keeping them away might not be a bad thing. Maybe AGPL is "toxic" in the same way that chlorine is, keeping the pool clean without harming the swimmers. And yes, some people are extra-sensitive to either. ;)