this post was submitted on 23 May 2024
94 points (98.0% liked)
Programming
17408 readers
95 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I will get shit on for this but „rejecting everything where I cant look in the source code“ makes more sense imo from a security standpoint.
The „free“ as in everyone can put in into their software and sell it without contributing back isnt security relevant from my pov (neither do I like that ideology tbf).
In other words, you're saying it has to be specifically copyleft (which is the only kind that guarantees that all downstream users will always be able to look at the source code), not merely permissively-licensed. Sounds good to me!
I appreciate the elaborate response. The intricacies of licensing arent fluent in me and the reminder helps.
Copyleft is cool but for OPs question, I would suggest source available at least. My criterion is that I (or op for that matter) can look at the source code of this project, not everyone on every downstream project.
I‘d also distinguish between in and out licensing. If they want to make a product that is not foss, copyleft wont work so reviewing the code would be the smallest denominator imo although I would not use or recommend their software.