Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Integrate persistent collaborative EtherCalc workbooks with experiment results and IPFS versions

Aberta
  • Algo errado?
#103 0 comentários 0 reações 1 responsável Ver no GitHub

Mantenedores costumam responder em até 1 dia

@Winter-Soren já está trabalhando nisso.

Desde 28/10/2026.

Avaliação

Esta issue ainda não foi avaliada.

Descrição

Outcome

Embed current audreyt/EtherCalc in QMesh so completed pharma, finance, and circuit runs can be explored together in persistent collaborative workbooks, with deliberate IPFS version backups. Demo target: October 31, 2026 (Asia/Kolkata), November 1 buffer.

Accepted design and scope

  • Pin and test current TypeScript/Hono/workerd upstream; use bundled SocialCalc. Deploy a separate persistent service, embedded inside the existing application.
  • One workbook feature and domain adapters. Idempotent creation keyed to immutable run identity/version; reopening never overwrites collaborator work.
  • Preserve original scientific JSON and artifact references alongside useful tables, units, method, configuration and provenance. Source snapshots remain separate from editable comparison/notes sheets.
  • Authenticate workbook access using existing app identity, with owner/editor/viewer permissions, invitations, stable links and shared-workbook discovery. Protect UI, HTTP, export and WebSocket paths; links alone do not authorize access.
  • Explicitly add an owned experiment to a shared workbook with data-sharing consent. No implicit sharing of future runs.
  • Agent reads bounded ranges and explains results; any supported edits use explicit approval. Opening/recalculating sheets must not submit paid jobs.
  • Persist live rooms on mounted durable storage and workbook/access/run/version metadata in the app database.
  • Explicit Save version to IPFS with deliberate public-data consent; upload native sheet saves, original JSON and manifest, retain actual returned CID, verify retrieval and restore coherently into a NEW workbook. Reuse persistent Kubo; credentials stay server-side.
  • Document decisions, setup, collaboration, persistence, demo and verification in QMeshPy/documentations. One issue covers both repositories.

Acceptance criteria

  • Completed pharma, finance and circuit results open correctly populated embedded spreadsheets; repeated export reopens the same workbook.
  • Two independent authenticated browser sessions collaborate in the same room; viewer mutations and unauthorized UI/API/export/WebSocket requests fail.
  • Collaborator can deliberately add their owned experiment without mutating either source run.
  • Workbook edits survive browser reload and service restart.
  • Bounded agent context works without automatic paid job execution.
  • Snapshot records actual provider CID, reports failure accurately, is retrievable without browser-local data, and restores all sheets/formulas/formatting/source metadata into a new workbook.
  • Mapping, idempotency, permissions, invitations, proxy boundaries, snapshot and failure-recovery tests pass; project checks and real Chrome demo evidence are recorded honestly.
  • Separate documentation branch is committed and pushed, with reproducible demo steps and precise remaining limitations.

Explicit non-goals

Browser-to-browser libp2p replication/offline CRDT merge, duplicate SocialCalc integration, automatic initial/public IPFS publication, per-keystroke IPFS synchronization, unrelated wallet work, merging main, contacting demo recipients or publishing a video.

Linguagem predominante
Python
Estrelas
2
Forks
4
Merge médio
8h 37min
PRs com merge (30d)
29

Preparar o ambiente

  • Inclui um Dockerfile ou arquivo Docker Compose
  • Sem modelo de pull request
  • Sem guia de contribuição

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de QMeshPy/distributed-quantum

Todas as issues de QMeshPy/distributed-quantum

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.