Skip to content

docs: add MAINTAINERS.md file#1547

Open
TheJuanAndOnly99 wants to merge 8 commits into
mainfrom
add-maintainers-file
Open

docs: add MAINTAINERS.md file#1547
TheJuanAndOnly99 wants to merge 8 commits into
mainfrom
add-maintainers-file

Conversation

@TheJuanAndOnly99
Copy link
Copy Markdown
Member

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 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.

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>
@TheJuanAndOnly99 TheJuanAndOnly99 requested a review from a team as a code owner May 25, 2026 18:35
@netlify
Copy link
Copy Markdown

netlify Bot commented May 25, 2026

Deploy Preview for endearing-brigadeiros-63f9d0 canceled.

Name Link
🔨 Latest commit eee5dc5
🔍 Latest deploy log https://app.netlify.com/projects/endearing-brigadeiros-63f9d0/deploys/6a1d9caf26da8d0008f27c5e

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 25, 2026

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

@codecov
Copy link
Copy Markdown

codecov Bot commented May 25, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.65%. Comparing base (ffd6937) to head (eee5dc5).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1547   +/-   ##
=======================================
  Coverage   90.65%   90.65%           
=======================================
  Files          69       69           
  Lines        5690     5690           
  Branches      985      985           
=======================================
  Hits         5158     5158           
  Misses        514      514           
  Partials       18       18           

☔ View full report in Codecov by Sentry.
📢 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.

Signed-off-by: Juan Escalada <97265671+jescalada@users.noreply.github.com>
@jescalada jescalada changed the title Add MAINTAINERS.md file docs: add MAINTAINERS.md file May 26, 2026
@jescalada
Copy link
Copy Markdown
Contributor

Pinging @06kellyjac @JamieSlome @andypols @coopernetes @kriswest to add the missing emails, thanks! 🙏🏼

@linux-foundation-easycla
Copy link
Copy Markdown

linux-foundation-easycla Bot commented May 26, 2026

CLA Signed
The committers listed above are authorized under a signed CLA.

  • ✅ login: TheJuanAndOnly99 / name: Juan Estrella (7662397)
  • ✅ login: andypols / name: Andy Pols (acd2cb9)
  • ✅ login: jescalada / name: Juan Escalada (e9a0f3a, fc0b718)

@andypols
Copy link
Copy Markdown
Contributor

Pinging @06kellyjac @JamieSlome @andypols @coopernetes @kriswest to add the missing emails, thanks! 🙏🏼

Done

@jescalada
Copy link
Copy Markdown
Contributor

@andypols Whoops, it seems Claude sneaked into your commit as a co-author - you might have to remove the co-author line to fix the EasyCLA check...

Comment thread MAINTAINERS.md Outdated
Comment thread MAINTAINERS.md Outdated
@coopernetes coopernetes force-pushed the add-maintainers-file branch from ff8db34 to acd2cb9 Compare May 26, 2026 18:32
Co-authored-by: Thomas Cooper <57812123+coopernetes@users.noreply.github.com>
Co-authored-by: j-k <dev@j-k.io>
Signed-off-by: Thomas Cooper <57812123+coopernetes@users.noreply.github.com>
@coopernetes
Copy link
Copy Markdown
Contributor

coopernetes commented May 26, 2026

Rebased and removed the Co-Authored-By message from Andy's commit. EasyCLA is happy now. Formatting is unhappy with some UI based additions but let's get all the emails in first then we can apply formatting before merging.

Comment thread MAINTAINERS.md Outdated
kriswest added 2 commits May 28, 2026 13:11
Signed-off-by: Kris West <kristopher.west@natwest.com>
@kriswest
Copy link
Copy Markdown
Contributor

kriswest commented Jun 1, 2026

@JamieSlome do you want to return/continue as a maintainer of Git Proxy? If so we need you to update your email address in this PR (a MAINTAINERS.md file is being added to all FINOS repos to track maintainer appointments).

If you could let us know one way or the other it would be appreciated sir!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants