Add a license

[JortvD]

We need to choose a license for this repository (and all of the others). That begs the question: which license? I am personally in favor of a GPL license, as MIT has some quirks I'm not that fond of. A GPL license, however, might have the consequence that the adoption of ijo will be lessened.

[TheOtterlord]

I've been looking at choose a license, and using GPL could lead to reduced adoption? But I suppose it depends on how it is used. What parts of the MIT license do you not like/want?
I'm not really worried about people distributing closed source versions of ijo, but I suppose it is something to consider.

[JortvD]

What parts of the MIT license do you not like/want?

I'm more against the start of closed source ecosystems for ijo. Where companies, for example, create a closed source version of ijo and then start making plugins that will only work for their closed source version.

... using GPL could lead to reduced adoption?

In the case that a company or person would only use ijo because it would be able to create a close version under a MIT license.

[TheOtterlord]

Yeah, I guess that GPL is probably best then. Since closed source versions don't really contribute to the overall ecosystem and proper adoption 🤔

[TheOtterlord]

After reading about elastic search and the recent developments, I think GPL is a good fit for the project. It definitely is beneficial to have everything open.

[JortvD]

Yes interesting move indeed, but I vow to never change the license when it has been set ;).