General questions
For general questions about ANS, email contact@ansinfo.ai.
Start with a contribution
- Improve the specification. Report an ambiguity, discuss a requirement, or propose an interoperable extension in the specification repository.
- Build and test. Choose an implementation or SDK, try it in your environment, and report reproducible issues in its repository.
- Improve the documentation. Clarify an example, correct a link, or explain a working integration and its assumptions.
- Review and help. Review a proposed change, reproduce an issue, or answer a question. These contributions are part of maintaining the project.
Read the target repository’s contribution guide before submitting a pull request. The ANS contribution guide covers the specification workflow. Sign off your commits under the Developer Certificate of Origin and follow the project’s Code of Conduct.
Where discussion happens
Use GitHub issues and pull requests in the relevant repository for technical questions and proposed changes. Include your environment, the behavior you expected, and enough detail for someone else to reproduce the issue.
Project-wide questions and TSC business belong in the governance repository. Meeting announcements, agendas, and notes are linked from the relevant issues. There is no standing meeting schedule; anyone can attend open project meetings.
Grow your involvement
The contributor track progresses from contributor to member, reviewer, and maintainer. The contributor ladder describes the responsibilities and nomination process for each role.
Repository maintainers review and merge technical work. The TSC handles project-wide governance and escalated decisions. Read the governance overview to meet the TSC and find the team responsible for a repository.
Share an integration
Open an issue with public source, installation instructions, the ANS features it supports, and tests showing that invalid identities or requests are rejected. Document limitations and distinguish examples and research previews from supported releases. A working integration should explain where verification is enforced and what changes when it fails.
Report sensitive issues through the right channel
Follow the affected repository’s security policy for suspected vulnerabilities. Start with the specification security policy or find the affected project in the implementation directory. Use the reporting process in the Code of Conduct for conduct concerns.