Looking for another maintainer

[patlux]

I'm looking for another maintainer. If you're interested, leave a comment here.

[pierreraby]

Hi! I'd be interested in helping out. Happy to help wherever needed — whatever is most useful to you.

[karaaslanz]

Hi Pat — I’d be interested in helping as another maintainer.

My recent OSS work has focused on TypeScript/developer tooling, reliability fixes, regression-focused testing, PR review, and maintenance hygiene.

I’d be happy to help with issue triage, focused PR review, CI/regression coverage, provider compatibility, release hygiene, and small reliability fixes. I prefer starting with a scoped area, building context through real maintenance work, and taking on broader responsibility as trust develops.

If that sounds useful, let me know where you’d prefer me to start.

[patlux]

Thanks @pierreraby and @karaaslanz — I’d be happy to have both of you on board as co-maintainers! I’ve sent you collaborator invitations.

Once you’ve accepted, you can triage issues, review and merge PRs after CI passes, and cut releases without waiting for me.

I’ve set up and tested automated publishing through GitHub Actions and npm Trusted Publishing. The release flow is: release PR → green CI → merge into main → push the version tag. You don’t need npm credentials.

CONTRIBUTING.md covers development and tests; RELEASE.md has the release and recovery steps.

@karaaslanz, starting with CI/regression coverage or provider compatibility sounds good if that’s what you’d enjoy. @pierreraby, feel free to pick up whichever issues or PRs interest you. There’s no expectation to take on everything at once.

Let me know what you’d like to start with. Thanks again for offering to help!

[pierreraby]

Thanks — invitation accepted, so the CODEOWNERS entries are live now.

I'd like to start with #120: I've been through it locally and everything passes, including the host tests against real pi and omp. I'll leave the full review on the PR, and unless you want a look first I'll update the branch and merge once CI is green again.

After that, #89 — I'd start with the deterministic UTC window/weekend tests you suggested.

@karaaslanz — #120 brushes against provider compatibility, so happy to split it with you rather than double up.