Add README and issue templates (support + feature request)
This commit is contained in:
commit
7e462e9c0d
3 files changed
+97
No files matched your search
@@ -0,0 +1,27 @@
|
|||||||
|
---
|
||||||
|
name: "Feature request"
|
||||||
|
about: "Propose a new capability or improvement."
|
||||||
|
title: ""
|
||||||
|
labels: "enhancement"
|
||||||
|
assignees: ""
|
||||||
|
---
|
||||||
|
|
||||||
|
## What's the idea?
|
||||||
|
|
||||||
|
<!-- A one-paragraph description of the feature or improvement. -->
|
||||||
|
|
||||||
|
## Why does it matter?
|
||||||
|
|
||||||
|
<!-- What problem does it solve, or what value does it add for members? -->
|
||||||
|
|
||||||
|
## Who is it for?
|
||||||
|
|
||||||
|
<!-- Which members would benefit? Everyone, API users, chat users, admins? -->
|
||||||
|
|
||||||
|
## How might it work?
|
||||||
|
|
||||||
|
<!-- Any thoughts on the design or implementation. Optional — a rough idea is fine. -->
|
||||||
|
|
||||||
|
## Anything else?
|
||||||
|
|
||||||
|
<!-- Links, examples from other services, constraints, etc. -->
|
||||||
@@ -0,0 +1,34 @@
|
|||||||
|
---
|
||||||
|
name: "Support request"
|
||||||
|
about: "You're stuck, something isn't working, or you need help."
|
||||||
|
title: ""
|
||||||
|
labels: "support"
|
||||||
|
assignees: ""
|
||||||
|
---
|
||||||
|
|
||||||
|
## What do you need help with?
|
||||||
|
|
||||||
|
<!-- A clear description of the problem or question. -->
|
||||||
|
|
||||||
|
## What were you trying to do?
|
||||||
|
|
||||||
|
<!-- The goal you had in mind, so we understand context. -->
|
||||||
|
|
||||||
|
## What happened instead?
|
||||||
|
|
||||||
|
<!-- The actual behavior or error. Include error messages verbatim if you have them. -->
|
||||||
|
|
||||||
|
## What have you already tried?
|
||||||
|
|
||||||
|
<!-- Steps you've taken, docs you've read, etc., so we don't repeat them. -->
|
||||||
|
|
||||||
|
## Environment
|
||||||
|
|
||||||
|
- **Where:** chat / API / dashboard / other
|
||||||
|
- **When:** date and time (your timezone)
|
||||||
|
- **Model:** which model, if relevant
|
||||||
|
|
||||||
|
<!--
|
||||||
|
Please don't include API keys, passwords, or other secrets in this issue.
|
||||||
|
If something is sensitive, email info@inference.coop instead.
|
||||||
|
-->
|
||||||
@@ -0,0 +1,36 @@
|
|||||||
|
# Support & Feature Requests
|
||||||
|
|
||||||
|
Help and ideas for the Inference Cooperative — in one place.
|
||||||
|
|
||||||
|
This is where members open an issue when they need help, hit a bug, or want to
|
||||||
|
propose a feature. We read every issue; an admin (or, soon, a support tool)
|
||||||
|
will triage it.
|
||||||
|
|
||||||
|
## Before you post
|
||||||
|
|
||||||
|
- **Need a quick answer?** Try the [docs](https://git.inference.coop/co-op/docs)
|
||||||
|
first — onboarding, API access, and the model list live there.
|
||||||
|
- **It's a governance question** (pricing, priorities, direction)? Take it to the
|
||||||
|
[Loomio forum](https://forum.inference.coop), not here.
|
||||||
|
- **Something private?** Don't post account details or API keys in an issue.
|
||||||
|
Email [info@inference.coop](mailto:info@inference.coop) instead.
|
||||||
|
|
||||||
|
## How to open an issue
|
||||||
|
|
||||||
|
Click **New Issue** and pick the template that fits:
|
||||||
|
|
||||||
|
- **Support** — something's broken, or you're stuck and need help.
|
||||||
|
- **Feature request** — an idea for a new capability or improvement.
|
||||||
|
- **Bug report** — a defect or unexpected behavior (no template for this yet;
|
||||||
|
describe what happened, what you expected, and how to reproduce it).
|
||||||
|
|
||||||
|
## What happens next
|
||||||
|
|
||||||
|
1. An admin labels and triages the issue.
|
||||||
|
2. For bugs/features, we may move the work to the relevant repo (`code/*`) and
|
||||||
|
link back here.
|
||||||
|
3. You'll get updates on the issue as we go.
|
||||||
|
|
||||||
|
Everything here is public and open to all members — see the
|
||||||
|
[Infrastructure](https://git.inference.coop/co-op/docs/src/branch/main/infrastructure.md)
|
||||||
|
doc for how the Git and membership tie together.
|
||||||
Reference in new issue
Block a user