chore: Add MAINTAINERS.md file

[TheJuanAndOnly99]

This PR adds a MAINTAINERS.md file to the root of this repository as part of a FINOS-wide effort to standardize maintainer signaling across all FINOS projects. An announcement was sent to community@finos.org with the full context, see announcement email here.

How this list was generated

The maintainers were determined from this repository's GitHub settings:

• Users with maintain or admin role on the repository
• Members of teams with maintain or admin permission

Each entry includes the GitHub username, name, and organization pulled from the user's public GitHub profile. Where name or organization is missing, a *please add ...* placeholder marks where to fill in the value. Email is optional: it is included when the user has a public GitHub email, otherwise the cell is left blank.

If no maintainers were detected automatically (e.g. your repo has no users or teams with maintain/admin role), the table is intentionally empty. Please populate it manually on this branch before merging and email help@finos.org.

What we need from this project's maintainers

1. Review the list for completeness and accuracy.
2. Update any incorrect or placeholder values (names, organization) directly on this branch. Email is optional.
3. Add anyone missing, edit the file in this PR if a maintainer was not automatically detected.
4. Merge when the list is accurate.

If your project does not need a MAINTAINERS.md for any reason, just close this PR and let us know at help@finos.org.

If this repository should instead be archived (e.g. it is no longer actively maintained or has been superseded), please email help@finos.org instead so we can coordinate the archival with you.

If you already have a MAINTAINERS.md file, you can close this PR. Please update your existing file if needed and place it in the root of the repository.

Multi-repo projects: share one MAINTAINERS.md

If this repository is part of a project with multiple repositories that share (and will continue to share) the same maintainers, you don't need a separate list per repo. Pick one repository (typically the project's main/umbrella repo) to host the canonical MAINTAINERS.md, and on every other repo replace the table in this PR with a short note pointing readers there, for example:

The maintainers of this repository are listed in the main project repository. See list here.

That way maintainer changes only need to be made in one place going forward.

Going forward: keeping the list current

To keep maintainer changes transparent and aligned with open governance:

• Any change to the maintainer list must be made via a PR to this file.
• If your project's governance requires a vote, document or link to the vote outcome in the PR description or comments.
• This gives the community a public audit trail of project leadership over time.

If you have any questions about the format or process, please email help@finos.org.

Thank you for your review!

[netlify]

✅ Deploy Preview for common-cloud-controls canceled.

Name	Link
🔨 Latest commit	1ccbc04
🔍 Latest deploy log	https://app.netlify.com/projects/common-cloud-controls/deploys/6a84c441d49a2f0008395c4a

[TheJuanAndOnly99]

Hi @eddie-knight can you help get this reviewed and merged? We don't necessarily need all the details (especially email) to be present before merging as long as the list of names + github usernames is correct and up to date we can marge and update the other fields later as needed.

[eddie-knight]

Suggested change

	| @Alexstpierrework | Alex St. Pierre | *please add organization* | *please add email* |
	| @aric-rosenbaum | Aric Rosenbaum | @redhat | *please add email* |
	| @ececon | *please add name* | *please add organization* | *please add email* |
	| @eddie-knight | Eddie Knight | *please add organization* | *please add email* |
	| @jared-lambert | Jared Lambert | Microsoft | *please add email* |
	| @jpower432 | Jennifer Power | Red Hat | jpower@redhat.com |
	| @lucaborella89 | Luca Borella | *please add organization* | *please add email* |
	| @mlysaght2017 | Michael Lysaght | *please add organization* | *please add email* |
	| @rgriffiths-scottlogic | Robert Griffiths | @ScottLogic | *please add email* |
	| @smendis-scottlogic | Sonali Mendis | Scott Logic | *please add email* |
	| @sshiells-scottlogic | Stevie Shiells | Scott Logic | sshiells@scottlogic.com |
	| @sublimino | Andrew Martin | @controlplaneio | *please add email* |
	| @zigmax | Maxime Coquerel | Royal Bank of Canada (RBC) | max.coquerel@gmail.com |
	| @aric-rosenbaum | Aric Rosenbaum | Red Hat | |
	| @eddie-knight | Eddie Knight | Revanite | |
	| @jpower432 | Jennifer Power | Red Hat | |
	| @mlysaght2017 | Michael Lysaght | Citi | |
	| @smendis-scottlogic | Sonali Mendis | Scott Logic | |
	| @sshiells-scottlogic | Stevie Shiells | Scott Logic | |
	| @zigmax | Maxime Coquerel | Royal Bank of Canada (RBC) | |

@aric-rosenbaum @sshiells-scottlogic we're overdue for a revamp on the outdated governance docs, and I think the README is out of date as well. We have avoided using the term "maintainer" in the past, favoring things like "WG Lead" and "Steerco Member," but I suspect we can't stay on that track.

Here's the list I submitted on the fly for the TOC presentation yesterday, focusing on technical contributors since we have any updated list of maintainers:

• Eddie Knight (Revanite)
• Rob Moffat (FINOS)
• Sonali Mendis (Scott Logic)
• Stevie Shiells (Scott Logic)
• Michael Lysaght (Citi)
• Leroy Abhikui (LSEG)
• Dave Reeve (Morgan Stanley)
• Jenn Power (Red Hat)
• Maxime Coquerel (RBC)
• Sankara Ramakrishnan (Black Rock)

[sshiells-scottlogic]

@eddie-knight do you want to raise an issue to update the docs?

I can get the Scott Logic folks working on the website to review the content and they may be able to make some updates based on the new content on the website.

@gbalysevaite FYI

[eddie-knight]

Added #1158