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, organization, and email pulled from the user's public GitHub profile. Where any field is missing on the profile, a *please add ...* placeholder marks where to fill in the value.

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, email) directly on this branch.
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!

[kriswest]

I'm checking on other maintainers on our end and whether contribution to the project will resume (very much still used and maintained internally)

[kriswest]

We've got someone new to appoint as a maintainer of this project @TheJuanAndOnly99 - to replace @Vivek-NatWest (who is still with us but has moved on to other duties)and intend to revive its maintenance. We'll get started on a PR to do that over the next few weeks with our intended maintainer and then seek to appoint them as soon as thats contributed, if that works for you @TheJuanAndOnly99.

[TheJuanAndOnly99]

@kriswest perfect works for me!

[kriswest]

@himanksegar is the developer I'll be working with to revive maintenance and will seek to appoint once we've got a PR raised.

[kriswest]

Moved to a different area in NWG and is unlikely to continue to contribute to maintenance.

Suggested change

| @Vivek-NatWest | *please add name* | *please add organization* | *please add email* |

Leaving as a suggestion for now as they may be able to help with appointing a new maintainer to take over.

[kriswest]

Moved to a different area in NWG and is unlikely to continue to contribute to maintenance.

Suggested change

| @manish-nwm | *please add name* | *please add organization* | *please add email* |

Leaving as a suggestion for now as they may be able to help with appointing a new maintainer to take over.