Add MAINTAINERS.md file by TheJuanAndOnly99 · Pull Request #1900 · finos/FDC3

TheJuanAndOnly99 · 2026-05-25T21:41:51Z

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

Review the list for completeness and accuracy.
Update any incorrect or placeholder values (names, organization, email) directly on this branch.
Add anyone missing, edit the file in this PR if a maintainer was not automatically detected.
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!

Signed-off-by: Juan Estrella <juan.estrella@finos.org>

netlify · 2026-05-25T21:41:55Z

✅ Deploy Preview for fdc3 canceled.

Name	Link
🔨 Latest commit	`ba35861`
🔍 Latest deploy log	https://app.netlify.com/projects/fdc3/deploys/6a297617c2681d0008233a63

codecov-commenter · 2026-05-25T21:46:06Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.77%. Comparing base (25cf6aa) to head (ba35861).
⚠️ Report is 6 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1900   +/-   ##
=======================================
  Coverage   95.77%   95.77%           
=======================================
  Files          69       69           
  Lines        4879     4879           
  Branches      738      804   +66     
=======================================
  Hits         4673     4673           
  Misses        206      206

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

kriswest · 2026-05-29T10:55:25Z

@finos/fdc3-maintainers & @finos/fdc3-editors as discussed at #1904 we've got a long list of maintainers, several of whom haven't been active for a 1 or more years, and there was consensus that we should use this as an opportunity to the ask all maintainers and editors to recommit to their role or role off.

We will include both Maintainers and Editors in the file.

Hence, if you'd like to continue as an FDC3 maintainer or editor we ask that update your organisation and email in this PR (enabling us to complete the PR and merge it). Otherwise, we'll propose changes to remove you from the file and the associated team (@finos/fdc3-maintainers & @finos/fdc3-editors) - I think in some cases we may have already rolled people off the mailing list and slack group, making this the final step.

If you've been inactive for a while but anticipate getting involved again some day soon reach out and update your details in this PR!

Co-authored-by: Kris West <kristopher.west@natwest.com> Co-authored-by: Roaders <10414642+Roaders@users.noreply.github.com> Co-authored-by: Hugh Troeger <troeger.hugh@gmail.com> Co-authored-by: Julianna Langston <74684272+julianna-ciq@users.noreply.github.com> Co-authored-by: kemerava <52539182+kemerava@users.noreply.github.com> Co-authored-by: Johan Sandersson <98814236+openfin-johans@users.noreply.github.com>

Co-authored-by: Kris West <kristopher.west@natwest.com>

kriswest

LGTM

kriswest · 2026-06-10T14:35:57Z

@finos/fdc3-maintainers can someone else approve and merge this pls - I had last push.

Add MAINTAINERS.md file

253d24c

Signed-off-by: Juan Estrella <juan.estrella@finos.org>

TheJuanAndOnly99 requested a review from a team as a code owner May 25, 2026 21:41

kriswest reviewed May 28, 2026

View reviewed changes