Rozdzielenie Engine Controller i Mission Controller
Open
@Antokolski is already working on this.
Since Sep 14, 2026.
Assessment
This issue has not been assessed yet.
Description
Opis:
Analiza plusów/minusów rozdziału EC i MC, propozycja interfejsu między nimi (API, transport, odpowiedzialności), estymata czasu.
DOD:
- Diagram odpowiedzialności EC vs MC
- Spec interfejsu (messages, transport: IPC/socket/shared mem)
- Tabela za/przeciw (latency, fault isolation, complexity)
- Plan migracji krok po kroku
- Estymata czasu (h/dni)
- Dominant language
- TeX
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No 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 Simba-Avionic/Rurku-docs
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Simba-Avionic/Rurku-docs#39 ·
-
Simba-Avionic/Rurku-docs#38 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Simba-Avionic/Rurku-docs#37 ·
-
Zalety użycia serv na RS485May be free again @mateuszwicinski claimed this 30 days ago, and no pull request is open. Open
Simba-Avionic/Rurku-docs#36 · 1 assignee ·
-
Prototype of PrimerMay be free again @WiktorLAN claimed this 50 days ago, and no pull request is open. Open
Simba-Avionic/Rurku-docs#35 · 1 assignee ·