New Maintainer Nomination: Mark Scott

[LeighFinegold]

Per the project’s Governance policy, I am formally nominating Mark Scott (@markscott-ms) to become a Lead Maintainer of various modules on the FINOS Architecture as Code project.

Rationale

Mark has made substantial and sustained contributions to the project, including (but not limited to):

• Multiple meaningful enhancements to the schema, helping to clarify structure, intent, and extensibility
• Significant contributions across the shared, CLI, Docs and CALM Hub modules.
• Ongoing engagement in design discussions and reviews, demonstrating strong alignment with the project’s technical direction and collaborative principles

These contributions meet the criteria outlined in the Maintainer Qualifications section of the governance policy.

Voting Process

As per governance:

• All members of @finos/architecture-as-code-maintainers are eligible to participate
• Please register your vote by commenting with:
  • +1 to approve the nomination
  • -1 to reject the nomination
  • +0 to abstain

All discussion and voting will take place publicly in the comments on this issue.

Unless consensus is reached earlier, this issue will remain open for voting and will be closed on or after midnight on Thursday 15 January 2025, at which point the outcome will be recorded.

[LeighFinegold]

Actually it seems we don't have a formal process for the lead maintainers/ Code Owners. I will add it to the agenda for the next Thursday meeting. We can also discuss the process to remove people as well as that is not officially defined.

[rocketstack-matt]

+1

[jpgough-ms]

+1

[aamanrebello]

+1

[markscott-ms]

Given that I am in the @finos/architecture-as-code-maintainers group we could consider this matter closed?

As suggested in #2039 and #2055 I have created PR #2067 to revise the Maintainer list in README.md