[Epic] MeshCore Phase 0 — Bot refactor, MeshCore exploration, ADRs
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 8/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- docker, python
- Domain
- backend, documentation
Research direction
This is an umbrella epic, not a single task: it links seven child issues across meshflow-bot, meshflow-ui and meshflow-api. The payload names RadioInterface, src/meshtastic/ and MESHCORE_PACKET_FIELDS.md as targets, so start by reading the bot's radio abstraction and the planned capture notes. Work is done when the child issues close and the ADRs are backed by captured packet data.
Written by the indexing model from the issue text.
Description
Goal
Prepare meshflow-bot for MeshCore: refactor spaghetti code into a protocol-agnostic core + Meshtastic-specific package, prove MeshCore connectivity with real radios, capture packets for several days, then lock schema decisions in ADRs backed by real captured data (not docs-only).
Scope
See MeshCore adoption plan (Phase 0): repo rename/tidy, bot refactor (RadioInterface, src/meshtastic/), MeshCore connect+dump (no API upload), capture campaign + MESHCORE_PACKET_FIELDS.md, ADRs for identity/channel/broadcast/dedup.
Child issues
- pskillen/meshflow-api#270 — Repo rename tidy (meshflow-bot + meshflow-ui)
- pskillen/meshflow-bot#84 — Docker: publish new tag + legacy tag (migration window)
- pskillen/meshflow-bot#81 — Docker: remove legacy tag push after migration
- pskillen/meshflow-bot#80 — Bot refactor: protocol-agnostic core + Meshtastic package
- pskillen/meshflow-bot#82 — MeshCore connect + packet dump (no API upload)
- pskillen/meshflow-api#275 — Capture campaign + packet field notes
- pskillen/meshflow-api#276 — ADRs (identity, channel, broadcast, dedup)
Repos: meshflow-bot, meshflow-ui, meshflow-api (docs only for capture output).
Milestone: MeshCore Support
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 5
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pskillen/meshflow-api
-
enhancement meshtastic-2.8
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
pskillen/meshflow-api#459 ·
-
enhancement meshtastic-2.8
Difficulty 3/5 1-2 days Newbie friendliness 35/100
pskillen/meshflow-api#465 ·
-
enhancement meshtastic-2.8
Difficulty 4/5 3-5 days Newbie friendliness 22/100
pskillen/meshflow-api#464 ·
-
enhancement meshtastic-2.8
Difficulty 4/5 3-5 days Newbie friendliness 35/100
pskillen/meshflow-api#463 ·
-
enhancement meshtastic-2.8
Difficulty 3/5 1-2 days Newbie friendliness 45/100
pskillen/meshflow-api#462 ·
All issues in pskillen/meshflow-api
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
elviskahoro/sdk-python-attio#144 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
RenyiELBO raises TypeError when model has no sample sitesPossibly taken @alibb007 claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
[Bug]: Four evaluation scripts unpack init_memmachine_params's five return values into three namesOpen
Difficulty 1/5 Under an hour Newbie friendliness 88/100
MemMachine/MemMachine#1911 ·
Maintainers usually reply within 3 days