Skip to content

Contributing

Welcome Contributors

KTP is an open-source project built by the community, for the community. Your contributionsβ€”big or smallβ€”help shape the future of digital trust.


πŸ“ How You Can Help

Every contribution matters. Whether you're fixing a typo, proposing a new RFC, or building an integration, you're helping advance the mission of trustworthy, transparent, and resilient digital systems.

Ways to Contribute:

  • Documentation β€” Improve clarity, fix errors, add examples
  • RFCs β€” Propose specifications, review drafts, provide feedback
  • Code β€” Build tools, SDKs, integrations, or reference implementations
  • Testing β€” Validate specs, report bugs, test edge cases
  • Community β€” Answer questions, share use cases, write tutorials
  • Advocacy β€” Present at conferences, write blog posts, spread the word

πŸš€ Getting Started

  1. Read the Code of Conduct β€” We're committed to an inclusive, respectful community
  2. Browse Open Issues β€” Find something that interests you or needs attention
  3. Join Discussions β€” Share your ideas before diving into large changes
  4. Fork & Branch β€” Work in your own fork, create descriptive branch names
  5. Submit a PR β€” Clear description, reference issues, follow conventions
  6. Collaborate β€” Respond to feedback, iterate, and improve together

🎯 Contribution Focus Areas

High Priority

  • Reference implementations in Python, TypeScript, Go
  • SIEM integrations (Splunk, Elastic, Chronicle)
  • Test suites and validation tools
  • Real-world case studies and deployment stories

Always Welcome

  • Typo fixes and grammar improvements
  • Code examples and tutorials
  • Translation of documentation
  • Accessibility improvements

πŸ“‹ Guidelines

  • Quality over speed β€” Take time to get it right
  • Context is key β€” Explain the "why" behind your changes
  • Stay focused β€” One change per PR when possible
  • Test thoroughly β€” Include examples, edge cases, and validation
  • Be patient β€” Review cycles vary; we'll get to your contribution

For detailed technical guidelines, see our main CONTRIBUTING.md on GitHub.


πŸ’¬ Questions?

Not sure where to start? Have an idea but need guidance? Reach out: