CODE LICENSE: ahenry3068

[ahenry3068]

I've been kind of remiss in putting any kind of license on my code.

Please accept this post as the terms for any other code I post on this Forum or on the X16 Discord, unless another license is explicitly included.

I hereby place all the X16 and other code I post here or on the X16 Discord under the most Permissive terms.. Essentially Public Domain. Do what you wish with it. Use it in your own project, modify it, share it or close your own modifications. You may use it in any legal way in any software on the X16 or other platform.

Thank You,
Tony.

[DragWx]

You might like the Zero-Clause BSD (0BSD) license, or the MIT No Attribution (MIT-0) license, if you ever run into a situation where you need to put the name of a more community-recognized license.

[ahenry3068]

You might like the Zero-Clause BSD (0BSD) license, or the MIT No Attribution (MIT-0) license, if you ever run into a situation where you need to put the name of a more community-recognized license.

Thank you.

[mortarm]

Please accept this post as the terms for any other code I post on this Forum or on the X16 Discord, unless another license is explicitly included.

Yeah, I'm afraid that's not gonna cut it, legally. You need to include an established license with the software. A text file of the license is sufficient.

[ahenry3068]

Please accept this post as the terms for any other code I post on this Forum or on the X16 Discord, unless another license is explicitly included.

Yeah, I'm afraid that's not gonna cut it, legally. You need to include an established license with the software. A text file of the license is sufficient.

Your not correct. The only one with any standing to sue for my code is me. If I say it's free publicly that's really all that's necessary.

[TomXP411]

Please accept this post as the terms for any other code I post on this Forum or on the X16 Discord, unless another license is explicitly included.

Yeah, I'm afraid that's not gonna cut it, legally. You need to include an established license with the software. A text file of the license is sufficient.

There's nothing in US Copyright law that specifies the method of license delivery. Copyright simply requires that people receive his permission before copying a Copyrighted work.

An open letter on the forum is a perfectly acceptable way of doing so.

That said - I strongly recommend that everyone include some sort of license and/or contact information in the Zip file with every software download. It's not required, but it's a really good idea.

[doslogo]

Imagine getting an email every time someone (Google) updates (changes terms) their license... I think placing your license in this public place is a nice idea (I wish I had thought of it, well I still can)