skyl is maintained in the open on GitHub. This page says who is responsible for what, and what you can expect when you open an issue or a pull request.
Current maintainers#
| Maintainer | Areas |
|---|---|
| BAGOMBEKA-JOB-DEV | Everything — core library, adapters, gateway, otel, release process |
The authoritative list is MAINTAINERS.md in the repository, and CODEOWNERS
controls review assignment.
What a maintainer does#
- Reviews and merges pull requests against the engineering rules.
- Cuts releases, following the multi-module process in Releasing — the order is not optional, and tags on the module proxy are immutable.
- Triages security reports through GitHub's private vulnerability reporting.
- Decides scope. The project has explicit non-goals, and saying no to a good idea that does not belong is part of the job.
What you can expect#
Issues get a response. A bug report with a reproduction against the sandbox is the fastest path to a fix, because it needs no credential to confirm.
Pull requests are reviewed against the written rules rather than against taste. If review asks for something, it should be traceable to a numbered rule — and if it is not, that is worth pushing back on.
Security reports are handled privately. Please do not open a public issue; see the Security Policy.
What is most useful right now#
Every adapter has now been exercised against its live provider API, so the wire mapping is confirmed rather than merely self-consistent. That was a snapshot taken on 2026-08-05, and providers change their formats without warning — so re-running the integration suite against a provider you use is still among the most useful things anyone can contribute, and recording a cassette from it improves the suite for everyone permanently.
After that: feature-matrix corrections. The matrix was written by reading the adapters, and if a cell no longer matches the code, that is a bug. Making drift somebody's problem is the only way it gets fixed.
Becoming a maintainer#
There is no formal process yet. Sustained, high-quality contribution — and a demonstrated feel for the project's non-goals — is the path. Open an issue if you want to talk about it.
Governance#
The project follows a Code of Conduct based on the
Contributor Covenant. Licensing is Apache 2.0, with per-module LICENSE files
and a NOTICE recording attributions.