Skip to content

Secure, Fast, and Extensible Sandbox runtime for AI agents.

docs(governance): publish AAIF charter and consolidate project policies (#2490)

Sky93c27741de6f
diff --git a/CHARTER.md b/CHARTER.md
new file mode 100644
index 000000000..528dd3fbb
--- /dev/null
+++ b/CHARTER.md
@@ -0,0 +1,77 @@
+<!-- Transcribed from OpenSandbox Technical Charter FINAL 10-20-2026.pdf. Only formatting, page numbers, and DocuSign envelope headers have been omitted or adapted. -->
+
+# Technical Charter (the “Charter”) for OpenSandbox a Series of LF Projects, LLC
+
+**Adopted October 20, 2026**
+
+This Charter sets forth the responsibilities and procedures for technical contribution to, and oversight of, the OpenSandbox open source project, which has been established as OpenSandbox a Series of LF Projects, LLC (the “Project”). LF Projects, LLC (“LF Projects”) is a Delaware series limited liability company. All contributors (including committers, maintainers, and other technical positions) and other participants in the Project (collectively, “Collaborators”) must comply with the terms of this Charter.
+
+## 1. Mission and Scope of the Project
+
+- **a.** The mission of the Project is to develop a vendor-neutral, open-source sandboxed execution platform for AI agents — supplying the isolated, policy-controlled runtime environment where AI-generated code, coding agents, browser agents, and evaluation workloads can safely run, with unified lifecycle APIs, multi-language SDKs, and MCP integration that any agent framework can build on without reinventing its own isolation and execution layer.
+- **b.** The scope of the Project includes collaborative development under the Project License (as defined herein) supporting the mission, including documentation, testing, integration and the creation of other artifacts that aid the development, deployment, operation or adoption of the open source project.
+
+## 2. Technical Steering Committee
+
+- **a.** The Technical Steering Committee (the “TSC”) will be responsible for all technical oversight of the open source Project.
+- **b.** The TSC voting members are initially the Project’s Maintainers. At the inception of the project, the Maintainers of the Project will be as set forth within the “CONTRIBUTING” file within the Project’s code repository. The TSC may choose an alternative approach for determining the voting members of the TSC, and any such alternative approach will be documented in the CONTRIBUTING file. Any meetings of the Technical Steering Committee are intended to be open to the public, and can be conducted electronically, via teleconference, or in person.
+- **c.** TSC projects generally will involve Contributors and Maintainers. The TSC may adopt or modify roles so long as the roles are documented in the CONTRIBUTING file. Unless otherwise documented:
+ - **i.** Contributors include anyone in the technical community that contributes code, documentation, or other technical artifacts to the Project;
+ - **ii.** Maintainers are Contributors who have earned the ability to modify (“commit”) source code, documentation or other technical artifacts in a project’s repository; and
+ - **iii.** A Contributor may become a Maintainer by a majority approval of the TSC. A Maintainer may be removed by a majority approval of the TSCs.
+- **d.** Participation in the Project through becoming a Contributor and Maintainer is open to anyone so long as they abide by the terms of this Charter.
+- **e.** The TSC may (1) establish work flow procedures for the submission, approval, and closure/archiving of projects, (2) set requirements for the promotion of Contributors to Maintainer status, as applicable, and (3) amend, adjust, refine and/or eliminate the roles of Contributors, and Maintainer, and create new roles, and publicly document any TSC roles, as it sees fit.
+- **f.** The TSC may elect a TSC Chair, who will preside over meetings of the TSC and will serve until their resignation or replacement by the TSC. The TSC Chair, or any other TSC member so designated by the TSC, will serve as the primary communication contact between the Project and Agentic AI Foundation (AAIF), a directed fund of The Linux Foundation.
+- **g.** Responsibilities: The TSC will be responsible for all aspects of oversight relating to the Project, which may include:
+ - **i.** coordinating the technical direction of the Project;
+ - **ii.** approving project or system proposals (including, but not limited to, incubation, deprecation, and changes to a sub-project’s scope);
+ - **iii.** organizing sub-projects and removing sub-projects;
+ - **iv.** creating sub-committees or working groups to focus on cross-project technical issues and requirements;
+ - **v.** appointing representatives to work with other open source or open standards communities;
+ - **vi.** establishing community norms, workflows, issuing releases, and security issue reporting policies;
+ - **vii.** approving and implementing policies and processes for contributing (to be published in the CONTRIBUTING file) and coordinating with the series manager of the Project (as provided for in the Series Agreement, the “Series Manager”) to resolve matters or concerns that may arise as set forth in Section 7 of this Charter;
+ - **viii.** discussions, seeking consensus, and where necessary, voting on technical matters relating to the code base that affect multiple projects; and
+ - **ix.** coordinating any marketing, events, or communications regarding the Project.
+
+## 3. TSC Voting
+
+- **a.** While the Project aims to operate as a consensus-based community, if any TSC decision requires a vote to move the Project forward, the voting members of the TSC will vote on a one vote per voting member basis.
+- **b.** Quorum for TSC meetings requires at least fifty percent of all voting members of the TSC to be present. The TSC may continue to meet if quorum is not met but will be prevented from making any decisions at the meeting.
+- **c.** Except as provided in Section 7.c. and 8.a, decisions by vote at a meeting require a majority vote of those in attendance, provided quorum is met. Decisions made by electronic vote without a meeting require a majority vote of all voting members of the TSC.
+- **d.** In the event a vote cannot be resolved by the TSC, any voting member of the TSC may refer the matter to the Series Manager for assistance in reaching a resolution.
+
+## 4. Compliance with Policies
+
+- **a.** This Charter is subject to the Series Agreement for the Project and the Operating Agreement of LF Projects. Contributors will comply with the policies of LF Projects as may be adopted and amended by LF Projects, including, without limitation the policies listed at https://lfprojects.org/policies/.
+- **b.** The TSC may adopt a code of conduct (“CoC”) for the Project, which is subject to approval by the Series Manager. In the event that a Project-specific CoC has not been approved, the LF Projects Code of Conduct listed at https://lfprojects.org/policies will apply for all Collaborators in the Project.
+- **c.** When amending or adopting any policy applicable to the Project, LF Projects will publish such policy, as to be amended or adopted, on its web site at least 30 days prior to such policy taking effect; provided, however, that in the case of any amendment of the Trademark Policy or Terms of Use of LF Projects, any such amendment is effective upon publication on LF Project’s web site.
+- **d.** All Collaborators must allow open participation from any individual or organization meeting the requirements for contributing under this Charter and any policies adopted for all Collaborators by the TSC, regardless of competitive interests. Put another way, the Project community must not seek to exclude any participant based on any criteria, requirement, or reason other than those that are reasonable and applied on a non-discriminatory basis to all Collaborators in the Project community.
+- **e.** The Project will operate in a transparent, open, collaborative, and ethical manner at all times. The output of all Project discussions, proposals, timelines, decisions, and status should be made open and easily visible to all. Any potential violations of this requirement should be reported immediately to the Series Manager.
+
+## 5. Community Assets
+
+- **a.** LF Projects (or an associated hosting entity) will hold title to all trade or service marks used by the Project (“Project Trademarks”), whether based on common law or registered rights. Project Trademarks will be transferred and assigned to LF Projects (or, where applicable, the associated hosting entity) to hold on behalf of the Project. Any use of any Project Trademarks by Collaborators in the Project will (a) either be (i) in a way that constitutes fair use or (ii) in accordance with the license from LF Projects to the Project and the applicable trademark usage guidelines and (b) inure to the benefit of LF Projects (or the associated hosting entity).
+- **b.** The Project will, as permitted and in accordance with such license from LF Projects, develop and own all Project GitHub and social media accounts, and domain name registrations created by the Project community.
+- **c.** Under no circumstances will LF Projects be expected or required to undertake any action on behalf of the Project that is inconsistent with the tax-exempt status or purpose, as applicable, of the Joint Development Foundation or LF Projects, LLC.
+
+## 6. General Rules and Operations.
+
+- **a.** The Project will:
+ - **i.** engage in the work of the Project in a professional manner consistent with maintaining a cohesive community, while also maintaining the goodwill and esteem of LF Projects, Joint Development Foundation and other partner organizations in the open source community; and
+ - **ii.** respect the rights of all trademark owners, including any branding and trademark usage guidelines.
+
+## 7. Intellectual Property Policy
+
+- **a.** Collaborators acknowledge that the copyright in all new contributions will be retained by the copyright holder as independent works of authorship and that no contributor or copyright holder will be required to assign copyrights to the Project.
+- **b.** Except as described in Section 7.c., all contributions to the Project are subject to the following:
+ - **i.** All new inbound code contributions to the Project must be made using Apache License, Version 2.0, available at http://www.apache.org/licenses/LICENSE-2.0 (the “Project License”).
+ - **ii.** All new inbound code contributions must also be accompanied by a Developer Certificate of Origin (http://developercertificate.org) sign-off in the source code system that is submitted through a TSC-approved contribution process which will bind the authorized contributor and, if not self-employed, their employer to the applicable license;
+ - **iii.** All outbound code will be made available under the Project License.
+ - **iv.** Documentation will be received and made available by the Project under the Creative Commons Attribution 4.0 International License (available at http://creativecommons.org/licenses/by/4.0/).
+ - **v.** The Project may seek to integrate and contribute back to other open source projects (“Upstream Projects”). In such cases, the Project will conform to all license requirements of the Upstream Projects, including dependencies, leveraged by the Project. Upstream Project code contributions not stored within the Project’s main code repository will comply with the contribution process and license terms for the applicable Upstream Project.
+- **c.** The TSC may approve the use of an alternative license or licenses for inbound or outbound contributions on an exception basis. To request an exception, please describe the contribution, the alternative open source license(s), and the justification for using an alternative open source license for the Project. License exceptions must be approved by a two-thirds vote of the entire TSC.
+- **d.** Contributed files should contain license information, such as SPDX short form identifiers, indicating the open source license or licenses pertaining to the file.
+
+## 8. Amendments
+
+- **a.** This charter may be amended by a two-thirds vote of the entire TSC and is subject to approval by LF Projects.
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 3f7d585cc..391e2ef9c 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -12,8 +12,11 @@ Thank you for your interest in contributing to OpenSandbox! This guide will help
- [Coding Standards](#coding-standards)
- [Testing Guidelines](#testing-guidelines)
- [Submitting Contributions](#submitting-contributions)
+- [Project Roles and Technical Steering Committee](#project-roles-and-technical-steering-committee)
- [Contributor Advancement](#contributor-advancement)
- [Communication Channels](#communication-channels)
+- [License](#license)
+- [Developer Certificate of Origin](#developer-certificate-of-origin)
## Code of Conduct
@@ -505,7 +508,7 @@ uv run pytest
4. **Update Documentation**: Update relevant docs
5. **Test Locally**: Ensure all tests pass
6. **Run Linters**: Fix any style issues
-7. **Commit Changes**: Use conventional commit messages
+7. **Commit Changes**: Use conventional commit messages and [sign off code contributions](#developer-certificate-of-origin)
8. **Push to Fork**: Push your branch to your fork
9. **Create Pull Request**: Submit PR with detailed description
@@ -568,6 +571,14 @@ Source code changes exceeding **2000 lines cannot be reviewed**. PRs above this
4. **Approval**: Once approved, a maintainer will merge your PR
5. **Cleanup**: Delete your feature branch after merge
+## Project Roles and Technical Steering Committee
+
+OpenSandbox's governance is established by the [Technical Charter](CHARTER.md). The project uses the following roles under Sections 2.b., 2.c., and 2.e. of the Charter:
+
+- **Contributors** participate through code, documentation, issues, reviews, testing, or community support.
+- **Maintainers (component scope)** guide development, review contributions, and help contributors in the areas assigned to them in [CODEOWNERS](.github/CODEOWNERS). They preserve quality, compatibility, and security, coordinate cross-component review, and keep affected implementations and documentation aligned. Component maintainership alone does not confer TSC membership or voting rights.
+- **Project Maintainers** provide repository-wide stewardship and serve as the voting members of the Technical Steering Committee (TSC), with responsibilities set out in [Section 2 of the Charter](CHARTER.md#2-technical-steering-committee). They coordinate cross-cutting decisions, governance updates, maintainer onboarding and offboarding, and resolution of review deadlocks. The Project Maintainers listed in [MAINTAINERS.md](MAINTAINERS.md#project-maintainers-and-technical-steering-committee) constitute the TSC membership under Section 2.b.; keep that roster synchronized with the fallback `*` owners in [CODEOWNERS](.github/CODEOWNERS).
+
## Contributor Advancement
OpenSandbox welcomes contributors seeking long-term involvement and project stewardship. The project maintains an explicit advancement process from Contributor to Maintainer (component ownership) and Project Maintainer (repository-wide stewardship).
@@ -664,4 +675,14 @@ If you have suggestions for improving this contributing guide, please open an is
## License
-By contributing to OpenSandbox, you agree that your contributions will be licensed under the [Apache 2.0 License](LICENSE).
+Code contributions are licensed under the [Apache 2.0 License](LICENSE). Documentation contributions are received and made available under the [Creative Commons Attribution 4.0 International License](https://creativecommons.org/licenses/by/4.0/), as specified in [Section 7 of the Technical Charter](CHARTER.md#7-intellectual-property-policy). License exceptions follow Section 7.c. of the Charter.
+
+### Developer Certificate of Origin
+
+All new inbound code contributions must include a [Developer Certificate of Origin](https://developercertificate.org/) (DCO) sign-off, as required by Section 7.b.ii. of the Technical Charter. Read the DCO before signing off. If you can make its certification, add the sign-off to each code contribution commit with:
+
+```bash
+git commit -s
+```
+
+This adds a `Signed-off-by: Your Name <[email protected]>` trailer to the commit message. Maintainers should verify the sign-offs on code contribution commits before merging; license-header checks do not verify DCO sign-offs.
diff --git a/GOVERNANCE.md b/GOVERNANCE.md
index a681f35ee..619b4146d 100644
--- a/GOVERNANCE.md
+++ b/GOVERNANCE.md
@@ -1,209 +1,44 @@
# OpenSandbox Governance
-This document describes how OpenSandbox is governed today and how technical decisions are made in the project.
+The [Technical Charter](CHARTER.md) establishes the project's technical governance. This document records project-specific working practices and maintainer procedures under that Charter.
-It is intended to reflect the project's current open development practice. As OpenSandbox grows, this document may evolve to support a more formal governance model.
+## Governance Documents
-## Goals
-
-OpenSandbox governance is designed to keep the project:
-
-- open to contributors and users
-- pragmatic in day-to-day decision making
-- transparent in technical direction
-- safe for public API, runtime, and security-sensitive changes
-- sustainable across multiple components and maintainers
-
-## Scope
-
-This document applies to the OpenSandbox repository and its major public surfaces, including:
-
-- public APIs and specifications in `specs/`
-- the lifecycle server in `server/`
-- runtime components in `components/`
-- Kubernetes controller and related assets in `kubernetes/`
-- SDKs in `sdks/`
-- CLI, examples, and project documentation
-
-## Project Values
-
-OpenSandbox maintainers and contributors are expected to act consistently with these principles:
-
-- **Open development**: design discussion, issue tracking, and code review happen in public whenever possible.
-- **Compatibility awareness**: public APIs, SDKs, CLI behavior, and documented user workflows should not change casually.
-- **Security first**: changes affecting isolation, networking, credentials, or execution safety require extra scrutiny.
-- **Component ownership with cross-project accountability**: subsystem maintainers own their areas, while cross-cutting changes require broader review.
-- **Documentation and implementation alignment**: public contracts, code, SDKs, examples, and docs should stay consistent.
-
-## Roles
-
-### Contributors
-
-Contributors are anyone who participates in the project, including by:
-
-- opening issues or discussions
-- submitting pull requests
-- reviewing code
-- improving docs, tests, examples, or tooling
-
-Contributors are expected to follow:
-
-- [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md)
-- [CONTRIBUTING.md](CONTRIBUTING.md)
-- [SECURITY.md](SECURITY.md) for vulnerability reporting
-
-### Maintainers
-
-Maintainers are contributors entrusted with reviewing and guiding changes in one or more parts of the repository.
-
-Today, the public record of subsystem maintainership is the [`CODEOWNERS`](.github/CODEOWNERS) file. Code owners for a given path are the default maintainers for that area.
-
-Maintainer responsibilities include:
-
-- reviewing pull requests for owned areas
-- helping preserve code quality, compatibility, and security
-- requesting cross-component review when a change affects other surfaces
-- keeping specs, implementation, tests, docs, and examples aligned when needed
-- helping contributors land changes successfully
-
-### Project Maintainers
-
-Project Maintainers are the maintainers responsible for repository-wide direction and final technical decisions when a matter cannot be resolved within normal component review.
-
-Until a dedicated `MAINTAINERS.md` is added, the fallback `*` owners in [`CODEOWNERS`](.github/CODEOWNERS) are treated as the public list of current Project Maintainers.
-
-Project Maintainers are responsible for:
-
-- cross-cutting technical decisions
-- governance updates
-- maintainer onboarding and offboarding
-- resolving review deadlocks
-- ensuring major changes follow the appropriate design process
+- [CHARTER.md](CHARTER.md) defines the mission, TSC authority, formal voting rules, project policies, and amendment requirements.
+- [CONTRIBUTING.md](CONTRIBUTING.md#project-roles-and-technical-steering-committee) defines project roles and explains contribution workflows and communication channels.
+- [MAINTAINERS.md](MAINTAINERS.md) lists current maintainers; [CODEOWNERS](.github/CODEOWNERS) records path ownership and routes reviews.
+- Conduct and vulnerability reports follow [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md) and [SECURITY.md](SECURITY.md), respectively.
## Decision Making
-### Day-to-Day Changes
-
-Most changes are made through the normal pull request workflow described in [CONTRIBUTING.md](CONTRIBUTING.md):
-
-1. discuss the change in an issue when appropriate
-2. submit a pull request
-3. pass automated checks
-4. receive maintainer review for affected areas
-5. address feedback
-6. merge once approved
-
-Normal changes are decided by maintainer review and rough consensus.
-
-### Component-Level Decisions
+### Reviews and Proposals
-For changes limited to one subsystem, the maintainers of that subsystem are the primary decision makers. Their review should carry the most weight for:
+Day-to-day changes follow the [pull request process](CONTRIBUTING.md#pull-request-process). Component maintainers lead decisions in their areas; changes affecting multiple components should involve the materially affected maintainers.
-- implementation details
-- code structure
-- tests
-- operational behavior within that component
+Changes to public APIs, SDKs, CLI behavior, lifecycle semantics, runtime isolation, ingress/egress, authentication, release processes, or repository-wide tooling require wider review. Maintainers should seek explicit review from all materially affected areas.
-If a change affects multiple subsystems, the relevant maintainers should be involved before merge.
+Before merge:
-### Cross-Cutting and Sensitive Decisions
+- Relevant CI checks should pass, or failures must be understood and accepted by maintainers.
+- At least one maintainer of the affected area should review the change.
+- Prefer additive, backward-compatible changes to public APIs, SDKs, CLI behavior, and documented configuration and deployment behavior. Call out breaking changes and provide migration guidance where needed.
+- Keep affected specifications, implementation, tests, documentation, examples, and release outputs aligned.
-Changes with broader impact require wider review. This includes changes to:
+Maintainers may decline changes that conflict with approved design, introduce unnecessary compatibility risk, weaken security without sufficient justification, or mix unrelated work.
-- public APIs or schemas in `specs/`
-- SDK interfaces or generated outputs
-- CLI behavior
-- lifecycle semantics
-- runtime isolation or security guarantees
-- ingress, egress, or authentication behavior
-- release processes or repository-wide tooling
-
-For these changes, maintainers should seek explicit review from all materially affected areas, not just the first area touched by the patch.
-
-### Major Design Changes and OSEPs
-
-OpenSandbox uses the OpenSandbox Enhancement Proposal process (`OSEP`) for major changes.
-
-An OSEP is expected for changes that:
-
-- introduce major features or architectural changes
-- modify the core API or runtime behavior
-- affect the security model or isolation guarantees
-
-The public OSEP process is documented in:
-
-- [oseps/README.md](oseps/README.md)
-- [oseps/CONTRIBUTING.md](oseps/CONTRIBUTING.md)
-
-When an OSEP is required, implementation should follow the approved design direction rather than bypassing it through code review alone.
+Major features, architectural changes, core API or runtime behavior changes, and changes to the security model or isolation guarantees follow the [OSEP process](oseps/CONTRIBUTING.md). Implementation should follow the approved design.
### Consensus and Voting
-OpenSandbox prefers **lazy consensus** for most technical decisions:
-
-- if affected maintainers agree, the change may proceed
-- if concerns are raised, they should be addressed in the PR, issue, or OSEP discussion
-
-If consensus cannot be reached in a reasonable time, Project Maintainers may use a simple majority vote of participating Project Maintainers.
-
-Voting rules:
-
-- each participating Project Maintainer has one vote
-- maintainers should recuse themselves in case of direct conflicts of interest
-- if a vote ties, the proposal does not pass and the status quo remains
-
-These general voting rules apply to technical disputes and design decisions. Maintainer nominations and promotions follow the dedicated electorate and approval thresholds specified in [Becoming a Maintainer](#becoming-a-maintainer).
-
-## Reviews and Merge Expectations
+OpenSandbox prefers **lazy consensus** for day-to-day technical decisions. A change may proceed when affected maintainers agree; concerns should be addressed in the PR, issue, or OSEP discussion.
-The following expectations apply before merge:
+If consensus cannot be reached in a reasonable time, Project Maintainers may hold a TSC vote under [Section 3 of the Technical Charter](CHARTER.md#3-tsc-voting). License exceptions and Charter amendments follow the special requirements in [Sections 7.c.](CHARTER.md#7-intellectual-property-policy) and [8.a.](CHARTER.md#8-amendments), respectively.
-- relevant CI checks should pass, or failures must be understood and accepted by maintainers
-- at least one maintainer of the affected area should review the change
-- cross-cutting changes should be reviewed by all materially affected areas when practical
-- breaking changes should be clearly called out, with migration guidance where needed
-- docs and tests should be updated when behavior changes
-
-Maintainers may decline or defer a change if it:
-
-- conflicts with approved design direction
-- introduces unnecessary compatibility risk
-- weakens security or isolation without a strong justification
-- mixes unrelated work into a single change
-
-## Public Interfaces and Compatibility
-
-OpenSandbox treats several surfaces as public contracts:
-
-- API specifications in `specs/`
-- published SDKs
-- CLI behavior
-- documented configuration and deployment behavior
-
-Maintainers should prefer additive and backward-compatible changes when possible.
-
-When changing a public contract, maintainers should update or verify the affected implementation, SDKs, docs, examples, and release outputs in the same change when practical.
+Maintainers should recuse themselves in cases of direct conflicts of interest. Maintainer nominations and promotions follow the dedicated electorate and approval thresholds in [Becoming a Maintainer](#becoming-a-maintainer).
## Releases
-Releases are managed through the public workflows and scripts in this repository, including the GitHub Actions workflows under `.github/workflows/` and the release tooling documented in `docs/community/release-automation.md`.
-
-Maintainers responsible for a release target are expected to ensure that:
-
-- the target has appropriate validation
-- release notes accurately reflect user-visible changes
-- versioning and tags follow the documented release conventions
-
-## Communication Channels
-
-The project's public collaboration channels are:
-
-- GitHub Issues for bugs, feature requests, and implementation questions
-- GitHub Discussions for broader design discussion and community help
-- pull requests for concrete code and documentation review
-- OSEPs for major design work
-
-Security issues should follow the private reporting guidance in [SECURITY.md](SECURITY.md).
+Maintainers responsible for releases are expected to ensure appropriate validation, accurate release notes, and adherence to the documented versioning and tag conventions. Release procedures are maintained in [Release Automation](docs/community/release-automation.md).
## Becoming a Maintainer
@@ -230,7 +65,7 @@ In addition, candidates for **Project Maintainer** are expected to show:
### Nomination Process
-Advancement is proposed through a public pull request updating [`CODEOWNERS`](.github/CODEOWNERS):
+Advancement is proposed through a public pull request updating [`CODEOWNERS`](.github/CODEOWNERS) and [MAINTAINERS.md](MAINTAINERS.md):
1. **Sponsorship**: Any existing Maintainer or Project Maintainer may sponsor a candidate by opening a nomination pull request against `CODEOWNERS` (adding the candidate to specific component paths for Maintainer, or to the fallback `*` list for Project Maintainer). Contributors interested in nomination may ask an existing Maintainer in a public issue or discussion.
2. **Nomination PR Content**: The pull request description must specify the candidate's GitHub username, the target role and path scope, links to their contributions demonstrating readiness, the list of eligible voting Project Maintainers, and the required approval count.
@@ -245,14 +80,14 @@ Nominations are decided through public review and voting on the pull request:
- **Approval Thresholds**:
- **Maintainer (component scope)**: Requires affirmative approvals (pull request approval or explicit LGTM) from at least **one-third (1/3)** of the eligible Project Maintainers, rounded up to the nearest whole maintainer.
- **Project Maintainer**: Requires affirmative approvals from at least **two-thirds (2/3)** of the eligible Project Maintainers, rounded up to the nearest whole maintainer.
-- **Voting Rules**: Approvals must be affirmative. Maintainers with direct conflicts of interest should recuse themselves. Abstentions, non-responses, or recusals do not count as approvals and do not lower the denominator. These nomination thresholds are separate from the simple majority of participating maintainers used for ordinary technical decisions.
+- **Voting Rules**: Approvals must be affirmative. Maintainers with direct conflicts of interest should recuse themselves. Abstentions, non-responses, or recusals do not count as approvals and do not lower the denominator. These nomination thresholds govern the role-specific advancement process; formal TSC votes follow [Consensus and Voting](#consensus-and-voting) and the Technical Charter.
- **Public Objections**: Any objections or concerns should be discussed publicly in the pull request during the seven-day period. There is no unanimity requirement or individual veto beyond the specified vote.
### Decision and Onboarding
- After the full seven calendar days have passed, a Project Maintainer verifies that the approval threshold has been met and that the candidate has explicitly accepted the nomination. The Project Maintainer then merges the pull request and coordinates the necessary scoped repository permissions.
- If the threshold is not met, the pull request cannot be merged and is closed without promotion. There is no automatic promotion based solely on time or contribution counts.
-- [`CODEOWNERS`](.github/CODEOWNERS) remains the public record of maintainership.
+- Keep [MAINTAINERS.md](MAINTAINERS.md) and [`CODEOWNERS`](.github/CODEOWNERS) synchronized when recording the appointment.
## Maintainer Inactivity and Removal
@@ -271,3 +106,5 @@ Changes to this document should be made through a public pull request.
Governance changes should receive review from Project Maintainers and should not be merged without giving maintainers and contributors a reasonable opportunity to comment.
Substantial governance changes may be proposed through an OSEP or a dedicated governance discussion if maintainers believe broader review is warranted.
+
+Changes to the Technical Charter itself follow [Section 8 of the Charter](CHARTER.md#8-amendments). Review or merge of a pull request alone does not amend the Charter.
diff --git a/MAINTAINERS.md b/MAINTAINERS.md
new file mode 100644
index 000000000..a6e970e38
--- /dev/null
+++ b/MAINTAINERS.md
@@ -0,0 +1,23 @@
+# OpenSandbox Maintainers
+
+Project roles are defined in [CONTRIBUTING.md](CONTRIBUTING.md#project-roles-and-technical-steering-committee). This file records the current membership; [CODEOWNERS](.github/CODEOWNERS) records component assignments and review routing.
+
+## Project Maintainers and Technical Steering Committee
+
+- [@jwx0925](https://github.com/jwx0925)
+- [@hittyt](https://github.com/hittyt)
+- [@Pangjiping](https://github.com/Pangjiping)
+- [@ninan-nn](https://github.com/ninan-nn)
+
+## Component Maintainers
+
+In addition to the Project Maintainers above:
+
+- [@Generalwin](https://github.com/Generalwin)
+- [@Spground](https://github.com/Spground)
+- [@fengcone](https://github.com/fengcone)
+- [@kevinlynx](https://github.com/kevinlynx)
+
+## Membership Changes
+
+Follow [GOVERNANCE.md](GOVERNANCE.md#becoming-a-maintainer) for nominations and advancement, and [Maintainer Inactivity and Removal](GOVERNANCE.md#maintainer-inactivity-and-removal) for departures. Update this file and [CODEOWNERS](.github/CODEOWNERS) together when membership changes.
diff --git a/README.md b/README.md
index 571074eb7..a071515bd 100644
--- a/README.md
+++ b/README.md
@@ -273,4 +273,4 @@ Tagged release images are signed keylessly with Cosign and include provenance at
OpenSandbox is a project of the [Agentic AI Foundation (AAIF)](https://aaif.io/projects/opensandbox).
-Licensed under the [Apache 2.0 License](LICENSE).
+Code is licensed under the [Apache 2.0 License](LICENSE). See the [contribution guide](CONTRIBUTING.md#license) for documentation licensing and contribution terms.
diff --git a/ROADMAP.md b/ROADMAP.md
index 4b61e1414..450077881 100644
--- a/ROADMAP.md
+++ b/ROADMAP.md
@@ -54,7 +54,7 @@ This roadmap describes the intended project direction for roughly the next 12 mo
|------|--------|----------|-------|
| Lifecycle API stability | Ongoing | [specs/](specs/README.md), [OSEPs](oseps/README.md) | Preserve compatibility and require clear migration paths for user-visible changes. |
| Security documentation | Ongoing | [SECURITY.md](SECURITY.md), [docs/](docs/) | Keep vulnerability reporting, security expectations, and deployment guidance current. |
-| Open project governance | Ongoing | [GOVERNANCE.md](GOVERNANCE.md), [CONTRIBUTING.md](CONTRIBUTING.md) | Maintain a lightweight, public decision process as the project grows. |
+| Open project governance | Ongoing | [CHARTER.md](CHARTER.md), [GOVERNANCE.md](GOVERNANCE.md), [CONTRIBUTING.md](CONTRIBUTING.md) | Maintain a lightweight, public decision process as the project grows. |
## Not Currently Planned
diff --git a/docs/community/contributing.md b/docs/community/contributing.md
index 1d486d672..023db804a 100644
--- a/docs/community/contributing.md
+++ b/docs/community/contributing.md
@@ -11,10 +11,14 @@ The contributing guide is maintained in the repository root to keep GitHub's con
Read the Contributing Guide on GitHub →
</a>
-## Contributor Advancement
+## Project Governance
-OpenSandbox maintains an explicit advancement process for contributors to become component maintainers or project maintainers. For nomination requirements, voting periods, and approval thresholds, see the project governance guide:
+Governance documents are maintained in the repository:
-<a href="https://github.com/opensandbox-group/OpenSandbox/blob/main/GOVERNANCE.md#becoming-a-maintainer" target="_blank">
- Read the Maintainer Advancement Process on GitHub →
-</a>
+- [Technical Charter](https://github.com/opensandbox-group/OpenSandbox/blob/main/CHARTER.md): formal governance and project policies.
+- [Governance Guide](https://github.com/opensandbox-group/OpenSandbox/blob/main/GOVERNANCE.md): project working practices.
+- [Maintainer Roster](https://github.com/opensandbox-group/OpenSandbox/blob/main/MAINTAINERS.md): current project and component maintainers.
+
+## Contributor Advancement
+
+For nomination requirements, voting periods, and approval thresholds, see the [Maintainer Advancement Process](https://github.com/opensandbox-group/OpenSandbox/blob/main/GOVERNANCE.md#becoming-a-maintainer).
diff --git a/docs/sdks/csharp.md b/docs/sdks/csharp.md
index 08483bc44..990efe724 100644
--- a/docs/sdks/csharp.md
+++ b/docs/sdks/csharp.md
@@ -788,4 +788,4 @@ catch (SandboxException ex)
## License
-Apache License 2.0
+The C# SDK code is licensed under [Apache 2.0](https://github.com/opensandbox-group/OpenSandbox/blob/main/LICENSE).
diff --git a/docs/sdks/go.md b/docs/sdks/go.md
index 21297e69f..b91f3e1ec 100644
--- a/docs/sdks/go.md
+++ b/docs/sdks/go.md
@@ -825,4 +825,4 @@ if err != nil {
## License
-Apache 2.0
+The Go SDK code is licensed under [Apache 2.0](https://github.com/opensandbox-group/OpenSandbox/blob/main/LICENSE).