Suggestion: add license

[masterwolf-git]

Hello.

This is a nice piece of software. May I suggest you put a license on it?
I suggest you go with the GPL 2.0, as this would make grabbing the code to make some closed source thing and not reward you at all, neither let you use it, forbidden, but if you have a better one in mind, your decision.

Regards!

[yurikhan]

The root of the repository already contains files gpl-2.0.txt and gpl-3.0.txt, though neither the README nor headers in each file explicitly say those licenses govern the project code.

It would be a good idea to fix that; in addition, when releasing under existing versions of GPL, it is customary to either say “or any other version” or explictly disallow future versions of the license.

@Swordfish90

[masterwolf-git]

I like the idea of being able to make appliances with the code, say, a terminal that runs your software in a really barebones wayland compositor and only sshs away to something else, that would be really cool. The GPL 3 makes it harder to do because you need to have user changeable bootloaders, and this would make it difficult to pull out in non UEFI ARM (raspberry pi?)... apart from that i really don't see any reason not to use the GPL 3.0, but then it would be cleaner to just use GPL 3.0 instead.

And about gpl-2.0.txt and gpl-3.0.txt, I did not see them, sorry. In GitHub if you name the license "LICENSE" it appears on the sidebar, it helps with visibility.