|
| 1 | += Governance |
| 2 | +:toc: |
| 3 | +:awestruct-layout: community-standard |
| 4 | + |
| 5 | +This document outlines the governance model for Hibernate projects. |
| 6 | +This governance model is designed to uphold the principles of transparency, open collaboration, and community involvement. |
| 7 | + |
| 8 | +[[roles]] |
| 9 | +== Roles and Responsibilities |
| 10 | + |
| 11 | +- **Contributors:** Anyone who contributes to Hibernate projects in any form. |
| 12 | +- **Members:** Contributors eligible for write access to a Hibernate code repository. |
| 13 | + Responsible for reviewing and merging contributions in their area of expertise. |
| 14 | +- **Project Leaders:** Elected members (at most one per code repository) with higher decision power whenever the project they lead is directly affected. |
| 15 | + Responsible for steering project direction, and for enforcing compliance with requirements of the Commonhaus Foundation. |
| 16 | + |
| 17 | +Small or inactive projects may not have a leader, |
| 18 | +in which case Members interested in the project will steer the project direction. |
| 19 | + |
| 20 | +[[decision-making]] |
| 21 | +== Decision-Making |
| 22 | + |
| 23 | +Hibernate projects follow the https://www.commonhaus.org/bylaws/decision-making.html[Commonhaus decision-making process], with one additional provision. |
| 24 | + |
| 25 | +Consensus-seeking (lazy consensus):: |
| 26 | +Projects primarily aims for a consensus-based decision-making process, where Members and active contributors discuss and come to an agreement. |
| 27 | +Voting:: |
| 28 | +In situations where consensus cannot be reached, decisions may be made through a simple majority vote among Members. |
| 29 | +Conflict Resolution:: |
| 30 | +If conflicts arise, Members are responsible for facilitating a resolution. The https://www.commonhaus.org/bylaws/cf-council.html[Commonhaus Foundation Council] (CFC) can be asked to mediate the discussion, if necessary. |
| 31 | +Overruling _(Hibernate-specific)_:: |
| 32 | +Project Leaders hold the power to overrule any decision directly affecting the project they lead. |
| 33 | +This allows swift decisions on urgent or critical matters. |
| 34 | +Appeal to such overruling follows conflict resolution rules described above. |
| 35 | +// This is intended to balance the very extensive power of project leaders. |
| 36 | +In extreme cases, abuse of this power may result in the role of Project Leader being revoked (see below). |
| 37 | + |
| 38 | +[[role-granting-revoking]] |
| 39 | +== Role granting/revoking |
| 40 | + |
| 41 | +The role of Member or Project Leader is granted or revoked through the <<decision-making,decision-making process>>, |
| 42 | +with additional restrictions: |
| 43 | + |
| 44 | +1. The discussion must happen on the Hibernate development mailing list, as listed in the link:/community[Community page on this website]. |
| 45 | +// This prevents a Project Leader overruling their own revocation, or arbitrarily instating/revoking others. |
| 46 | +2. Project Leaders may not use their overruling power. |
| 47 | +// This is consistent with Commonhaus' own processes, which use supermajority for critical decisions. |
| 48 | +3. If consensus cannot be reached, |
| 49 | + the ensuing vote requires supermajority approval by two-thirds of voting Members, instead of simple majority. |
| 50 | +// This is long on purpose, to eliminates the risk of a decision being taken "in absentia" during e.g. holidays. |
| 51 | +// The assumption is that decisions around the project can be taken collectively, or by the previous leader, in the interim. |
| 52 | +4. Discussions regarding the role of Project Leader may not last less than 30 days. |
| 53 | + |
| 54 | +Eligible candidates are: |
| 55 | + |
| 56 | +For the role of Member:: |
| 57 | +Any contributor. |
| 58 | +For the role of Project Leader:: |
| 59 | +Any contributor to the project they will lead, provided the candidate is a Commonhaus Foundation member, |
| 60 | +// TODO update link upon the PR getting merged. |
| 61 | +and agrees to become a Signatory of the https://github.com/commonhaus/foundation/pull/219/files#diff-64f58a8e70e16b011f35a30256797c538e6a951da4e9985943b55f4abe6e94b1[Commonhaus Fiscal Sponsorship Agreement] before taking on their new role. |
| 62 | + |
| 63 | +Members and Project Leaders keep their role indefinitely, unless they resign or a new decision revokes their role. |
| 64 | + |
| 65 | +The list of Members and Project Leaders is kept up-to-date on the link:/community/team["Team" page] of this website. |
| 66 | + |
| 67 | +[[code-of-conduct]] |
| 68 | +== Code of Conduct |
| 69 | + |
| 70 | +All participants in Hibernate projects are expected to adhere to the https://www.commonhaus.org/policies/code-of-conduct/[Commonhaus Foundation Code of Conduct]. Please ensure you are familiar with its guidelines and expectations, as it's essential for maintaining a positive and collaborative environment. |
| 71 | + |
| 72 | +[[trademark-policy]] |
| 73 | +== Trademark Policy |
| 74 | + |
| 75 | +The Hibernate logos, icons, and domain names are protected by trademark rights. Usage of these trademarks must adhere to the https://www.commonhaus.org/policies/trademark-policy/[Commonhaus Foundation Trademark Policy]. |
| 76 | + |
| 77 | +[[contributing]] |
| 78 | +== Contributing |
| 79 | + |
| 80 | +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 link:/community/contribute/[Contributing Guidelines]. |
0 commit comments