mirror of
https://github.com/cozystack/cozystack.git
synced 2026-11-22 20:53:52 +09:00
Add an issue-template chooser and a feature-request template, and document in CONTRIBUTING and the README where each kind of contribution belongs: - bugs and concrete features -> issues in this repo - questions and early ideas -> GitHub Discussions - cross-cutting / architectural changes -> design proposals in cozystack/community Also reconciles the README, which routed feature requests to a Discussions category while the issue tracker is actually used for kind/feature issues. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>
1.4 KiB
1.4 KiB
name, about, labels, assignees
| name | about | labels | assignees |
|---|---|---|---|
| Feature request | Propose a concrete, scoped improvement to Cozystack | kind/feature |
Problem / motivation
What are you trying to do, and what is missing or painful today?
Proposed solution
What should Cozystack do? Be as concrete as you can — the API field, flag, value, or behavior you expect.
Scope check
- This affects a single component / package (if it spans many, consider a design proposal)
- I can describe the expected behavior concretely (if not, consider a Discussion first)
Alternatives considered
Other approaches you weighed, and why this one.
Additional context
Links, related issues, screenshots, prior art.