Code of Conduct document identifies that reports will be handled by this team but does not identify who makes it up. Is this handled by David Bryant who is identified as the Compliance Officer in the Whistleblower Policy or someone else?

Proposal to Create a Component Model Go project

This document is a proposal to create a go monorepo as a formal Hosted Project under the auspices of the TSC of the Bytecode Alliance, as specified in the TSC Charter.

The proposed repo will be: github.com/bytecodealliance/cm-go

Project Summary

Describe the project and its goals. Target 1-2 paragraphs.

The SIG Guest Languages Working Group desires a repository to collaborate around tooling and shared go modules to improve the ergonomics around Go and Wasm CM + WASI Preview 2.

Repo: github.com/bytecodealliance/cm-go
The intention is to create a go vanity url: https://go.bytecodealliance.org/

This will allow for modules that we expect to be vendored easily like to upstream tinygo and big go. For example only: go.bytecodealliance.org/wasi/http

Existing Resources

The tooling around Go is nascent where most of the work is underway within POC in the TinyGo repository and other various projects that can be combined to improve go development with components. The idea is to join efforts across some of these into the go project.

• https://github.com/bytecodealliance/wit-bindgen go generator that relies on CGO
• https://github.com/ydnar/wasm-tools-go

Governance Summary

This project will be governed and maintained by SIG Guest Languages - Go Subgroup. There are two chairs for this subgroup representing two different Bytecode Alliance member organizations.

Software Development Process

1-3 paragraphs explaining how the project uses pull requests, issue maintenance, LGTM policy, release management, and security processes. Emphasize how code quality is ensured.

This project needs to be bootstrapped so there are no existing process today. During bootstrapping, this project will follow all hosted project requirements.

Alignment with Bytecode Alliance Mission and Goals

Bytecode Alliance projects represent the mission and goals of the Bytecode Alliance itself.
We understand that as a Bytecode Alliance project, our project must adhere to the TSC Charter and other governing documents (such as the Security Policies and IP Policy).
As a Bytecode Alliance project, our project's source code and other pieces of intellectual property will be assigned to the Bytecode Alliance.

We understand and agree that:

• All code for this project must be under the Apache v2 License with the LLVM exception, unless an exception is required for compliance with existing licensing, and granted by the Bytecode Alliance's board of directors per IP Policy §4. If our code is not already licenses accordingly, we will take the necessary steps to correct this prior to becoming a Bytecode Alliance Project.
• We will comply with the Security Policies.
• Project name, trademarks, logos, wordmarks, and other intellectual property other than source code and documentation copyright is assigned to Bytecode Alliance per the IP Policy.
• Social media handles, GitHub repository access, and other relevant communication and coordination platforms will be overseen by Bytecode Alliance. Administrative/Owner permissions will be granted to the Bytecode Alliance for all such accounts.
• We will abide by the definition of a project as set forth in the TSC Charter.
• This project must remain under active development or maintenance, or it may be archived by the Bytecode Alliance.
• This project may be reviewed from time to time by the TSC, and project maintainers will assist with this review process.
• Project members will be able to participate in Bytecode Alliance governance, as specified in the TSC Charter and other governing documents.

Supporting Members

The following individuals support the creation of Bytecode Alliance's go project:

• Randy Reddig (Fastly)
• Damian Gryski (Fastly)
• Jiaxiao Zhou (Mossaka) (Microsoft)
• Achille Roussel (Stealth Rocket)
• Bailey Hayes (Cosmonic)

Proposal to Create wasi-virt

This document is a proposal to create wasi-virt as a formal (Hosted) Project under the auspices of the TSC of the Bytecode Alliance, as specified in the TSC Charter.

Project Summary

WASI Virt is a project that provides many different adapters that are simply composed. Similar to the wasm-tools project, this project will be in a monorepository and contain many different implementations. Individual virtualization adapters may need to work in concert with others, e.g. a virtualized blobstore may use a virtualized filesystem.

A key feature of the proposed WebAssembly Component Model is virtualizability of components, see the link-time virtualization example. Virtualized components will aid the WebAssembly community in enhancing WebAssembly's key value propositions of embeddability and language neutrality.

Existing Resources

• wasi-vfs

Governance Summary

This project will begin with maintainers from the wasi-vfs project and additionally add maintainers of two other Bytecode Alliance projects, @peterhuene (cargo component) and @guybedford (jco). This representation from multiple organizations and language ecosystems will be a key component of this project.

Software Development Process

The project will meet the passing criteria for the OpenSSF best practices badge. Pull requests, issues, CI, and release management will be performed via GitHub.

Alignment with Bytecode Alliance Mission and Goals

Bytecode Alliance projects represent the mission and goals of the Bytecode Alliance itself.
We understand that as a Bytecode Alliance project, our project must adhere to the TSC Charter and other governing documents (such as the Security Policies and IP Policy).
As a Bytecode Alliance project, our project's source code and other pieces of intellectual property will be assigned to the Bytecode Alliance.

We understand and agree that:

• All code for this project must be under the Apache v2 License with the LLVM exception, unless an exception is required for compliance with existing licensing, and granted by the Bytecode Alliance's board of directors per IP Policy §4. If our code is not already licenses accordingly, we will take the necessary steps to correct this prior to becoming a Bytecode Alliance Project.
• We will comply with the Security Policies.
• Project name, trademarks, logos, wordmarks, and other intellectual property other than source code and documentation copyright is assigned to Bytecode Alliance per the IP Policy.
• Social media handles, GitHub repository access, and other relevant communication and coordination platforms will be overseen by Bytecode Alliance. Administrative/Owner permissions will be granted to the Bytecode Alliance for all such accounts.
• We will abide by the definition of a project as set forth in the TSC Charter.
• This project must remain under active development or maintenance, or it may be archived by the Bytecode Alliance.
• This project may be reviewed from time to time by the TSC, and project maintainers will assist with this review process.
• Project members will be able to participate in Bytecode Alliance governance, as specified in the TSC Charter and other governing documents.

Supporting Members

The following individuals support the creation of wasi-virt:

• Guy Bedford (Fastly)
• Bailey Hayes (Cosmonic)
• Peter Heune (Fastly)
• Yuta Saito (GoodNotes)

Proposal to Create componentize-py

This document is a proposal to create componentize-py as a formal (Hosted) Project under the auspices of the TSC of the Bytecode Alliance, as specified in the TSC Charter.

Project Summary

componentize-py is a project to create components using the Python programming language, analogous to how jco componentize creates components using JavaScript. It currently resides at https://github.com/dicej/componentize-py/ and is published to PyPI at https://pypi.org/project/componentize-py/. In addition to supporting guest code written in pure Python, it supports native extensions written in C, C++, and other native languages via emulated dlopen/dlsym functions. We aim to make this tool the easiest, most efficient way to build components using Python.

This project has been developed with the advice and assistance of the members of the Python subgroup of the Guest Languages SIG, including @brettcannon, who currently maintains the CPython WASI port on which componentize-py is based.

Governance Summary

This project will begin with @dicej (Joel Dice, Fermyon) as the primary maintainer, with informal assistance from the Guest Languages SIG Python subgroup. By making this a hosted Bytecode Alliance project, we hope to attract additional contributors going forward.

Software Development Process

The project will meet the passing criteria for the OpenSSF best practices badge. Pull requests, issues, CI, and release management will be performed via GitHub.

Alignment with Bytecode Alliance Mission and Goals

Bytecode Alliance projects represent the mission and goals of the Bytecode Alliance itself.
We understand that as a Bytecode Alliance project, our project must adhere to the TSC Charter and other governing documents (such as the Security Policies and IP Policy).
As a Bytecode Alliance project, our project's source code and other pieces of intellectual property will be assigned to the Bytecode Alliance.

We understand and agree that:

• All code for this project must be under the Apache v2 License with the LLVM exception, unless an exception is required for compliance with existing licensing, and granted by the Bytecode Alliance's board of directors per IP Policy §4. If our code is not already licensed accordingly, we will take the necessary steps to correct this prior to becoming a Bytecode Alliance Project.
• We will comply with the Security Policies.
• Project name, trademarks, logos, wordmarks, and other intellectual property other than source code and documentation copyright is assigned to Bytecode Alliance per the IP Policy.
• Social media handles, GitHub repository access, and other relevant communication and coordination platforms will be overseen by Bytecode Alliance. Administrative/Owner permissions will be granted to the Bytecode Alliance for all such accounts.
• We will abide by the definition of a project as set forth in the TSC Charter.
• This project must remain under active development or maintenance, or it may be archived by the Bytecode Alliance.
• This project may be reviewed from time to time by the TSC, and project maintainers will assist with this review process.
• Project members will be able to participate in Bytecode Alliance governance, as specified in the TSC Charter and other governing documents.

Supporting Members

The following individuals support the creation of componentize-py:

• Joel Dice (Fermyon)
• Till Schneidereit (Fermyon)
• Kyle Brown (SingleStore)