Choose a new license

[subhramit]

One of the points raised during a discussion on #60 was that we wish to solve the issue for enterprise Redis (and not just oss), and in fact, we expect most users to be from that faction.

However, our LGPL license is a blocker for closed source/propieratory bodies to utilize our library due to its "copyleft" clause.

The action item would be to choose a new license, such as MIT or Apache 2.0 (for stronger attribution).

A great resource - https://choosealicense.com/licenses/

More notes - even though LGPL allows larger bodies of work (except libraries) to be kept closed source/proprietary even if they use an LGPL-licensed library, it requires sharing the object (.o) files of the application to its users (which the closed source bodies are usually not comfortable with) for purposes of auditing, if the library is used via static linking. This is not a problem in the case of dynamic linking. Go has a specific problem with LGPL 2.1 as it bundles and compiles everything statically by default.

[subhramit]

Notes on methodology of change of license:

1. The change must be made to the LICENSE file with a signed commit (git commit -s -m ...)
2. A new release has to be made adopting that license.
3. Users (if any) have to be notified (explicitly declaring in the release changelog should be sufficient)

[bburli-craft]

Thank you @subhramit for raising this issue. Apahe looks good to me. @a3y3 @hthuwal What do you think?

[a3y3]

The justification makes sense to me, but I've somehow never paid a lot of attention to licenses. I figured this was as good a time to start as any, so I looked it up. It looked like LGPL should've worked for us but golang statically links everything so it won't.

That said, I think the MIT license should work!