search

PentiaLabs / generator-helix

Generate Helix compliant solutions with Yeoman.
MIT License
40 stars 22 forks source link

Add licence file and license block to readme #55

Closed Saturate closed 7 years ago

Saturate commented 7 years ago

We should have a more clear license, without a license file and statement in the readme it's a bit hard.

Would recommend MIT or GPL.

jsurland commented 7 years ago

Sure about GPL? GPL can be problematic in some scenarios. MIT is my suggestion.

Saturate commented 7 years ago

I guess MIT is the best one, as it's simple and allows . However some might say that GPL would fit this project and still allow for it's use.

I would just go MIT, and call it a nice day. However I guess we need to think a bit about it, take a look at https://choosealicense.com/.

I don't know how is responsible for this, but we need to add one soon :-)

ronnidc commented 7 years ago

What's the big difference between the existing ISC license referenced in package.json and the MIT?

As far as I can tell the only difference is that ISC is written in shorter and fewer sentences but they both share the same meaning.

I do agree that a license file should be included in the repo.

jsurland commented 7 years ago

If you at ANY time make a product, that uses any of a GPL license you have to give anyone the whole source of your product, if they ask. It's a nasty license for product creators.

Saturate commented 7 years ago

MIT as well @jsurland is my vote, but again I have no idea who can decide this? Maybe it's you :-)