> I think it's totally normal and correct to have a license where a company like Amazon can't come in, steal the volunteer work of hundreds of developers, slap their logo on it and sell it.
Why shouldn't this to apply to every company - including the one ostensibly shepherding the open source project? I would argue that employing a bunch of core developers doing 10% of the work doesn't entitle you to be the sole entity to monetize the work of the other 90% of the community, but I don't think anyone has come up with a proper license to defend against that yet.
Open source indeed needs to adapt, but I don't think the source-available or open-core models we are seeing these days is the right solution. If you really want to prevent third-party entities to profit off your work you'd need to go for something like the AGPL, but that is for obvious reasons not exactly a popular choice.
> Why shouldn't this to apply to every company - including the one ostensibly shepherding the open source project?
Because that's simply not how copyrights and trademarks work. The licensor doesn't need to abide by the terms of the license, by definition. The purpose of a license is to grant rights from the licensor to the licensee.
> employing a bunch of core developers doing 10% of the work doesn't entitle you to be the sole entity to monetize the work of the other 90% of the community
Very few of these cases are 10% company / 90% community. If anything, it's usually the other way around. Not to mention the huge amount of time spent on code review and ongoing maintenance of third-party contributions.
> I don't think anyone has come up with a proper license to defend against that yet.
That wouldn't really make sense; a software license isn't going to remove rights from the licensor. More realistic solutions are things like intentionally not having a CLA (effectively preventing the project creator from relicensing) and/or reassigning copyright and trademarks to a foundation.
Why shouldn't this to apply to every company - including the one ostensibly shepherding the open source project? I would argue that employing a bunch of core developers doing 10% of the work doesn't entitle you to be the sole entity to monetize the work of the other 90% of the community, but I don't think anyone has come up with a proper license to defend against that yet.
Open source indeed needs to adapt, but I don't think the source-available or open-core models we are seeing these days is the right solution. If you really want to prevent third-party entities to profit off your work you'd need to go for something like the AGPL, but that is for obvious reasons not exactly a popular choice.