Missing project LICENSE

[lucioveloso]

As more people are using the project, it's important to have a LICENSE.md file. Github already provides templates for most common licensing model (https://help.github.com/en/articles/licensing-a-repository).

Given that I'd love to hear from you (@amnk) your thoughts about it and find out which license model should applicable here =)

Those articles can be also useful to help to take a decision: https://github.blog/2015-03-09-open-source-license-usage-on-github-com/ (old but good) https://resources.whitesourcesoftware.com/blog-whitesource/top-open-source-licenses-trends-and-predictions

[amnk]

@lucioveloso oh, this is big. I never actually cared about them (unfortunately), but will evaluate links you send (thanks for them) and post my thoughts here.

[lucioveloso]

What I mean is not actually write down a new license from scratch. It's just to decide among one of the most common, like GPL, MIT, APACHE or something like that and add the file into the repo. Currently we have no information and majority people can believe they can use it for any purpose and in any way (what is not necessarily a problem). I think with a license, if the idea is keep it open/free, it will just make it formal. =)

[cory-signalfx]

👍 to this idea, a license would be great!

[clarketm]

👍 for license! @amnk – I can send a PR if you decide what license you want.