LambdaBuffers is developed and maintained by MLabs.
Gergely Szabo (@szg251)
- Role: Developer
- Email: gergely@mlabs.city
- Code review and approval
- Issue triage and management
- Release planning and execution
Both maintainers must agree on:
- Major architectural changes
- Breaking API changes
- New feature additions
- Release timing
- Contributor guidelines changes
Each maintainer can independently:
- Merge small bug fixes and improvements
- Respond to issues and community questions
- Create and assign issues
- Update documentation
When we disagree:
- Discussion: Extended discussion to understand perspectives
- Research: Gather community input if needed
- Compromise: Find middle ground or alternative solution
- Escalation: If needed, seek input from trusted community members
- Temporary Decision: If urgent, implement temporary solution with plan to revisit
- Issues: Bug reports and feature requests
- Discussions: General project discussion
- Pull Requests: Code contributions
- Email: info@mlabs.city for private matters
- Small Changes: Single maintainer approval required
- Medium/Large Changes: Both maintainers should review
We aim to respond to:
- Security issues: Within 24 hours (one of us)
- Urgent bugs: Within 24-48 hours
- General issues: Within 3-5 days
- Pull requests: Within 1 week
- Community discussions: Within 1 week
- Planning: Decide features and timeline together
- Development: Divide work based on expertise
- Review: Cross-review all significant changes
- Testing: Shared responsibility for testing
- Release: Both approve final release
This project follows the Contributor Covenant. Both maintainers are responsible for enforcement.
This governance reflects our current project structure, which may evolve in the future.