Hacktoberfest 2026：維護者為十月標記出來的 issue，仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Integrate persistent collaborative EtherCalc workbooks with experiment results and IPFS versions

未關閉
  • 哪裡不對？
#103 0 則留言 0 個 reaction 已指派 1 人 在 GitHub 檢視

維護者通常 1 天內回覆

@Winter-Soren 已經在處理了。

開始於 2026年10月28日。

評估

這個 Issue 還沒有評估資料。

描述

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.

主要語言
Python
星號
2
分支
4
平均合併
8 小時 37 分鐘
30 天內合併 PR
29

環境準備

  • 提供 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 沒有貢獻指南

從這裡開始

  1. 先讀完整個 Issue，再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫，在一個分支上完成修改。
  4. 送出 Pull Request，並在描述裡引用這個 Issue 編號。

QMeshPy/distributed-quantum 的其他 Issue

查看 QMeshPy/distributed-quantum 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。