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!

[github-actions]

Workflow Telemetry - Build CI / Build

Workflow telemetry for commit 78942a59286269040904f1b24d97f18bc64cbe38
You can access workflow job details here

Step Trace

gantt
	title Build
	dateFormat x
	axisFormat %H:%M:%S
	Set up job : milestone, 1779745391000, 1779745392000
	Checkout repo : 1779745392000, 1779745395000
	Java setup : 1779745395000, 1779745402000
	Configure git : 1779745402000, 1779745402000
	Download deps and plugins : 1779745402000, 1779745538000
	Collect Workflow Telemetry : 1779745538000, 1779745539000

Loading

[github-actions]

Workflow Telemetry - Build CI / Build

Workflow telemetry for commit 8824d9e23e336acf46209a3683c587c1aa8321ad
You can access workflow job details here

Step Trace

gantt
	title Build
	dateFormat x
	axisFormat %H:%M:%S
	Set up job : milestone, 1780084261000, 1780084262000
	Checkout repo : 1780084262000, 1780084265000
	Java setup : 1780084265000, 1780084299000
	Configure git : 1780084299000, 1780084299000
	Download deps and plugins : 1780084299000, 1780084342000
	Collect Workflow Telemetry : 1780084342000, 1780084342000
	Build : 1780084342000, 1780084697000

Loading

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

Workflow Telemetry - Build CI / Build

Workflow telemetry for commit e4b72899aa41dcdebd5da09951232e768d8c7f5d
You can access workflow job details here

Step Trace

gantt
	title Build
	dateFormat x
	axisFormat %H:%M:%S
	Set up job : milestone, 1782853513000, 1782853514000
	Checkout repo : 1782853514000, 1782853518000
	Java setup : 1782853518000, 1782853523000
	Configure git : 1782853523000, 1782853523000
	Download deps and plugins : 1782853523000, 1782855926000
	Collect Workflow Telemetry : 1782855926000, 1782855927000

Loading

[github-actions]

Workflow Telemetry - Build CI / Build

Workflow telemetry for commit f32a266765429b341df7c9f618a20acbbc707014
You can access workflow job details here

Step Trace

gantt
	title Build
	dateFormat x
	axisFormat %H:%M:%S
	Set up job : milestone, 1786625643000, 1786625645000
	Checkout repo : 1786625645000, 1786625649000
	Java setup : 1786625649000, 1786625700000
	Configure git : 1786625700000, 1786625700000
	Download deps and plugins : 1786625700000, 1786625735000
	Collect Workflow Telemetry : 1786625735000, 1786625735000
	Build : 1786625735000, 1786626087000
	Compute image version : 1786626087000, 1786626087000

Loading