Skip to content

Latest commit

 

History

History
35 lines (22 loc) · 1.94 KB

File metadata and controls

35 lines (22 loc) · 1.94 KB

Contributing to Audio-V

Audio-V welcomes reproducible defect reports, validation fixtures with documented provenance, accessibility improvements, documentation, and focused code changes.

Before submitting code

  1. Do not submit confidential audio, personal data, credentials, or material You cannot legally redistribute.

  2. Add or update tests for behavioral changes.

  3. Run:

    npm ci
    npm run provision:engines
    npm run verify
    npm run validate:platform
  4. Keep Oracle claims within the evidence boundaries documented in docs/METHODOLOGY.md.

  5. Complete the Contributor License Agreement checkbox in the pull-request template.

Contributor agreement

Contributions are accepted under the Audio-V Contributor License Agreement. Contributors retain copyright while granting the Project and its users the rights needed for AGPL distribution, enforcement, future dual licensing, and commercial editions.

The agreement does not permit contributors to relicense third-party material they do not own. Identify every third-party source and license in the pull request.

Validation-corpus recordings

Do not add validation audio to a pull request or Git commit. Source masters, derivatives, and personal acceptance records are intentionally ignored.

Recordings require the separate Audio-V Validation Corpus Contribution Agreement, covering both the sound recording and underlying composition. Maintainers import an accepted master with npm run corpus:import, generate controlled cases with npm run corpus:generate, and publish only the rights-cleared corpus artifacts authorized by the recorded agreement.

Licensing and branding

Project code is licensed under AGPL-3.0-only. Dependencies and bundled engines retain their own licenses. The Audio-V name, logo, icon, Oracle Engine identity, and official-release designation are governed by TRADEMARKS.md.