From 9910181040eab4150ccea2eecfcaca3bae70f6c2 Mon Sep 17 00:00:00 2001 From: Ligia Zanchet Date: Tue, 17 Feb 2026 22:47:52 +0100 Subject: [PATCH] Add maintenance expectations for Kilo community projects Added maintenance expectations for community projects using the Kilo name, including guidelines for compatibility checks, updates, support, and documentation. --- packages/kilo-docs/pages/contributing/ecosystem.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/packages/kilo-docs/pages/contributing/ecosystem.md b/packages/kilo-docs/pages/contributing/ecosystem.md index fc23a8374d1..4a0c8e6cbb9 100644 --- a/packages/kilo-docs/pages/contributing/ecosystem.md +++ b/packages/kilo-docs/pages/contributing/ecosystem.md @@ -14,6 +14,15 @@ This naming convention is important because it ensures: - **Maintenance:** Users understand the product is maintained and supported by you (the community creator), not the core Kilo team. - **Clarity:** New users can easily distinguish between official Kilo releases and the diverse range of community-built integrations. +## Maintenance Expectations +To ensure a high-quality experience for all users, we ask that maintainers using the Kilo name commit to keeping their projects active and aligned with the current ecosystem. Specifically, we expect community projects to: + +- **Conduct Monthly Compatibility Checks:** Verify that the integration remains functional with the latest Kilo versions and APIs at least once per month. +- **Proactive Updates:** Address breaking changes promptly when core platform updates impact your project's functionality. +- **Responsive Support:** Maintain a reasonable timeframe for responding to critical bugs or security reports from users. +- **Version Documentation:** Clearly state which versions of Kilo are supported and list any known limitations or requirements. + +Note: Projects that become abandoned, unmaintained, or persistently incompatible may be asked to remove the "Kilo" name to prevent user frustration and ensure the ecosystem remains reliable. ## Brand Assets & Logos Developers are welcome to use any logos available in our open-source repositories to help identify their project's compatibility with Kilo. Please ensure they are used to indicate association or compatibility (e.g., "Works with Kilo") and not in a way that suggests the project is an official Kilo product.