Community¶

pVisor is an Apache-2.0 open source project.

Communication channels¶

Start with a reproducible problem¶

Include the version or commit, operating system, executor, minimal command, and expected and actual results in a report. Remove credentials and private content before sharing a Run Bundle or logs. Discuss substantial interface or behavior changes in an issue first, covering options, compatibility effects, and acceptance criteria before implementation.

Keep a PR focused on one change: repair the implementation, add relevant regressions, and update the authoritative Chinese and English documentation together. Read READMEs along the modified path, prepare dependencies using Development environment, then follow Contributing for formatting, lint, and relevant tests. State which checks you actually ran and which conditions remain unverified; do not report unexecuted scenarios as passing.

Separate validation from approval¶

Unit and integration tests check implementation. Semspec expresses product commitments as claims, violation examples, and executable checks. You may draft new cases, fix implementations, and maintain runner tests, but must not weaken existing claims, checks, or xfail annotations to obtain PASS.

Human semantic review is separate from tests and PR merging. AI must not run semspec approve / revoke or edit real REVIEWED.toml or .approved/ snapshots. See Testing and semspec for the rules. Contributions are licensed under Apache-2.0.

Discussion norms¶

Keep discussions about implementation, issue reports, and contribution reviews focused on observable behavior and evidence: include version, platform, and reproduction when reporting a problem; explain impact and acceptable changes when reviewing, without judging a contributor's ability or identity; when disagreeing, first restate the problem each side needs solved, then compare options and verification results. Insults, harassment, discrimination, publishing others' private information, and sustained personal attacks are not acceptable. The project has not yet formally adopted a Contributor Covenant or a private conduct-reporting channel; both will be announced here once established. Report security vulnerabilities through the disclosure policy.

Trying it out and sharing a case¶

No organization case is currently registered here with public authorization; organization names, logos, and production scale are published only after the user's confirmation. If you have tried pVisor, a useful case record includes the original workflow and the problem, the pVisor version, platform and executor, agent and model versions, key commands or configuration, how results were reviewed, and what actually changed after adoption. Attach task counts, machine specs, and measurement methods to performance numbers; failed attempts and the configurations adjusted afterward are equally valuable. Confirm public authorization for names, quotes, and data before submitting, and replace private code and credentials with publicly reproducible material.