|
| 1 | +--- |
| 2 | +name: 👥 Maintainer Update |
| 3 | +about: Propose adding a new maintainer or removing an existing maintainer |
| 4 | +--- |
| 5 | + |
| 6 | +## Maintainer Update Proposal |
| 7 | + |
| 8 | +### Type of Update: |
| 9 | + |
| 10 | +<!-- Select one by placing an 'x' in the brackets --> |
| 11 | + |
| 12 | +- [ ] **Add New Maintainer** - Proposing to add a new maintainer to the project |
| 13 | +- [ ] **Remove Maintainer** - Proposing to remove an existing maintainer from the project |
| 14 | + |
| 15 | +--- |
| 16 | + |
| 17 | +### Maintainer Details: |
| 18 | + |
| 19 | +**Name:** <!-- Full name of the maintainer --> |
| 20 | + |
| 21 | +**GitHub Handle:** @<!-- GitHub username --> |
| 22 | + |
| 23 | +**Component/Module:** <!-- Which component(s) will they maintain (e.g., CALM Hub UI, CLI, Shared, etc.) or "All" --> |
| 24 | + |
| 25 | +--- |
| 26 | + |
| 27 | +## For New Maintainer Additions |
| 28 | + |
| 29 | +<!-- Complete this section if proposing to ADD a new maintainer --> |
| 30 | + |
| 31 | +### Contribution History: |
| 32 | + |
| 33 | +...describe the substantial contributions this person has made to the project, including: |
| 34 | + |
| 35 | +- Number and significance of pull requests merged |
| 36 | +- Participation in issue discussions and reviews |
| 37 | +- Documentation contributions |
| 38 | +- Community engagement (Office Hours, meetings, etc.) |
| 39 | +- Any other relevant contributions |
| 40 | + |
| 41 | +### Why This Person Should Be a Maintainer: |
| 42 | + |
| 43 | +...explain why this person is qualified and why their maintainer status would benefit the project... |
| 44 | + |
| 45 | +### Links to Contributions: |
| 46 | + |
| 47 | +<!-- Provide links to key PRs, issues, or other contributions --> |
| 48 | + |
| 49 | +- PR: |
| 50 | +- Issue: |
| 51 | +- Other: |
| 52 | + |
| 53 | +--- |
| 54 | + |
| 55 | +## For Maintainer Removals |
| 56 | + |
| 57 | +<!-- Complete this section if proposing to REMOVE a maintainer --> |
| 58 | + |
| 59 | +### Reason for Removal: |
| 60 | + |
| 61 | +<!-- Select one by placing an 'x' in the brackets --> |
| 62 | + |
| 63 | +- [ ] **Voluntary** - The maintainer has requested to be removed |
| 64 | +- [ ] **Inactivity** - The maintainer has been inactive (see criteria below) |
| 65 | + |
| 66 | +### Rationale: |
| 67 | + |
| 68 | +...provide clear reasoning for the removal proposal: |
| 69 | + |
| 70 | +**For Voluntary Removals:** |
| 71 | +- State that the maintainer has requested to step down |
| 72 | +- Include any relevant context they've provided (optional) |
| 73 | + |
| 74 | +**For Inactivity Removals:** |
| 75 | +- Confirm the maintainer has had no commits AND no involvement in issues/PRs for **3+ months** |
| 76 | +- Specify the period of inactivity (e.g., "no activity since [DATE]") |
| 77 | +- Note: This removal proposal does NOT reflect negatively on the individual, but rather acknowledges changes in their ability to contribute |
| 78 | +- Explain why having the README.md reflect active maintainers is important for the project |
| 79 | + |
| 80 | +### Notice Period: |
| 81 | + |
| 82 | +<!-- For inactivity removals only --> |
| 83 | + |
| 84 | +**Issue Created:** <!-- Date this issue was created --> |
| 85 | + |
| 86 | +**Notice Period Ends:** <!-- Date 4 weeks from creation --> |
| 87 | + |
| 88 | +**Vote May Proceed After:** <!-- Same as notice period end date --> |
| 89 | + |
| 90 | +### Maintainer Notification: |
| 91 | + |
| 92 | +<!-- For inactivity removals only - confirm the maintainer has been notified --> |
| 93 | + |
| 94 | +- [ ] Maintainer tagged in this issue |
| 95 | +- [ ] Maintainer contacted via email (if contact info available) |
| 96 | +- [ ] Other notification methods used (specify): |
| 97 | + |
| 98 | +--- |
| 99 | + |
| 100 | +## Voting Process |
| 101 | + |
| 102 | +As per [Governance.md](https://github.com/finos/architecture-as-code/blob/main/Governance.md): |
| 103 | + |
| 104 | +- All members of **@finos/architecture-as-code-maintainers** are eligible to participate |
| 105 | +- Please register your vote by commenting with: |
| 106 | + - `+1` to approve the proposal |
| 107 | + - `-1` to reject the proposal |
| 108 | + - `+0` to abstain |
| 109 | + |
| 110 | +**For New Maintainer Additions:** |
| 111 | +- The nomination MUST receive a majority of votes to be approved |
| 112 | +- All discussion and voting will take place publicly in the comments on this issue |
| 113 | + |
| 114 | +**For Voluntary Removals:** |
| 115 | +- No vote is required; Maintainers should acknowledge and proceed with removal |
| 116 | + |
| 117 | +**For Inactivity Removals:** |
| 118 | +- A minimum **4-week notice period** MUST be observed before voting |
| 119 | +- If the maintainer responds or resumes activity during the notice period, this issue SHOULD be closed without a vote |
| 120 | +- After the notice period, a vote will be held if the maintainer has not responded or resumed activity |
| 121 | + |
| 122 | +**Voting Period:** |
| 123 | + |
| 124 | +Unless consensus is reached earlier, this issue will remain open for voting and will be closed **on or after [DATE - typically 1 week after notice period for removals, or 1-2 weeks for additions]**, at which point the outcome will be recorded. |
| 125 | + |
| 126 | +--- |
| 127 | + |
| 128 | +## Implementation Checklist |
| 129 | + |
| 130 | +<!-- To be completed by the Lead Maintainer or designated Maintainer after approval --> |
| 131 | + |
| 132 | +**For Additions:** |
| 133 | +- [ ] Add maintainer to the GitHub team: `@finos/architecture-as-code-maintainers` |
| 134 | +- [ ] Update `README.md` to list the new maintainer |
| 135 | +- [ ] Update `.github/CODEOWNERS` if they will be owning specific components |
| 136 | +- [ ] Welcome the new maintainer in the project channels |
| 137 | + |
| 138 | +**For Removals:** |
| 139 | +- [ ] Remove maintainer from the GitHub team: `@finos/architecture-as-code-maintainers` |
| 140 | +- [ ] Update `README.md` to remove the maintainer from the list |
| 141 | +- [ ] Update `.github/CODEOWNERS` to reassign their owned components |
| 142 | +- [ ] Thank the maintainer for their contributions in the project channels (if appropriate) |
| 143 | + |
| 144 | +--- |
| 145 | + |
| 146 | +## Additional Context |
| 147 | + |
| 148 | +...add any other relevant context, history, or information about this proposal... |
0 commit comments