License

[tilmanginzel]

Hi @toy,

thanks for continuing the work of Frederik. :) I would like to use the compiled binary in my Alfred 3 workflow and was wondering if you'd have any problems with that.

Do you mind adding a license to this repository so that others and me can be sure that we are allowed to use and distribute the binary with our software (with attribution to this repository)?

Thanks and best regards
Tilman :)

[toy]

Hi Tilman,

First reaction: Oh no, license question…

Normally I use MIT license for my projects, caring only about attribution and have nothing against integration of compiled binary. This project lacks a license as I'm not sure how to handle license of a public domain fork and you are the first to ask about it ;) Stackexchange seems to suggest to contact Frederik, so I'll try.

[triplef]

Hi guys, I’m the original author of blueutil. Great to see my little tool being further developed here!

@toy had emailed me about this license change. I am totally fine with changing the license of this fork to MIT. 👍

[tilmanginzel]

First reaction: Oh no, license question…

Yeah, I am sorry I had to be the one asking, but you can see it as a good sign. :)

@toy had emailed me about this license change. I am totally fine with changing the license of this fork to MIT. 👍

Hi Frederik, that's great! I will then add a compiled binary to my project and give proper attribution back to you guys. 👍

[toy]

@triplef Please have a look at #15 and tell if you want anything to be changed

[triplef]

@toy looks good, thanks! 👍

[toy]

Any strong opinion on bumping patch, minor or major version?

[tilmanginzel]

Good question. According to semver it could be seen as a patch, because it's a backwards-compatible change. Some prefer a major version for license changes though (or even a new project, but this would be a bit excessive...).

IMO you have one of the following options:

• If you think that the license change from none/public domain to MIT might have any negative or breaking impact on current users, be "safe" by using a major version change
• If you think the license change has no negative or breaking impact at all, just use minor or patch

[toy]

I came to similar conclusion. I feel that change of license doesn't introduce changes requiring major version increase, so I'll go with minor version increase (patch would be not visible enough).