Consider moving binaryen (and other tools) into a different org

Per @jfbastien, I am opening a separate issue to discuss possibly moving binaryen (and other wasm tools) into their own org.

The conversation originally came up in #1340 when I asked whether any of the main contributors to these tools require the W3C's IPR protection (as opposed to licensing under something like Apache2) in order to contribute.

The W3C's contribution process is more involved than other projects, so there could be benefits to pulling these tools out into a more traditional organization.

@jfbastien replied:

To answer your question: binaryen was started early in WebAssembly's history when much of the design was in flux, and it definitely provided significant input to what will become the final WebAssembly standard. I was one of the 4 CG chairs at the time, representing Google, and advice from representative companies' standards folks + lawyers, and W3C folks, was that WebAssembly contributions which affect the design must be under the W3C umbrella and contributors who provide significant input must be CG members. Binaryen fit that description and was therefore under the WebAssembly organization.

Now that the design has settled more we could reconsider and put binaryen as well as other tools under their own organization. For example, the LLVM work now occurs directly in upstream LLVM. It remains true that significant contributions to the standard must come from CG members, but at this point tooling development doesn't influence the design as much as just get stuff working.

So I'm opening this issue to track it 😄

@jfbastien mentioned that this might be added to the agenda for the next CG video call, which I'd quite appreciate.

Start by reading issue #1340 and the linked 2018 CG meeting materials, then review the discussion here about W3C IPR requirements and moving Binaryen and other WebAssembly tools. The issue is complete only when the organization and contribution-process question has a decided outcome; no implementation files or tests are identified.