Contribute

Ways to Contribute

Standards

Propose a new standard or amendment through the RFC (Request for Comments) process. Standards are community-voted and ratified. Learn how the process works ↓

Open an RFC →View All Standards

Whitepapers

Technical deep dives and analysis by community contributors. Open a proposal issue, then submit a PR with your content.

Propose a Whitepaper →View All Whitepapers

Glossary

Add a new term or improve an existing definition. Open an issue with your contribution.

Add a Term →Edit a Term

Equipment Database

Submit specs for AV equipment. Open an issue with manufacturer, model, category, and specifications.

Submit Equipment →Browse Equipment

Blog

The blog is editor-maintained for project news and updates. If you have an idea for a post, reach out to the maintainers.

Read the Blog

Site & Tools

Found a bug? Have an idea for a new calculator or feature? Report it or open a PR.

Report a Bug →View Source

How the RFC Process Works

All standards proposals follow the RFC (Request for Comments) process, inspired by the IETF model.

Proposal

Open a GitHub issue using the RFC template. Describe the problem, proposed solution, and affected AV domains.

Discussion

The community reviews the RFC. Comments, concerns, and proposed amendments are discussed openly on the issue.

Draft PR

Once rough consensus is reached, open a Pull Request with the draft standard document in Markdown format.

Review Period

The PR enters a minimum 60-day public review. Major changes restart the clock.

Ratification

After review with no blocking objections, the PR is merged. The standard is published.

Open an RFC Now →

RFC Statuses

See the RFC Status Dashboard for the current state of every standard.

Status	Meaning
draft	Work in progress. Not yet ready for formal review.
under-review	In the 60-day public review period. Comments welcome.
published	Ratified and recommended for implementation.
deprecated	Superseded or no longer recommended.

Principles

Rough consensus, not unanimity. We seek broad agreement, not perfection.
Technical merit first. Arguments backed by evidence and real-world data carry more weight.
No IP encumbrances. All standards must be implementable freely without patent licensing fees.
Plain English. Write for the working AV professional, not just academics.
Versioned and auditable. Every change is in Git. Nothing is ever quietly altered.

Quick Start

git clone https://github.com/sane-av/sane-av.github.io
cd sane-av.github.io
pnpm install
pnpm dev

Content repos are cloned as siblings automatically during pnpm build. See README.md for the full workspace layout.

License

All contributions are licensed under CC BY-SA 4.0 (content) or Apache 2.0 (code). The SANE name, logo, and certification marks are trademarks — see NOTICE.

Sponsorship

If your organization benefits from SANE, considersponsoring the project on GitHub Sponsors. Donations cover infrastructure, legal review, and maintainer time.