Community & Governance

Join the OSSP Working Group and help shape the future of AI safety telemetry standards. Open, transparent, and vendor-neutral.

Join Working Group Neutrality Pledge

Working Group

Mission

Develop and maintain the Open Safety Signal Protocol as a vendor-neutral standard for AI safety telemetry, ensuring broad industry adoption and interoperability.

Scope

  • Technical specification development
  • Schema design and validation
  • Reference implementation oversight
  • Compliance and conformance testing
  • Ecosystem development and adoption

Membership

Open to organizations and individuals committed to advancing AI safety through standardized telemetry. All participants must agree to the working group charter and code of conduct.

The Neutrality Pledge

Foundation Governance Commitment

OSSP will be donated to a neutral foundation (CNCF or LF AI & Data) within 12-18 months of v1.0 release.

Why Neutrality Matters

  • Vendor Independence: No single company controls the standard
  • Community Ownership: Democratic governance by working group members
  • Long-term Stability: Foundation backing ensures continuity
  • Broad Adoption: Neutral governance encourages industry participation

Governance Transition

The working group is developing transition plans for foundation governance, including intellectual property transfer, trademark assignment, and community governance structures.

How to Contribute

🐛 Report Issues

Found a bug or have a feature request? Open an issue in the appropriate repository.

📝 Improve Documentation

Help make OSSP more accessible by improving documentation, examples, and tutorials.

  • Fix typos and clarify language
  • Add missing examples
  • Improve API documentation
  • Create integration guides

🔧 Code Contributions

Contribute code improvements, new features, and bug fixes.

  • SDK enhancements and new language bindings
  • Schema improvements and new event types
  • Validation tools and testing utilities
  • Integration examples

🎯 Schema Design

Help design new event schemas and improve existing ones.

  • Propose new AI safety event types
  • Improve schema validation rules
  • Add real-world use case examples
  • Review compliance requirements

🌍 Ecosystem Development

Build integrations and tools that expand the OSSP ecosystem.

  • Observability platform integrations
  • Framework and library bindings
  • Monitoring and alerting tools
  • Compliance and audit utilities

🗣️ Community Engagement

Help grow the OSSP community through outreach and education.

  • Write blog posts and articles
  • Present at conferences and meetups
  • Answer questions in discussions
  • Organize community events

Contribution Process

1. Discussion

Start with a GitHub Discussion or issue to propose changes and gather feedback from the community.

2. Fork & Branch

Fork the repository and create a feature branch for your changes. Follow the repository's branching conventions.

3. Implement

Make your changes following the project's coding standards and include appropriate tests and documentation.

4. Pull Request

Submit a pull request with a clear description of your changes and link to related issues or discussions.

5. Review

Participate in the review process, address feedback, and work with maintainers to refine your contribution.

6. Merge

Once approved, your contribution will be merged and included in the next release.

Working Group Structure

Technical Steering Committee

Provides technical leadership and makes final decisions on specification changes and architectural direction.

  • Review and approve specification changes
  • Set technical roadmap and priorities
  • Resolve technical disputes
  • Maintain quality standards

Schema Working Group

Focuses on event schema design, validation rules, and compliance requirements.

  • Design new event schemas
  • Review and improve existing schemas
  • Ensure compliance alignment
  • Validate real-world use cases

Implementation Group

Develops and maintains reference implementations, SDKs, and integration tools.

  • Maintain Python SDK
  • Develop additional language bindings
  • Create integration examples
  • Build testing and validation tools

Adoption & Outreach

Drives community growth, education, and ecosystem development.

  • Community events and workshops
  • Documentation and tutorials
  • Industry partnerships
  • Marketing and communications

Code of Conduct

Our Commitment

The OSSP Working Group is committed to providing a welcoming and inclusive environment for all participants, regardless of background, experience level, or personal characteristics.

Expected Behavior

  • Be respectful: Treat all community members with respect and professionalism
  • Be inclusive: Welcome new contributors and help them succeed
  • Be collaborative: Work together to achieve common goals
  • Be constructive: Provide helpful feedback and suggestions
  • Be patient: Understand that everyone is learning and growing

Reporting

If you experience or witness unacceptable behavior, please report it to the working group maintainers. All reports will be handled confidentially and with care.

Resources

Community Repository

Governance documents, contribution guidelines, and community resources.

View Repository

Discussions

Join ongoing conversations about OSSP development and adoption.

Join Discussions

Roadmap

See what's planned for future OSSP releases and how you can contribute.

View Roadmap

Meeting Notes

Access working group meeting notes, decisions, and action items.

View Notes