|
| 1 | +Diversity Initiative Governance |
| 2 | +=============================== |
| 3 | + |
| 4 | +Membership |
| 5 | +---------- |
| 6 | + |
| 7 | +Membership of Symfony's Diversity Initiative is open to any member of the |
| 8 | +Symfony community; to avoid the risk of elitism or meritocracy, no requirement |
| 9 | +is needed to be involved. All members, at any time, are invited to put forward |
| 10 | +ideas and suggestions as a proposal for an actionable item. |
| 11 | + |
| 12 | +Guidance |
| 13 | +-------- |
| 14 | + |
| 15 | +The project leader, Fabien Potencier, is responsible for publicly appointing |
| 16 | +five (5) key players of the initiative to provide guidance and drive it forward, |
| 17 | +but also retains the right to revoke any of the key players at any time. These |
| 18 | +guiding key players should: |
| 19 | + |
| 20 | +* Be committed to the initiative's cause and have joined because they want to |
| 21 | + help the initiative to deliver its purpose most effectively for the |
| 22 | + community's benefit. |
| 23 | +* Recognize that meeting the initiative's purpose is an ongoing effort. |
| 24 | +* Be committed to good governance and want to contribute to the initiative's |
| 25 | + continued improvement. |
| 26 | + |
| 27 | +Veto |
| 28 | +~~~~ |
| 29 | + |
| 30 | +The project leader (Fabien Potencier) will have the right to veto any actionable |
| 31 | +item, regardless of the vote of the initiative's key players. The project leader |
| 32 | +may, at their discretion, also appoint other people from among the initiative's |
| 33 | +key players to also have the right to veto - in such a case these people are |
| 34 | +expected to use appropriate judgement to know when to use a "no" vote or a veto. |
| 35 | +Any single veto will reject an actionable item. |
| 36 | + |
| 37 | +The purpose of having members with the right to veto is to prevent a "people's |
| 38 | +majority" from overruling the core interests of the Symfony project. This will |
| 39 | +encourage communication between proposing members, the initiative's key players |
| 40 | +and the Core Team to create realistic proposals, and in return any veto will |
| 41 | +come with a full explanation (not just a justification). |
| 42 | + |
| 43 | +Advice Process |
| 44 | +~~~~~~~~~~~~~~ |
| 45 | + |
| 46 | +When a proposal on an actionable item is ready to be decided on, insight from |
| 47 | +the community (advice, general consensus, or non-binding poll) should be |
| 48 | +requested from the wider community - this will aim to include both those who |
| 49 | +will be meaningfully affected and those with meaningful expertise in the matter |
| 50 | +at hand. |
| 51 | +This feedback will enable the key players to have the confidence to vote for the |
| 52 | +best possible decision according to the information they have available, knowing |
| 53 | +that the responsibility they accept for said vote is justified. |
| 54 | + |
| 55 | +Voting |
| 56 | +~~~~~~ |
| 57 | + |
| 58 | +Key players have the right to vote on proposals for actionable items. |
| 59 | +The quorum of "yes" or "no" votes required for a decision to be considered valid |
| 60 | +is at least 75% of active, appointed key players - to abstain from voting means |
| 61 | +that vote will not be counted towards the quorum. |
| 62 | +For an actionable item to pass, approval from greater than 50% of the voting key |
| 63 | +players is required. Use or management of finances/donations require at least a |
| 64 | +two-thirds majority to pass. |
| 65 | + |
| 66 | +Guidance Principles |
| 67 | +------------------- |
| 68 | + |
| 69 | +Purpose |
| 70 | +~~~~~~~ |
| 71 | + |
| 72 | +The initiative should be led by an effective team of key players that provide |
| 73 | +strategic guidance in line with the initiative's aims and values, including a |
| 74 | +shared understanding with fellow key players to ensure that these are being |
| 75 | +delivered effectively and sustainably. |
| 76 | + |
| 77 | +Integrity |
| 78 | +~~~~~~~~~ |
| 79 | + |
| 80 | +Key players should act with integrity: adopting values which help achieve the |
| 81 | +initiative's purposes, even where difficult or unpopular decisions are required. |
| 82 | +Key players should undertake their duties, aware of the importance of confidence |
| 83 | +and trust in the initiative from the wider community, and ultimately |
| 84 | +acknowledges shared responsibility for the reputation of the Symfony project |
| 85 | +like the Core Team. |
| 86 | + |
| 87 | +Decision-making Effectiveness |
| 88 | +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 89 | + |
| 90 | +Key players should work as an effective team, using the appropriate balance of |
| 91 | +skills, experience, backgrounds and knowledge to make sure its decision-making |
| 92 | +processes are informed and equitable. Risk assessment and management systems |
| 93 | +should be set up and monitored. |
| 94 | + |
| 95 | +Openness and Accountability |
| 96 | +~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 97 | + |
| 98 | +The behaviour and conduct of the initiative's key players sets the tone for the |
| 99 | +rest of the community. Key players should lead by example to create a culture |
| 100 | +that enables members to feel it is safe to suggest, question and challenge - |
| 101 | +rather than avoid - difficult ideas and topics. Key players guide the initiative |
| 102 | +in being transparent, accountable and open. |
| 103 | + |
| 104 | +Adaptability |
| 105 | +~~~~~~~~~~~~ |
| 106 | + |
| 107 | +The initiative should establish processes that do not require any one person to |
| 108 | +hold specific positions while being adaptable to accommodate unforeseen needs of |
| 109 | +the community, especially as membership and involvement grows over time (changes |
| 110 | +to key player appointment will have to be approved by the current system, which |
| 111 | +is Fabien Potencier). |
0 commit comments