Agent coordination: ownership, claims and heads-ups (Linux ↔ Mac)
Maintainer antworten meist innerhalb von 1 Tag
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Anfängerfreundlichkeit
- 8/100
- Issue-Typ
- Feature
- Klarheit
- Muss geklärt werden
- Aktivitätsstatus
- Aktiv
- Tech-Stack
- flutter, rust
- Bereich
- developer-experience
Rechercherichtung
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.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
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.
- Vorherrschende Sprache
- Rust
- Sterne
- 3
- Forks
- 1
- Ø Merge
- 9 Std. 51 Min.
- Gemergte PRs (30 T.)
- 310
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Hat eine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus codeatlasdev/atlas
-
type: bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 75/100
codeatlasdev/atlas#597 ·
Maintainer antworten meist innerhalb von 1 Tag
-
area: ci os: linux type: bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
codeatlasdev/atlas#496 ·
Maintainer antworten meist innerhalb von 1 Tag
-
area: ci type: bug
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 68/100
codeatlasdev/atlas#596 ·
Maintainer antworten meist innerhalb von 1 Tag
-
os: linux type: bug
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 68/100
codeatlasdev/atlas#591 ·
Maintainer antworten meist innerhalb von 1 Tag
-
flaky: Windows scripts job hits test timeouts (check-dco, i18n runner/translate, check-changed)Offenarea: ci os: windows type: bug
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 56/100
codeatlasdev/atlas#550 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
Alle Issues in codeatlasdev/atlas
Ähnliche Issues
-
marketing
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 74/100
kinqsradio/orbyn-engineering#729 ·
-
Plans page scenario races Shift+Tab against the plan list being drawn again in Firefox and WebKitOffenbug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 83/100
nledford/Ladderback#1091 ·
Maintainer antworten meist innerhalb von 1 Tag
-
bug fix packaging ui user-sprint
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
Vondor/KassenSturz#1197 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
Maintainer antworten meist innerhalb von 1 Tag