Create LICENSE

[Maniues]

Add MIT license (based on license of Haxe standard library)

[Maniues]

@Simn @ncannasse ?

[Simn]

Is the MIT license actually compatible if we pull the documentation for packages like js.html from other sources? I have no idea how that works in such cases.

[Maniues]

@Simn there are licenses like CC-BY-SA for some MDN docs or something. Haxelib documentation should be available under MIT license. Any other packages can have their own license. I can check (or at least try) what other licenses are, but you can just add information "All works by Haxe Foundation" for the MIT license.

[Maniues]

I found that when there is a CC-BY-SA license (for MDN docs), the CC-BY-SA license is available from the web view and in XML file e.g. https://api.haxe.org/js/html/AbortController.html

[Maniues]

I don't know under which license are flash XMLs, but you should provide at least a copyright note.
And Java packages (if they are taken from the OpenJDK source as Javadoc) are under GPL+CE.

This repo needs a fix, because there may be a copyright violation.

[Simn]

Hmm yes, I thought this repo only had the generator code but with the XMLs being here too I agree this should be addressed...

... somehow

[Maniues]

@Simn I can assist with this, but please note that there are other repositories without a license as well. I hope you can help address those too.

VERY IMPORTANT:
https://github.com/HaxeFoundation/haxe-evolution
https://github.com/HaxeFoundation/format

IMPORTANT (in descending order of priority, in my opinion):
https://github.com/HaxeFoundation/haxe.org
https://github.com/HaxeFoundation/code-cookbook (this one might be challenging due to many contributors)
https://github.com/HaxeFoundation/nekovm.org
https://github.com/HaxeFoundation/haxedevelop.org
https://github.com/HaxeFoundation/summit.haxe.org
https://github.com/HaxeFoundation/staging.summit.haxe.org

[Maniues]

@Simn I can assist with this, but please note that there are other repositories without a license as well. I hope you can help address those too. [...]

#23 (comment)

@Simn @ncannasse Would you like to comment on this somehow?