/sunset omits the deletion date, the refund offer and the MCP change

Cerrado
  • ¿Algo no está bien?
#2,009 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
55/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
react, typescript
Área
content, frontend

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement frontend help wanted hosted UI

The gap

docs/architecture/sunset.md lists this under Known gaps:

/sunset has 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

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.md in 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.

Lenguaje dominante
Python
Estrellas
16.3k
Forks
1.6k
Merge medio
14 h 22 min
PR fusionados (30 d)
175

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de MODSetter/SurfSense

Todos los issues de MODSetter/SurfSense

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.