chore(linux): establecer baseline y contrato del port nativo
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 22/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- linux, nodejs, rust, typescript
- Domain
- desktop-dev
Research direction
Start by reading the entry files named in the issue: src-tauri/tauri.conf.json, src-tauri/src/lib.rs, src-tauri/src/login.rs, src-tauri/src/secrets.rs, src-tauri/src/providers/, src/lib/dock.ts and src/Settings.tsx, plus README and CONTRIBUTING. Then run npm test, npm run typecheck, npm run build, cargo test in src-tauri and npm run app:dev on a real Linux machine, recording exit codes and failures. Done means a reproducible baseline and an accepted support matrix, not a claim of Linux support.
Written by the indexing model from the issue text.
Description
Objetivo y motivo
Determinar un objetivo Linux nativo reproducible y verificable antes de prometer soporte. Esta unidad abre el milestone Linux portability, no desarrolla por sí sola todo el port.
Alcance
- Inventariar dependencias Linux de Tauri/WebKitGTK, Rust/Node, bandeja, ventanas, compositor, Secret Service, CLI y proveedores; registrar límites y regresiones Windows.
- Medir en una máquina Linux real instalación,
npm test,npm run typecheck,npm run build,cargo testensrc-tauri,npm run app:devy arranque/primer uso, con comandos, códigos de salida y fallos preexistentes. - Proponer y obtener aceptación de distribución y versión mínima, arquitectura, sesión gráfica y matriz X11/Wayland; identificar formato de paquete local para L3.
- Excluye implementar integraciones completas, distribución pública, firma, CI/release y afirmar soporte de distros/compositores no comprobados.
Dependencias
Ninguna técnica; respetar roadmap #45. #89 es un preflight Windows independiente; no ampliar su alcance implícitamente.
Criterios de aceptación
- Baseline reproducible en Linux real con entorno, comandos, exit codes, bloqueos y evidencia de arranque; compilación no equivale a experiencia funcional.
- Matriz de soporte inicial y política de X11/Wayland, bandeja, secretos y formato local explícitas y aceptadas antes de L1/L2/L3.
- Riesgos priorizados y entradas del código contrastadas con comportamiento real; no afirmar equivalencia WSL/Linux nativo.
- Plan de pruebas y regresión Windows, con límites no verificados declarados.
Orientación
Entradas: src-tauri/tauri.conf.json, src-tauri/src/lib.rs, src-tauri/src/login.rs, src-tauri/src/secrets.rs, src-tauri/src/providers/, src/lib/dock.ts, src/Settings.tsx, README y CONTRIBUTING. No incluir ni publicar credenciales de la máquina de prueba.
Comprobaciones y ODD cercano
| Fase | Resultado | Dependencias | Validación y salida |
|---|---|---|---|
| Observar L0a | Inventario y baseline real | Ninguna | Entorno y comandos documentados con exit codes; fallos distinguidos |
| Decidir L0b | Matriz y contrato Linux, política X11/Wayland y paquete local | L0a | Decisiones contrastadas y aceptadas, incertidumbres explícitas |
| Desarrollar L0c | Solo guardas o documentación mínima que exija el baseline aprobado | L0b | Tests primero cuando haya comportamiento determinista; sin port prematuro |
| Verificar L0d | Evidencia replicable y desglose de L1–L3 | L0b/L0c | Gates y riesgos publicados, sin declarar plataforma soportada |
Coordinación y entrega
Estado: planificada, no lista para implementar hasta acordar matriz y contrato. Sin assignee inicial; revalidar issue, comentarios y PR al iniciar explícitamente. Mantener el primer objetivo nuevo recomendado #66 y compromisos Windows; WSL #90–#93 y macOS #69 son trabajos distintos. Tests y docs con la unidad; la planificación no autoriza implementación, PR, merge ni release.
- Dominant language
- TypeScript
- Stars
- 10
- Forks
- 2
- Avg merge
- 16m
- Merged PRs (30d)
- 51
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 egdev6/quorb
-
status:approved type:bug
Difficulty 1/5 Under an hour Newbie friendliness 70/100
egdev6/quorb#109 · 1 comment ·
Maintainers usually reply within 1 day
-
odd type:feature
Difficulty 5/5 Over a week Newbie friendliness 15/100
Maintainers usually reply within 1 day
-
odd type:feature
Difficulty 4/5 3-5 days Newbie friendliness 15/100
Maintainers usually reply within 1 day
-
odd type:feature
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
homarr-labs/homarr#7191 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
AvaProtocol/ava-sdk-js#276 ·
Maintainers usually reply within 1 day
-
useFragment does not require `variables` when the fragment's variables type has required fieldsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
apollographql/apollo-client#13493 ·
Maintainers usually reply within 1 day