Software licenses try to avoid ambiguity, which results in them being rather lengthy and hard to read. Would I be okay with flippantly summarizing the gist or spirit of a license in another place (like a code file)? I don't want the summery to be binding in any way.

Something like this for instance, which refers to the actual license text at the very end?

//    legal:
// This code is free to use for any purpose.
// I don't promise this code will do anything right or nothing wrong, 
// and is given "as is", see license.txt
  • You write software? If you “summarize” you code will it do the same thing? Same with legal “code”.
    – Dale M
    Dec 2 '19 at 21:28
  • 1
    Creative Commons has an intriguing strategy: This is a human-readable summary of (and not a substitute for) the license.
    – xuhdev
    Dec 3 '19 at 3:23
  • @DaleM - This might stretch the analogy, but human readable summaries and weightless remarks are absolutely strewn through-out software as "comments", which are vital to coding.
    – Anne Quinn
    Dec 3 '19 at 15:34

Those are just comments in the code, the license is still the license. Comments in code do not effect that.

  • 1
    Or maybe they are relied on and do have a legal effect, screwing up the clarity of your license. Dec 2 '19 at 20:15
  • They don't though. The license is what you agree to.
    – Putvi
    Dec 2 '19 at 20:16

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.