Skip to content

GOVERNANCE.md

Latest commit

 

History

History
104 lines (69 loc) · 2.81 KB

GOVERNANCE.md

File metadata and controls

104 lines (69 loc) · 2.81 KB

Governance

This document outlines the governance structure for Arillso projects.

Project Leadership

Core Maintainers

Core maintainers have write access to repositories and are responsible for:

  • Reviewing and merging pull requests
  • Triaging issues
  • Managing releases
  • Setting technical direction
  • Enforcing Code of Conduct

Current Core Maintainers:

  • Simon Baerlocher (@sbaerlocher)

Contributors

Anyone can contribute to Arillso projects by:

  • Submitting pull requests
  • Reporting issues
  • Participating in discussions
  • Improving documentation
  • Helping other users

Decision Making

Consensus

Most decisions are made through consensus among core maintainers. We aim for:

  1. Discuss - Open discussion in issues or discussions
  2. Propose - Create a proposal with rationale
  3. Review - Allow time for feedback (minimum 3 days for non-urgent changes)
  4. Decide - Core maintainers reach consensus
  5. Document - Record decision in relevant documentation

Voting

If consensus cannot be reached, decisions are made by simple majority vote among core maintainers.

Contribution Process

  1. Open an Issue - Discuss significant changes before implementing
  2. Fork and Branch - Create a feature branch
  3. Implement - Make your changes following standards
  4. Test - Ensure all tests pass
  5. Pull Request - Submit for review
  6. Review - Address feedback from maintainers
  7. Merge - Maintainer merges when approved

Becoming a Maintainer

Contributors can become maintainers by:

  • Demonstrating deep understanding of the project
  • Making significant contributions over time
  • Showing good judgment in reviews and discussions
  • Being nominated by existing maintainers
  • Accepting responsibilities of the role

Code of Conduct Enforcement

Violations of our Code of Conduct are handled by:

  1. Report - Email hello@arillso.io with details
  2. Review - Core maintainers review privately
  3. Decide - Determine appropriate action
  4. Action - Implement decision (warning, temporary ban, permanent ban)
  5. Document - Record decision (respecting privacy)

Release Management

Ansible Collections

  • Patch releases (X.Y.Z → X.Y.Z+1): Bug fixes, security updates
  • Minor releases (X.Y.Z → X.Y+1.0): New features, non-breaking changes
  • Major releases (X.Y.Z → X+1.0.0): Breaking changes

Other Projects

Follow Semantic Versioning 2.0.0

Changes to Governance

This governance document can be updated by:

  1. Opening a pull request with proposed changes
  2. Allowing 7 days for discussion
  3. Approval by consensus of core maintainers

Contact

Last Updated: January 2026