Agent coordination: ownership, claims and heads-ups (Linux ↔ Mac)
Mantenedores costumam responder em até 1 dia
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 5/5
- Tempo estimado
- Mais de uma semana
- Facilidade para iniciantes
- 8/100
- Tipo de issue
- Funcionalidade
- Clareza
- Precisa de esclarecimento
- Status de atividade
- Ativa
- Stack de tecnologia
- flutter, rust
- Domínio
- developer-experience
Direção de pesquisa
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.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
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.
- Linguagem predominante
- Rust
- Estrelas
- 3
- Forks
- 1
- Merge médio
- 9h 51min
- PRs com merge (30d)
- 310
Preparar o ambiente
- Sem Dockerfile nem arquivo Docker Compose
- Tem um modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de codeatlasdev/atlas
-
type: bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 75/100
codeatlasdev/atlas#597 ·
Mantenedores costumam responder em até 1 dia
-
area: ci os: linux type: bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
codeatlasdev/atlas#496 ·
Mantenedores costumam responder em até 1 dia
-
area: ci type: bug
Dificuldade 3/5 1-2 dias Facilidade para iniciantes 68/100
codeatlasdev/atlas#596 ·
Mantenedores costumam responder em até 1 dia
-
os: linux type: bug
Dificuldade 3/5 1-2 dias Facilidade para iniciantes 68/100
codeatlasdev/atlas#591 ·
Mantenedores costumam responder em até 1 dia
-
flaky: Windows scripts job hits test timeouts (check-dco, i18n runner/translate, check-changed)Abertaarea: ci os: windows type: bug
Dificuldade 3/5 1-2 dias Facilidade para iniciantes 56/100
codeatlasdev/atlas#550 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
Todas as issues de codeatlasdev/atlas
Issues semelhantes
-
marketing
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 76/100
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 74/100
kinqsradio/orbyn-engineering#729 ·
-
Plans page scenario races Shift+Tab against the plan list being drawn again in Firefox and WebKitAbertabug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 83/100
nledford/Ladderback#1091 ·
Mantenedores costumam responder em até 1 dia
-
bug fix packaging ui user-sprint
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
Vondor/KassenSturz#1197 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 82/100
Mantenedores costumam responder em até 1 dia