Nice post! I’d like to put a copy of the code on Github, but I don’t see a license anywhere in the directory (or mentioned in the files). May I assume it’s generally intended to be Open Source and I can do this?
Cheers! I’ve added the text of the “unlicence” https://choosealicense.com/licenses/unlicense/ to the script file “toyscript.txt”. Can you update the file on github? (I notice you renamed the script file; that’s fine).
You should provide some more explicit license, if you don’t want to risk headaches for others later. “yes [It’s generally intended to be Open Source]” may be enough reassurance to copy the code once, but “yes, you can have it under the new BSD (or LGPL2.1+, or whatever) license” would be useful to have in writing in the repository in case others want to create derived works down the road.
Nice post! I’d like to put a copy of the code on Github, but I don’t see a license anywhere in the directory (or mentioned in the files). May I assume it’s generally intended to be Open Source and I can do this?
yes, go ahead!
Thanks! It’s up.
Cheers! I’ve added the text of the “unlicence” https://choosealicense.com/licenses/unlicense/ to the script file “toyscript.txt”. Can you update the file on github? (I notice you renamed the script file; that’s fine).
Sorry I’m two weeks late, but the text of the unlicense has been added. Thank you!
You should provide some more explicit license, if you don’t want to risk headaches for others later. “yes [It’s generally intended to be Open Source]” may be enough reassurance to copy the code once, but “yes, you can have it under the new BSD (or LGPL2.1+, or whatever) license” would be useful to have in writing in the repository in case others want to create derived works down the road.
Thanks very much for creating this!
Added the text of the “unlicence” https://choosealicense.com/licenses/unlicense/ to the script file “toyscript.txt”.