-
You're creating a new repo and they are asking if you want to include a license?
They have a good page that explains the gist of each licence, but you absolutely do not have to include one if you don't want to.
I typically use the MIT license, one of the more permissive and relaxed licenses, because I don't care what people do with my code and I've certainly gained a lot more from the open source ecosystem than I'll ever be able to contribute back.
cyclotron3k-
You're creating a new repo and they are asking if you want to include a license?
They seem to recommend it? The link you post links to another which explains no licence = issues.
I've certainly gained a lot more from the open source ecosystem than I'll ever be able to contribute back.
This will be my case too. As unlikely as it is I would be a bit miffed if someone lifts the code, makes a tidy profit from it then somehow prevents others doing the same. I'm probably overthinking things.
rhb
I can't get past licensing. Seems very complicated to choose one. I might skip and go without for now.
In a nutshell I'm happy for anyone else to use the code, just feel like they should not make mega£££ from it. Is that not in the spirit of things?