Skip to content

GOVERNANCE.md

Latest commit

 

History

History
92 lines (64 loc) · 4.19 KB

GOVERNANCE.md

File metadata and controls

92 lines (64 loc) · 4.19 KB

Simple Project Governance

This document outlines the governance model for RESTEasy. This governance model is designed to uphold the principles of transparency, open collaboration, and community involvement.

Roles and Responsibilities

  • Contributors: Anyone who contributes to RESTEasy in any form.
  • Maintainers: Contributors eligible for write access to a RESTEasy code repository.
    • Responsible for driving initiatives and reviewing/merging contributions in their area of expertise.
  • Project Lead: Maintainer with higher decision power.
    • Responsible for keeping RESTEasy’s technical direction consistent, safe and sustainable. This involves in particular enforcing compliance with requirements of the Commonhaus Foundation.
  • Organization Project Lead: Maintainer with higher decision power in all projects and components. Acts as the WildFly Commonhaus Organization Project Lead for the RESTEasy Organization at the WCO. Responsible for communicating the overall RESTEasy organization's project direction and roadmap to the RESTEasy community. Responsible for keeping the project's technical direction consistent, safe and sustainable. This involves in particular enforcing compliance with requirements of the Commonhaus Foundation.

Decision-Making

Consensus-seeking (lazy consensus)

RESTEasy primarily aims for a consensus-based decision-making process, where Maintainers and active Contributors discuss and come to an agreement.

In practice, this involves:

  • Discussing matters openly, to facilitate others joining the discussions and expressing concerns.
  • Taking into account every Contributor’s opinion, regardless of their role.

Note

Actual implementation of consensus decision-making is up to Maintainers and can vary based on the audience and criticality of the discussion. Inspiration may be found in the Lazy Consensus model as defined by the Apache Foundation, and in Martha’s Rules.

Conflict Resolution

If conflicts arise, Maintainers are responsible for facilitating a resolution.

  1. The Project Lead or Organization Project Lead holds the power to make the final decision.
  2. As a last resort, in particular in case of disagreement about the decision-making process, the Commonhaus Foundation Council (CFC) can be asked to mediate the discussion.

Role Granting/Revoking

The role of Maintainer, Project Lead or Organization Project Lead is granted or revoked through the decision-making process, with additional restrictions:

  1. The discussion must happen in a GitHub Discussion.
  2. The opinion of the Maintainer, Project Lead or Organization Project Lead whose role is being discussed does not factor into the decision.
  3. Discussions regarding the role of Project Lead must last at least 30 days.

Eligible candidates:

  • For the role of Maintainer: Any contributor.
  • For the role of Project Lead: Any contributor.
  • For the role of Organization Project Lead: Any Project Lead, provided the candidate is a Commonhaus Foundation member.

Maintainers, Project Leads and Organization Project Lead keep their role indefinitely, unless they resign or a new decision revokes their role.

Code of Conduct

All participants in RESTEasy are expected to adhere to the RESTEasy Code of Conduct, which is adopted in accordance with Commonhaus Foundation requirements. Please ensure you are familiar with its guidelines and expectations, as it's essential for maintaining a positive and collaborative environment.

Trademark Policy

The RESTEasy’s logos, icons, and domain names are protected by trademark rights. Usage of these trademarks must adhere to the Commonhaus Foundation Trademark Policy.

Contributing

We welcome all forms of contribution, from code improvements to documentation and design. For details on how to contribute and the process your contributions will follow, please read our Contributing Guidelines.