Overview

PromptKit is an open source project developed by AltairaLabs and is committed to building a welcoming and diverse community. This document describes the governance structure and processes for the PromptKit project.

Project Goals

PromptKit aims to provide:

• A comprehensive testing framework for LLM applications (Arena)
• A production-ready SDK for deploying LLM applications
• Tools for packaging and distributing prompt configurations (PackC)
• A robust runtime for executing LLM workflows with tool integration

Governance Structure

Maintainers

Maintainers are responsible for the overall direction, quality, and long-term sustainability of the project. They have write access to the repository and are responsible for:

• Reviewing and merging pull requests
• Managing releases and versioning
• Ensuring code quality and test coverage
• Facilitating community discussions and decisions
• Maintaining project documentation
• Enforcing the Code of Conduct

Current Maintainers:

• AltairaLabs Team (primary maintainer)

Contributors

Contributors are community members who have made valuable contributions to the project through:

• Code contributions (bug fixes, features, improvements)
• Documentation improvements
• Issue reporting and triage
• Community support and engagement
• Testing and feedback

All contributors are recognized and appreciated regardless of the size of their contribution.

Committers

Committers are trusted contributors who have demonstrated:

• Consistent high-quality contributions over time
• Good understanding of the project architecture and goals
• Collaborative attitude and adherence to the Code of Conduct
• Active participation in project discussions

Committers have additional privileges such as:

• Ability to review and approve pull requests
• Participation in technical discussions and decisions
• Mentoring new contributors

Decision Making Process

Consensus Building

The project strives to make decisions through consensus among maintainers and active contributors. For significant changes:

1. Proposal: Create a GitHub issue or RFC describing the change
2. Discussion: Allow time for community input and discussion
3. Consensus: Maintainers work to build consensus among stakeholders
4. Implementation: Proceed with implementation once consensus is reached

Types of Decisions

Day-to-day Decisions:

• Bug fixes and minor improvements
• Documentation updates
• Routine maintenance

These can be made by any maintainer or trusted contributor.

Significant Decisions:

• New features or major changes
• Breaking changes to APIs
• Changes to project governance
• Addition of new maintainers

These require broader discussion and consensus among maintainers.

Contribution Process

Getting Started

1. Read the Contributing Guide
2. Review the Code of Conduct
3. Check existing issues and discussions
4. Start with small contributions to familiarize yourself with the project

Pull Request Process

1. Fork the repository and create a feature branch
2. Make your changes with appropriate tests and documentation
3. Submit a pull request with a clear description
4. Participate in the review process
5. Address feedback and iterate as needed

Issue Management

• Use GitHub issues for bug reports, feature requests, and discussions
• Follow issue templates when available
• Provide clear, detailed information
• Be respectful and constructive in discussions

Becoming a Maintainer

Maintainer status is earned through sustained contribution and demonstrated commitment to the project. The process involves:

1. Track Record: Consistent, high-quality contributions over at least 6 months
2. Trust: Demonstrated good judgment and adherence to project values
3. Nomination: Existing maintainer nominates the candidate
4. Consensus: Current maintainers reach consensus on the nomination
5. Acceptance: Candidate accepts the responsibilities of maintainership

Maintainer Responsibilities

• Technical Excellence: Ensure code quality and architectural integrity
• Community Building: Foster an inclusive and welcoming environment
• Project Stewardship: Make decisions in the best interest of the project and community
• Transparency: Communicate decisions and rationale clearly
• Availability: Maintain reasonable responsiveness to community needs

Stepping Down

Maintainers may step down at any time. When stepping down:

• Notify other maintainers of the decision
• Transfer any critical responsibilities
• Remove access credentials appropriately
• Maintain confidentiality of any sensitive information

Code of Conduct Enforcement

The maintainers are responsible for enforcing the Code of Conduct. This includes:

• Responding to reports of misconduct
• Investigating violations
• Taking appropriate corrective action
• Maintaining confidentiality of reports

Communication Channels

• GitHub Issues: Bug reports, feature requests, technical discussions
• GitHub Discussions: General community discussions, Q&A
• Pull Requests: Code review and technical discussions
• Email: Private communications to conduct@altairalabs.ai

Project Assets

The following assets are managed by the maintainers:

• GitHub repository and organization settings
• Domain names and websites
• Social media accounts
• Release artifacts and distributions
• Trademark and intellectual property

Changes to Governance

This governance document may be updated as the project evolves. Changes require:

1. Proposal via GitHub issue or pull request
2. Community discussion period (minimum 2 weeks)
3. Consensus among current maintainers
4. Documentation of the decision and rationale

Acknowledgments

This governance model is inspired by successful open source projects and CNCF best practices. We thank the broader open source community for their guidance and examples.

Document Version: 1.0
Last Updated: November 1, 2025
Next Review: February 1, 2026