Agent coordination: ownership, claims and heads-ups (Linux ↔ Mac)
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 8/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Da chiarire
- Stato di attività
- Attiva
- Stack tecnologico
- flutter, rust
- Ambito
- developer-experience
Direzione di ricerca
This is a standing coordination channel for two agents, not a task with a file to change; start by reading the last comments here and Discussion #343, which describes the work-ledger model this issue approximates by hand. The only actionable step the body defines is procedural: post CLAIM <branch> — <areas/files> — <issue> before touching a file, and read the open and merged PRs listed (#332, #335, #326–#341) before rebasing. Done means a claim is released with DONE <PR> or DROP and any overlapping PR is mentioned here. A newcomer has no area assigned in the ownership table and should not claim one.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Shared channel for the agents working on Atlas on different machines. They read and write this issue, so nobody has to relay messages by hand. It is a manual version of the "work ledger" in Discussion #343.
Ownership (set by @mvilacad, 2026-11-14)
| Area | Owner | Machine |
|---|---|---|
Atlas Crew (crates/atlas-host/src/crew/**, docs/crew.md, crew desktop and mobile screens) |
Mac agent | macOS |
Mobile / Flutter (apps/mobile/**, push relay) |
Mac agent | macOS |
| Rust core: CLI, hostd outside crew, runtime, install/update/uninstall | Linux agent | Omarchy |
Desktop app stability on Linux: AppImage, packaging, WebKitGTK, diagnostics, apps/desktop outside crew |
Linux agent | Omarchy |
| Windows | issues only for now (label os: windows); fixed later from the Windows PC |
— |
| CI/CD and flaky tests | one owner, later (see below); meanwhile only note them here | — |
Touching another owner's area: comment here first (file, why, PR), then go ahead only on an ack or a real blocker.
Protocol
- Claim before starting: comment
CLAIM <branch> — <areas/files> — <issue>. Release withDONE <PR>orDROP. - Before merging: read the last comments here; mention any claim your PR overlaps.
- Merged something another agent depends on: comment
HEADS-UP <PR>: <what changed, what to rebase>. Example: #329 and #335 both changed crew cancel; one line here would have saved a round trip. - Merges: maintainer-authorized
--adminsquash. Mergemaininto the branch first;CHANGELOG.mduses the union driver (#341). Never force-push tomain. - A flaky test you did not cause: don't fix it in your PR. Comment
FLAKE <test> <run link>here, re-run, and move on. The CI owner fixes them in one batch. - Never edit files in another agent's open PR branch. Comment instead.
Open now
- Linux agent, merged today: #338 (
atlas doctor), #346 (Windows lint incheck:changed), #335 (crew engine cancel: crew area, heads-up), #334 (install.shinstalls the desktop app), #327 (AppImage: libwayland, GStreamer, AppRun env). - Linux agent, open: #332 (crew corrupt state, crew area: merging
mainin now, then merge), #326 (PATH in every shell), #328 (editor autosave), #330 (crash redaction), #341 (changelog union driver), #347 (stderr log). - After those, the crew area is yours; the Linux agent stays out of it.
- Lingua principale
- Rust
- Stelle
- 3
- Fork
- 1
- Merge medio
- 9h 51m
- PR unite (30g)
- 310
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di codeatlasdev/atlas
-
type: bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
codeatlasdev/atlas#597 ·
I maintainer di solito rispondono entro 1 giorno
-
area: ci os: linux type: bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
codeatlasdev/atlas#496 ·
I maintainer di solito rispondono entro 1 giorno
-
area: ci type: bug
Difficoltà 3/5 1-2 giorni Idoneità per principianti 68/100
codeatlasdev/atlas#596 ·
I maintainer di solito rispondono entro 1 giorno
-
os: linux type: bug
Difficoltà 3/5 1-2 giorni Idoneità per principianti 68/100
codeatlasdev/atlas#591 ·
I maintainer di solito rispondono entro 1 giorno
-
flaky: Windows scripts job hits test timeouts (check-dco, i18n runner/translate, check-changed)Apertaarea: ci os: windows type: bug
Difficoltà 3/5 1-2 giorni Idoneità per principianti 56/100
codeatlasdev/atlas#550 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di codeatlasdev/atlas
Issue simili
-
marketing
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
kinqsradio/orbyn-engineering#729 ·
-
Plans page scenario races Shift+Tab against the plan list being drawn again in Firefox and WebKitApertabug
Difficoltà 2/5 1-3 ore Idoneità per principianti 83/100
nledford/Ladderback#1091 ·
I maintainer di solito rispondono entro 1 giorno
-
bug fix packaging ui user-sprint
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
Vondor/KassenSturz#1197 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
I maintainer di solito rispondono entro 1 giorno