/sunset omits the deletion date, the refund offer and the MCP change
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 3/5
- 見積もり時間
- 1〜2日
- 初心者へのやさしさ
- 55/100
- issue の種類
- ドキュメント
- 明瞭さ
- 明確に書かれている
- 活発さ
- 活発
- 技術スタック
- react, typescript
調査の方向性
Read docs/architecture/sunset.md and journey 2 in plans/community-local/portal/02-pages.md, then inspect the STEPS array and closing section in surfsense_web/app/(home)/sunset/page.tsx. Ask a maintainer for the refund and MCP details before writing those parts; use the existing unit tests as the verification starting point. Done means the page clearly states the deletion date and maintainer-approved details, and the Known gaps line is removed.
索引モデルが issue の本文から書いたものです。
説明
The gap
docs/architecture/sunset.md lists this under Known gaps:
/sunsethas the export button, download links and import steps, but not the deletion date (18 Oct 2026), the refund-or-discount offer or the change for MCP users, which the launch plan put on it.
Why it matters
The missing deletion date is the serious one. The purge runbook treats 18 Oct 2026 as a promise with a deadline because users "were given it in the launch email, the T+23 reminder and on /sunset" — and the page does not say it. Anyone who arrives from a bookmark, from the app's redirect, or from a legacy desktop client loading this page in its own window gets five calm steps about moving to the desktop app and no indication that their data disappears on a date.
The other two are commitments made and not kept in the one place everyone is being sent. PAT-holding MCP clients keep working through the tail and then stop, and nothing on the page tells them so.
Where
surfsense_web/app/%28home%29/sunset/page.tsx— theSTEPSarray and the closing section below it. Steps areGuideStepobjects rendered bycomponents/site/guide-steps.tsx; a step can carry acontrol, anactionor ashot, so most of what you need already exists.surfsense_web/app/%28home%29/sunset/sunset-export.tsx— the paragraph under the export button, which states plainly what does not travel. That is the tone to match: specific, unhedged, no marketing.plans/community-local/portal/02-pages.md— journey 2 is the source of the five things this page was meant to carry. Items 4 and 5 are the ones missing.- Use the existing
ss-home-*primitives andHomeButtonrather than the product's own components. The page renders inside the site design, and mixing the two is visible.
What done looks like
- A reader learns the deletion date without looking for it, and learns it early enough to act on it rather than as a footnote.
- MCP users are told what changes for them and when.
- The refund-or-discount offer appears, or a maintainer records in this issue that it is no longer being made — in which case the doc line changes rather than the page.
- The date is a real date in the copy, not a countdown or anything that needs to stay correct on its own after the day passes.
- Ask before you write items 4 and 5. The refund terms and the MCP cutover detail are commercial facts you cannot infer from the repo. Comment here and wait for a maintainer to supply them; the deletion date is in the architecture doc and needs nobody's permission.
- Delete the Known gaps line from
docs/architecture/sunset.mdin the same PR.
What not to change
Leave the export step first and leave SunsetExport where it is. The comment in page.tsx explains that the button sits inside the step that tells you to export, so the reader meets it in the order they act — and a date-and-refund banner above the fold is exactly the change that would push it down.
How to verify
surfsense_web/tests/unit/sunset-export.test.ts covers this page's exported helpers, and tests/unit/sunset-redirect.test.ts proves /sunset stays publicly reachable. Copy alone needs no test; anything you extract as a function does, written failing first.
cd surfsense_web
pnpm test:unit
Before you start
Read CONTRIBUTING.md, the sunset doc and the page plan linked above. React and UI work in surfsense_web follows the frontend-workflow skill described in AGENTS.md. This page also loads inside the legacy desktop client's own window under contract 4, which requires it to work there with no Electron-specific assumptions — adding copy does not touch that contract, but do not add anything that needs a browser the legacy client is not. This is time-critical: the date it should be announcing is 18 Oct 2026. Open your PR against dev, not main. Comment here to claim this.
- 主要言語
- Python
- スター
- 16.3k
- フォーク
- 1.6k
- 平均マージ
- 13時間 35分
- マージ済み PR（30日）
- 267
環境構築
このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
MODSetter/SurfSense のほかの issue
-
Security Scan: stop flagging pinned hashes and test fixtures on release PRs対応中かも @karthikeya1220 が 2 日前に担当しました。 オープンcode quality security
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
MODSetter/SurfSense#2225 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
Check Apple notarization credentials on dry runs and weekly対応中かも @Cedric921 が 2 日前に担当しました。 オープンdesktop
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
MODSetter/SurfSense#2224 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
Release workflow: keep the macOS certificate off the Windows dry-run build対応中かも @Cedric921 が 2 日前に担当しました。 オープンdesktop security
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
MODSetter/SurfSense#2223 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
Write the ADR for chat modes対応中かも @Cedric921 が 2 日前に担当しました。 オープンarchitecture desktop documentation
難易度 2/5 1〜3時間 初心者へのやさしさ 75/100
MODSetter/SurfSense#2220 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 73/100
メンテナーはふだん 1 日以内に返信
MODSetter/SurfSense の issue をすべて見る
似ている issue
-
bot-triaged module: LrScheduler module: optimizer triaged
難易度 2/5 1〜3時間 初心者へのやさしさ 70/100
メンテナーはふだん 1 日以内に返信
-
documentation glm5 llm-model
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
vllm-project/vllm-ascend#19062 ·
メンテナーはふだん 1 日以内に返信
-
author-page correction
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
acl-org/acl-anthology#10496 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
Issue Type: Bug Report
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
celery/celery#10875 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
enhancement good first issue
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
SasanLabs/VulnerableApp#836 ·
メンテナーはふだん 1 日以内に返信