Is this generally considered a truism? Has about zero influence on me, or with director level decision makers at companies I've worked with.
Is this generally considered a truism? Has about zero influence on me, or with director level decision makers at companies I've worked with.
For myself, I only contribute to FOSS just because it is FOSS. If I know it won't be FOSS in the future, I wouldn't contribute to it.
I'm not interested in spending my time working for free for some company if I think they'll end up saying "Hey, actually, this thing you've contributed to, we've decided not everyone should equally be able to run this, so it won't be FOSS anymore, but thanks for the help".
> or with director level decision makers at companies I've worked with
That makes sense. I don't think there is a ton of "director level decision makers" people who are actually involved in writing FOSS on a day to day basis, and also aren't the ones carrying the ecosystem on their back.
The OSS Community is full of projects that are both immensely popular and yet maintained by individuals or very small numbers of contributors.
Thats nice but realistically paid labor gets more done than free labor.
A lot of FOSS dies through neglect that wouldnt happen if someone was paid to work on it.
For which a business model is required.
Why is that "realistic" while FOSS maintainers working on software for the love of FOSS isn't realistic?
Not too long ago, the only ones working on FOSS were unpaid developers, at all.
It isn't just Hashicorp that could relicense all of their products from now forward - you could too, for your own personal editions.
So, mostly no need to add the F to OSS when talking about this particular danger. Although moving to later GPLs has definitely upset people in the past, moving to proprietary (or ideosyncratic) licensing is different. The disputes about moving to later GPLs are about what code people will be forced to share in order to continue using the software in the way they're accustomed to, not about making competition a license violation.
The fact that hasicorp changed their license has precisely zero impact on me using OpenSSL in my next project.
I think the key problem word is "community". 99.999% of OSS users are not in any concept of "community". They just run software. Firefox users aren't a "community" - they are just people browsing the Web.
So no, companies can change to BSL licenses all day and you can count all the people in the world who care in one HN thread.
I'm at the point where I will not contribute to projects with copyright assignment, especially those under more restrictive licenses like GPLv3 or AGPLv3.
It is a sign of a person or organization which has not figured out how they want to make their money, and wants to reserve the ability to take someone else's good idea.
That doesn't mean I wouldn't _use_ such software, but I look at it more as a piece of software where the installer is instead potentially leveraging CMake or autotools. There's rarely value in trying to participate in such a "community", which also tends to push further in the project being more of "published source" rather than a collaboratively driven effort.
Of course, a piece of free software means that I suddenly could lose future support, and software consuming free services means I could lose current support rapidly and even be potentially strong-armed into commercial licensing as a result.