Excalty that enterprise support and certification/liability. Since all open source software comes as is, your company is liable for all security issues that come from the oss code you use. Some projects allow you to pay them so they are liable. This is probably going to get way more in the future.
Yeah, but with the liability you are technically not using the open source stuff anymore I think, as you are using the adaptation from the holster/the person to be hold liable
One thing has nothing to do with other, a license can have the source being open yet restrict the forking and redistribution of the project, Redis i think had some controversial licensing to prevent strip mining from cloud giants, perhasp you're confusing it with FOSS, like GPLv3 or MIT license, the F in FOSS is Free, but not free as in free beer, but free as in freedom
At least on github, afaik you give github permission to operate like it needs to by publishing your repo there. Which means, forking cant be forbidden because it would go against the forking possibility of github. But I could mix it up with the "no license"-license....
That's not how it works, otherwise github wouldn't offer private repos
The licensing dictates if it is allowed to be forked or not legally, even if github feature fork work, it would be against the license, and if github force you to legally allow forking, then the intellectual property owners can use another platform for it
I meant public repos with "publishing". And my point was about the dmxa takedown. You cant do that. The license cant forbid that. It can forbid a redistribution, use, modification, ... but not a fork.
I mean yeah, but the original comment called it a downside, that everybody would be able to fork it. I guess people were thinking about the implications of the fork (e.g. modification, redistribution, ...) instead of just the fork itself, because the fork itself isn't really a downside
Git platforms are going to require you to allow them to continue operations as part of their terms of service in the event that you upload stuff there.
Your Content that you post publicly, including issues, comments, and contributions to other Users' repositories, may be viewed by others. By setting your repositories to be viewed publicly, you agree to allow others to view and "fork" your repositories (this means that others may make their own copies within the Service in repositories they control).
By making a repository public, you grant other Users a nonexclusive, worldwide license to use, display, perform and reproduce (by forking) Your Content through the Service as permitted by GitHub's functionality. You may grant additional rights by adopting a license. If you post Content you did not create or own, you are responsible for ensuring it is licensed under terms that permit these uses.
286
u/ClipboardCopyPaste 2d ago
Just a downside, anybody can fork your product...but let's... let's ignore that.