Earlier quoted context omitted.
Well, let's take a look at ElasticSearch, since that's the current hot topic. If Lucene followed the same logic being espoused here, then ElasticSearch as we know it wouldn't exist, because they wouldn't be able to use Lucene, which is an incredibly core component to ES. Elastic employs several people to work on Lucene full time at this point, so they're "giving back" in that regard, but they're still making money of…
You have a valid point, and I don't have the answers to your concerns yet. I am sure best practices that protect Lucenes of the world will develop, given chance. For example ES could buy out rights for independent development, or they could simply pay part of their income to the original developers. Having constraints for selling and building on other people's work doesn't mean that one shouldn't be able to do it, ju…
This sounds exactly like a lot of proprietary software licensing agreements :)
>Having constraints for selling and building on other people's work doesn't mean that one shouldn't be able to do it, just that previous link in the chain should be financially rewarded for it.
I don't think there's anything wrong with building and selling proprietary software, but that's really what's being described here.
If financial reward is what you most care about, write proprietary software. If FOSS is what you care most about, then the AGPL is probably a good fit for you. It won't force anyone to pay you for using your work, but it would force them to give back to the community.