The current Maintainers (listed Code Owners) will be assigned to review the Pull Request, and the PR will be merged once two Maintainers approve the request
If the Baseline Maintainer request is denied or poses concerns, the proposer or other Baseline Core Devs can escalate to the TSC
What is expected of Baseline Maintainers?
To retain Maintainer permissions and status, Baseline Maintainers are required to comply with the following,
Attendance Policy: Maintainers must notify the 'maintainer' Slack group or a community leader if unable to attend. If a Maintainer misses three consecutive meetings without prior notice, a community member will submit a PR to remove the member's GitHub ID from the Code Owners File
If a Maintainer is removed due to the attendance policy, they must attend 2 Core Dev sessions, notify the group of intent to re-commit, then submit the PR to be added back to the Code Owners File.
Show commitment over time by timely review of Pull Requests
Follow branch, PR, code, project style, and testing guidelines
Be reliable in completing issues to which they have been assigned
Demonstrate competency in software development or specification writing
Have a high degree of understanding of the project architecture
Be welcoming to others in the community who are using or interested in the protocol
Contribute in ways that substantially improve the quality of the project and the experience of people who use it
How to stop being a Baseline Core Developer or Maintainer?
To step away from being a Baseline Core Developer, you can notify the other core developers you would like to relinquish your core developer status.
What can take away your Core Dev status?
You stop reviewing PR's, responding to messages, answering emails, and/or generally ghost the project.
You are disrespectful towards anyone in the community and/or involved in the project.
You are disruptive to the general process of maintaining the project, meetings, discussions, issues, or other.
Two-thirds of all current Maintainers constitute a quorum for a meeting involving a question of removal. A simple majority vote from Maintainers is required to remove a Baseline Core Dev, but the TSC may be brought in to arbitrate if the Baseline Core Developer to be removed or any other Baseline Core Developer wishes to dispute the action. See Governance **** for details.