Skip to main content

Cadence Workflow Open Source Governance

This document outlines the governance model for the Cadence Workflow project. It defines the roles, responsibilities, decision-making processes, and contribution guidelines to ensure transparency, inclusivity, and sustainability within the Cadence open-source community.

Guiding Principles​

The governance of the Cadence project adheres to the following principles:

  1. Transparency: Discussions, decisions, and contributions are made in public forums.
  2. Inclusivity: Contributions are welcome from anyone, regardless of affiliation, experience, or background.
  3. Meritocracy: Decisions are guided by technical merit and the value of contributions to the community.
  4. Sustainability: Processes are designed to ensure the long-term health and success of the project.

Roles and Responsibilities​

Ways to contribute to the Cadence project can be found in this document.

Decision-Making Process​

1. Consensus-Based Decisions​

Most decisions are made through open discussions on GitHub or community meetings. Contributors and committers work towards consensus, ensuring that all voices are heard.

Based on the requests from the past, feedback during planning sessions and the criticality of the features Cadence core team, which is also the technical steering committee, will propose a plan for the next year or 6 months.

2. Appeals​

If a contributor disagrees with a decision, they can escalate the issue for review through Github or community meetings, explaining why a change in current proposal is necessary by comparing their ideas to existing items in the planning proposal.

Contribution Guidelines​

  1. How to Contribute:
    • Review the contributing guide.
    • Submit issues to report bugs, suggest features, or ask questions.
    • Create pull requests for code, documentation, or tests.
  2. Review Process:
    • All pull requests must be reviewed by at least one committer.
    • Significant changes require approval from the core team.
    • Based on your past contributions and future commitments, you may be invited to be a part of Cadence open source teams listed in cadence-workflow org.
  3. Code Standards:
    • Follow the project's coding styles and guidelines.
    • Ensure code includes adequate tests and documentation.
  4. Behavior Expectations:
    • Abide by the Code of Conduct.
    • Treat all community members with respect and professionalism.

Code of Conduct​

The Cadence community follows a Code of Conduct to ensure a welcoming and inclusive environment for all participants.

Project Roadmap​

The core team is responsible for maintaining and updating the project roadmap. The roadmap outlines:

  • Upcoming features and milestones.
  • Technical debt and areas of improvement.
  • Long-term goals for the project.

The roadmap is published and updated regularly on the project website and GitHub.

Licensing​

All repositories under the Cadence Workflow organization are released under the MIT License, unless otherwise specified.

Amendments​

This governance document is a living document. Changes can be proposed by any contributor and must be approved by the core team. Updates will be announced to the community.

Thank you for being part of the Cadence Workflow community. Together, we can build resilient and scalable applications!