Direct issue creation is disabled in this repository. Please start with a Discussion.
Kynetic follows a workflow observed across many healthy open-source projects: Discussions are used for exploration and clarification, while the issue tracker is reserved for well-defined, actionable work. Feature ideas, questions, and potential problems should begin as discussions. When a discussion converges on a clearly scoped, reproducible issue or concrete task, a maintainer will convert it into an Issue.
This separation improves signal quality. Across the broader open-source ecosystem, the majority of items initially reported as “issues” tend to fall into one of three categories: usage misunderstandings, environment- or configuration-specific problems, or requests for functionality that has not yet been implemented. Even legitimate feature requests are often under specified at first and require iteration before they are ready to be worked on.
Using Discussions as the entry point allows these cases to be resolved, clarified, or refined without cluttering the issue tracker. As a result, Issues remain a reliable list of work that is ready for contributors to pick up.
If a Discussion identifies a real defect or a concrete improvement that can be confirmed or reproduced, a maintainer will promote it to an Issue. Users are not expected to duplicate effort or refile anything manually.
This approach helps keep Kynetic’s development process focused, efficient, and contributor-friendly.
Direct issue creation is disabled in this repository. Please start with a Discussion.
Kynetic follows a workflow observed across many healthy open-source projects: Discussions are used for exploration and clarification, while the issue tracker is reserved for well-defined, actionable work. Feature ideas, questions, and potential problems should begin as discussions. When a discussion converges on a clearly scoped, reproducible issue or concrete task, a maintainer will convert it into an Issue.
This separation improves signal quality. Across the broader open-source ecosystem, the majority of items initially reported as “issues” tend to fall into one of three categories: usage misunderstandings, environment- or configuration-specific problems, or requests for functionality that has not yet been implemented. Even legitimate feature requests are often under specified at first and require iteration before they are ready to be worked on.
Using Discussions as the entry point allows these cases to be resolved, clarified, or refined without cluttering the issue tracker. As a result, Issues remain a reliable list of work that is ready for contributors to pick up.
If a Discussion identifies a real defect or a concrete improvement that can be confirmed or reproduced, a maintainer will promote it to an Issue. Users are not expected to duplicate effort or refile anything manually.
This approach helps keep Kynetic’s development process focused, efficient, and contributor-friendly.