Sami Vaarala

@martinetd Let me know how you want to proceed :) No worries about the delay, I'm struggling to find time myself right now also.

If you are OK with Docker, the easiest approach is to use the docker shell: ``` $ make docker-images $ make docker-shell-wd ``` This runs a shell inside a docker...

@braindigitalis Could you rebase to master, it should fix the failing checks? There are a couple of small things that come to mind from the diff (still worth merging as...

Could you elaborate why including the copyright notice is a problem? It's typically included in some About dialog or similar, which is minimally intrusive.

I know, I was just asking why it's a problem including the license. It is, after all, the only thing that is asked in return for free software.

I originally chose the MIT license without too much thought. It was used by Lua, which has wide acceptance, and since Duktape targets many of the same usage scenarios it...

Assuming the project license was changed, the main issues would be: 1. Deciding on what license(s) to use. If the license is changed now, I would prefer it to be...

MIT licensed libraries are used quite widely (including Lua) so I'm not aware of any actual problems with that. Also embedded Linux distributions often include MIT licensed packages.

@mloskot Re: the license change process, I agree it would be nice to have flexibility. But, in my view it should be made clear beforehand in CONTRIBUTING, e.g. that a...

@grafikrobot The most permissive license would obviously be "public domain". WTFPL (http://www.wtfpl.net/) is as close as you get to public domain while still calling it a license, so it might...