4 ms·
The BSD licenses mention code and documentation together ("this software and associated documentation files") so I assume any of those would provide you the sam
by eliteraspberrie 11y ago
The BSD licenses mention code and documentation together ("this software and associated documentation files") so I assume any of those would provide you the same protection for your entire work. I don't know much about the GPL.
You could always make the source (of both code and documentation) public but non-free, and make the generated code and documentation available separately with their own liberal licenses.
By the way, did you use literate programming? I'm always curious about large programs made in that style, it's very rare.
- ISL 11y agoAlas, I'm not so formal as to do anything so beautiful as literate programming. This is perhaps just slightly higher quality than your usual physicist spaghetti code. It runs, it works, and it's reproducible. I can't figure out if the non-free "No License" option on GitHub is truly non-free. The GitHub terms of use grant the right to view and "to fork" without any clear definition of what "forking" means in that context. Is that "fork so you can see what it looks like" or "fork so you can use it and incorporate it into your own analysis without sharing"? If it's the former, I'll just throw it up on GitHub unlicensed or with an "all rights reserved" tag, as making the guts of the code visible is my highest priority. I'd be very happy to table for later the actual issue of selecting a license (and appending it to the header of files in >5 different interoperating computer languages). Thanks!