3 ms·
Would you mind adding a license to the code (e.g., Apache 2.0)? GitHub's TOS says that without one, code is considered "all rights reserved" -- putting any user
by profquail 14y ago
Would you mind adding a license to the code (e.g., Apache 2.0)? GitHub's TOS says that without one, code is considered "all rights reserved" -- putting any users on shaky legal ground.
Very cool (and practical!) project though.
- _yosefk 14y agoMy README.md says the code is "free" as in "do whatever you want with it" - isn't it good enough? As in, does the license have to be in some specially-named file or what-not?
- profquail 14y agoUnfortunately, I don't think "do whatever you want with it" is specific enough for the lawyers of the world ;) The license doesn't need to be a specially-named file, though most people use something sensible like 'license.txt' or 'LICENSE'. For example, here's one of my in-progress hobby projects: https://github.com/jack-pappas/fsharp-tools https://github.com/jack-pappas/fsharp-tools The Apache 2.0 license is a "do whatever you want with it" license (i.e., a permissive license).
- _yosefk 14y agoOK; I kind of thought WTFPL was a good enough license and mine was pretty much similar except for the F part. Since I got 3 different people asking for a license, I might as well find one. I'd like something really permissive that also lets you strip the thing and doesn't have to be at the top of every file and doesn't require to give credit... Something that lets you do whatever you want to.
- _yosefk 14y agoOK, so I picked the 2-clause FreeBSD license for brevity; hope this helps.
- deleted 14y ago[deleted]