Calandria community
Calandria’s community lives on GitHub so decisions remain searchable and connected to the work; GitHub is the canonical record for bugs, proposals, and releases.
Where to go
| You want to… | Use |
|---|---|
| Propose or vote on a feature | Ideas in GitHub Discussions |
| Ask for help | Q&A in GitHub Discussions |
| Show what you built | Show and tell |
| Report a reproducible bug | Bug report |
| Fix or improve Calandria | Contributing guide |
| Report a vulnerability | Security policy |
Search before opening a new thread. Add the problem you’re solving, your current workaround, and why the outcome matters; that context is more useful than a proposed UI alone.
How ideas become features
- New ideas begin in Discussions, where others can add use cases and vote.
- Maintainers triage ideas as Considering, Planned, Needs evidence, or Not planned.
- Accepted ideas become scoped GitHub issues before implementation begins.
- The issue and pull request link back to the original discussion.
- Release notes close the loop when the feature ships.
The roadmap is directional, not a promise. A focused pull request may ship before a popular idea when it is safer or unlocks other work.
Maintainers review new threads weekly. A lightweight public project can track only accepted work under Now, Next, and Later; uncommitted ideas stay in Discussions until their problem and scope are clear.
Community standards
Be respectful, constructive, and curious. Critique ideas and code, not people. Do not post private repository content, credentials, or security reports in public channels.
For contribution mechanics, tests, and the Developer Certificate of Origin, see CONTRIBUTING.md.