It kinda feels wrong to add a license to a simple bash script, also I can't decide on which one to use...
@lukas2511 commented on GitHub (Dec 22, 2015):
It kinda feels wrong to add a license to a simple bash script, also I can't decide on which one to use...
Problem is that due to common laws, if you don't declare a license, basically no one is even allowed to copy that file. :-(
@xtaran commented on GitHub (Dec 22, 2015):
It's anything else than simple. :-)
And for being undecided, http://choosealicense.com/ might help. :-) If you don't care at all, I recommend the [WTFPL, the Do What The Fuck You Want To Public License](http://www.wtfpl.net/). The name is more or less also the license text. ;-)
Problem is that due to common laws, if you don't declare a license, basically no one is even allowed to copy that file. :-(
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @TabTwo on GitHub (Dec 22, 2015).
Any plans to add a license to this project?
@lukas2511 commented on GitHub (Dec 22, 2015):
It kinda feels wrong to add a license to a simple bash script, also I can't decide on which one to use...
@xtaran commented on GitHub (Dec 22, 2015):
It's anything else than simple. :-)
And for being undecided, http://choosealicense.com/ might help. :-) If you don't care at all, I recommend the WTFPL, the Do What The Fuck You Want To Public License. The name is more or less also the license text. ;-)
Problem is that due to common laws, if you don't declare a license, basically no one is even allowed to copy that file. :-(
@lukas2511 commented on GitHub (Dec 22, 2015):
this one should be good enough