The bug form now asks what JP's Discord post asks: how often it happens, whether there's a workaround, what hardware you're on, and which companion device — with the note that "a Xiao" doesn't narrow anything down. Three things his post didn't cover got added: the MeshTerm version, whether it still happens under `--mock` (which splits an app bug from a radio bug before anyone spends an evening on it), and whether you're on the regular or PicoCalc look, since those draw differently enough that a bug in one often doesn't exist in the other. The README gains the part that was missing: what to expect from a maintainer doing this on evenings and weekends. Issues welcome, ask before opening a pull request, no promised timelines, and a nudge on a quiet issue is fine. Report on GitHub or on Discord, whichever you have — the real ones get moved across either way, and being told beats filing it tidily. Install is rewritten for someone who wants to run MeshTerm rather than work on it. It said `pip install -e ".[dev]"`, which is a contributor's command and puts pytest and ruff on the machine of somebody who just wants to talk to a radio. Now it's one pip line, a pipx alternative, `--mock` for people without a radio yet, and an honest "coming" list for installers and PyPI. Badges now include CI, the licence and Discord, so they say something checkable rather than only decorating. The two survey documents get a line at the top saying they're a snapshot of a date, not a to-do list. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
31 lines
1.0 KiB
YAML
31 lines
1.0 KiB
YAML
name: Feature request
|
|
description: Suggest a feature or an improvement
|
|
labels: [enhancement]
|
|
body:
|
|
- type: markdown
|
|
attributes:
|
|
value: |
|
|
MeshTerm is one person's spare time, so the honest answer to a good idea is often
|
|
"yes, eventually". Saying what you are actually trying to do — rather than the
|
|
feature you have in mind — often finds something that already works.
|
|
|
|
- type: textarea
|
|
id: problem
|
|
attributes:
|
|
label: What are you trying to do
|
|
description: The situation you are in, not the feature. What are you trying to find out about your mesh?
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: idea
|
|
attributes:
|
|
label: What you had in mind
|
|
description: If you have a shape in mind — a screen, a key, a subcommand — describe it.
|
|
|
|
- type: textarea
|
|
id: today
|
|
attributes:
|
|
label: What you do today instead
|
|
description: The workaround, if there is one. This says more about how much the feature is worth than anything else.
|