Hacker News new | past | comments | ask | show | jobs | submit login

> For example ES could buy out rights for independent development, or they could simply pay part of their income to the original developers.

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.




> 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.

This is a false dichotomy. You don't need to "care most about financial reward" to recognize that FOSS is simply not sustainable.

There is a whole level of freedoms one can grant (or not) to users of their software. FOSS is one extreme. Proprietary software is another. I don't think we need to tolerate black boxes, just because we want functioning software.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: