hraban
commented
5 years ago Hi all,
A comment on this issue is long overdue! Here goes.
I won't lie: I'm not a fan of the MIT license. I prefer the GPL, specifically its latest version the AGPLv3.
There are two main copyright holders to this codebase: Ravelin (the company), and me (an independent contributor, after I left Ravelin). All of my contributions up to and including 104f7eb1f703c27b50d0416220c0e9200d7f30c4 have their copyright assigned to Ravelin. Whatever they choose to do with that, be it MIT or GPL or no license i.e. all rights reserved: that's up to them.
Every change after that, contributed by me, I hereby release under AGPLv3. Once Ravelin have decided what they want to do with the rest, I can either fork and relicense, or just leave it as is. There are also two patches by Kai and Douglas, but you could probably cherry-pick those out, or send them an e-mail (see AUTHORS file).
Sorry to disappoint you in your choice of license, I know the MIT is appealing for companies. But if you give it a chance, the AGPL might grow on you. It is far more permissive to users than people give it credit for. Unless you want to repackage this into a closed source SaaS, you should be free to do as you please.
Best wishes!
As mentioned in #30 we'd like to build upon your script. To do so it would be nice to know if we're allowed to do so and under what circumstances.
To make things as easy as possible for you, here's a standard MIT license with your details ready to merge - if that's what you want. Please double check!