CoreLink Platform public repositories are currently maintained by the CoreLink engineering team.
Changes are evaluated based on:
- user and integration value;
- public API consistency;
- backward compatibility;
- security and tenant isolation;
- implementation independence;
- operational maintainability.
Material changes to public APIs, schemas, SDK behavior, authentication, events, or webhooks should begin with an issue or design proposal.
Breaking changes require:
- documented motivation;
- compatibility assessment;
- migration path;
- versioning decision;
- maintainer approval.
Repository maintainers are responsible for:
- reviewing pull requests;
- managing releases;
- enforcing compatibility policies;
- responding to security reports;
- maintaining public documentation.
The maintainer list may be expanded as the project and contributor community grow.