I believe, respectfully, that you're reading posturing into my position where none exists. In a typical scenario for us, we use some open source software for o

I believe, respectfully, that you're reading posturing into my position where none exists. In a typical scenario for us, we use some open source software for our SaaS platform. We need to extend it in ways that weren't envisaged, so we (a) add some hooks to allow extensions and (b) add the extensions themselves. Our preference is to contribute both (a) and usually (b) back to the project. But sometimes for business reasons we can't contribute (b), or at least not until more people internally have their heads around it. AGPL stops us from contributing (a) and not (b). So we just don't use AGPL software. I wasn't trying to poison the well, I was just indicating what our decision making process is. Some people, like us, have valid business reasons for not using AGPL software, even though we love OSS. I find it weird that this narrative thing pops up here. There's no narrative. If I was the owner of said AGPL software, I probably wouldn't give a rat's arse if anyone said they weren't going to use my software. But my original post was a specific response to someone who said "Not sure what the downsides are." [of using AGPL]. So let me try again. Here's one possible downside - *you may miss out on some patches that you would have otherwise got, since your license is incompatible with some people's business needs".