| It feels like you intentionally omitted his immediate follow-up to your quoted comment: > > my theory about embrace/extend/extinguish seems to be as accurate as I thought. > This is confused. Embrace/extend/extinguish means to initially participate in an open standard and then extend the standard in such a way that the non-extended version is sidelined. I'd encourage people to read the entire thread rather than seize on the cherry-picked comment, additionally loaded with terminology like "they want to destroy open source", which doesn't appear in the original thread. I can't speak for whit537, but I do work at Sentry, and I feel your comments about our intentions are disingenuous. We are open in that we feel the existing models don't fit our needs, and we're trying to evolve the language to make non-compete licenses more approachable and thus more mainstream. That doesn't mean an elimination of existing popular OSS licenses. We're even explicit in saying, "FSL is for SaaS businesses". That's pretty narrow, and probably excludes 99% of software. Note that the FSL is developed in the public, and echoes the language I've used above[1]. But if you believe pursuing additional licensing mechanisms means we're destroying OSS, there is probably little I can do to disavow you of that notion. [1] https://github.com/getsentry/fsl.software |
Speaking of disingenuous, every time the sentry people come in here to talk it's always strawmen. My issue is with sentry trying to redefine open source, not your creation of new licenses. If you want to put out proprietary or shared source licenses I'm cool with that, but when you try to mislead people into thinking those licenses are open source I think you're crossing a line. Your head of open source himself said he wants to redefine open source in a way that restricts how people can use software. That is the issue.