Change to MIT license

[angelsix]

Why BSD 2 license? Could you change it to MIT? I would love to use this in my open source MIT projects, but don't want to have to mix multiple license types that then anyone wanting to use my code would have to then know about too.

[Taritsyn]

I would love to use this in my open source MIT projects, but don't want to have to mix multiple license types that then anyone wanting to use my code would have to then know about too.

As far as I know, if you use only assemblies (or package), then there will be no license restrictions.

[xoofx]

The BSD 2 License is almost the same to MIT. The only difference is that it is slightly more explicit in explaining when to redistribute the license readme (e.g. in case of binary vs source distribution).
You can mix BSD 2 license with MIT, as they are completely compatible.

[angelsix]

ok to be sure, if I add a nuget reference in my MIT license, where would I include the license and with what name?

[xoofx]

You should redistribute the SharpScss license.txt for example if you are developing an application and you redistribute it (and exe + all the assemblies, either on an appstore, or a desktop application...etc.). But if you are developing a nuget package that is dependent on SharpScss, you don't have to do anything. It is not your responsibility to include transitively all the licenses when someone will use your package.

[angelsix]

I have an open source project https://github.com/angelsix/dna-web I want to reference it in there. I have installers for it too, so in the installer I'll include a license. However for the github project.. do I need a license file?

[xoofx]

No you don't need if you are using nuget. If you copy the dll inside the repo then you just need to copy the license.txt as well (as you should have also to do for a MIT license btw)