3 ms·
Open Source Science Software is generally licensed under MIT or GPL to make the source available, source code inheritable, mark the artifact as a deliverable, a
by bayindirh 4y ago
Open Source Science Software is generally licensed under MIT or GPL to make the source available, source code inheritable, mark the artifact as a deliverable, and make code reviewable and encourage collaboration.
So the funding bodies can support you financially over the code you released, and other users can support you with improvements to make code more valuable and usable.
This is beyond source available, this how Free Software is designed and dreamed to work in practice.
- frutiger 4y agoYes but GGP said “instead of licensing”.
- bayindirh 4y agoI read it as "licensing in a proprietary way", or "licensing with strict copyright terms". Which is also present in some research software. You buy the source, but can't share/distribute. Only compile, customize and use.
- sfpotter 4y agoThis is the correct interpretation. Apologies for any confusion.
- tokai 4y agoI mean this in the best way, but your comment doesn't make any sense. I'm asking sfpotter what he means by releasing something OS without using licensing. I didn't ask for an overview of free software.
- bayindirh 4y agoLicensing in this context means "closed/strict licensing which doesn't provide freedoms". The code is actually licensed: https://github.com/DrTimothyAldenDavis/SuiteSparse/blob/master/LICENSE.txt https://github.com/DrTimothyAldenDavis/SuiteSparse/blob/mast...
- quietbritishjim 4y ago> Licensing in this context means "closed/strict licensing which doesn't provide freedoms". Maybe that's what the commenter meant but that's not what that language means. Open source licenses are, well, licenses, and if you use them then you're licensing your code. The L in GPL stands for license, for example.
- bayindirh 4y agoThe original commenting user verified that he/she used the term "License" as in "Strict copyright" [0]. There's no need to be pedantic over a word here. [0]: https://news.ycombinator.com/item?id=33274282 https://news.ycombinator.com/item?id=33274282
- Anon1096 4y ago"Strict copyright" doesn't make sense either. OSS licenses are just as strict as closed source ones. You can just say a "closed source license."
- bayindirh 4y agoOSS licenses are generally called "permissive", "weak copyright", "weak copyleft" and "strong copyleft" (in case of GPL family) depending on the context and nature of the license implied. "Strict/Strong Copyright" makes sense.
- quietbritishjim 4y agoJust try Googling for "weak copyright" or "strong copyright". You can see for yourself that there's no such usage like you're explaining. All the top results are about whether copyright as a general concept is, or should be, strong or weak, applied to all circumstances (proprietary and open sourced software alike and even other types of copyrightable works). Strong and weak copyleft is a different matter, those terms do make sense. Maybe that's the source of confusion here.
- deleted 4y ago[deleted]
- klooney 4y agohttps://github.com/DrTimothyAldenDavis/SuiteSparse/blob/master/LICENSE.txt https://github.com/DrTimothyAldenDavis/SuiteSparse/blob/mast... it's lgpl or gpl, which is the point of the complaint. GitHub does a ton of work to formalize license management, it's odd that copilot ignored all of that.