Thank you for your interest in contributing to the Codex Document Format specification.
- Use GitHub Issues for bug reports, specification questions, and feature requests
- Search existing issues before creating a new one
- Provide clear, detailed descriptions
- Open an Issue First: For significant changes, open an issue to discuss the proposal before submitting a PR
- Fork and Branch: Create a feature branch from
main - Follow Standards: Adhere to the specification writing style (see below)
- Submit PR: Reference the related issue in your PR description
- Use clear, unambiguous language
- Follow RFC 2119 for requirement levels (MUST, SHOULD, MAY)
- Include rationale for design decisions
- Provide examples for complex concepts
- Reference external standards precisely (include version numbers)
For reference implementation and tooling:
- TypeScript with strict type checking
- Comprehensive test coverage
- Clear documentation
Currently using informal consensus with project maintainers having final say. This will evolve as the community grows.
- Be respectful and constructive
- Focus on technical merit
- Welcome newcomers
By contributing, you agree that your contributions will be licensed under Apache License 2.0.
All contributors must agree to the following:
- You have the right to submit the contribution
- You grant license to use your contribution
- Your contribution does not include patented material (or you grant patent license)
- Open a GitHub Issue for questions
- Use GitHub Discussions for general conversation and ideas
- Tag issues with
questionfor specific inquiries - Email greg.vonnessi@entrolution.ai for private matters
Contributors will be acknowledged in the project documentation.