Add license files
Hello! I was looking over the repo and realized that there aren't any license files:
~The witx tool has a license listed in the cargo.toml, but we should include a license file as well.~
I'd like to add a license for the entire repo if possible, but especially for the docs and witx data files themselves.
I'm not aware of if there's any formal process required for this or if everything in the WebAssembly org is assumed to be under a certain license.
Apache 2 seems reasonable to me though -- it's what witx and some other projects in the WebAssembly org are using. If that sounds reasonable to you all, I can make a pull request to add it!
edit:
looks like there's been a need to use a separate documentation license in the past https://github.com/WebAssembly/spec/pull/496. That raises the question of whether witx is documentation or source code...
edit2: not sure how I missed the license file on witx -- thanks for the correction!
there are some license files: https://github.com/WebAssembly/WASI/blob/master/tools/witx/LICENSE there may be more that I missed.
Yes, the witx library already has a license. For the witx files themselves, I'm seeking input on the proper way to proceed here.
Has anybody looked at this lately?
I'm working on packaging wasmtime for Fedora Linux, which includes a copy of the witx files from this repository, but inclusion of the packages is blocked for now, because it is not specified how the files in this project are licensed.
I'm pretty sure witx files aren't copyrightable in any legal domain, because of how rigidly structured they are, and in the US specifically they seem to quite clearly fall under fair use, but to eliminate all uncertainty I'd propose we explicitly license them under CC0 / public domain.
I'm pretty sure
witxfiles aren't copyrightable in any legal domain, because of how rigidly structured they are, and in the US specifically they seem to quite clearly fall under fair use, but to eliminate all uncertainty I'd propose we explicitly license them under CC0 / public domain.
Could we consider a different license such as MIT-0? There's been a change in classification of CC0 to only be used for content and not code. The use of CC0 for code will prevent us from being able to officially package in Fedora. See https://lists.fedoraproject.org/archives/list/[email protected]/thread/RRYM3CLYJYW64VSQIXY6IF3TCDZGS6LM/ for details.