Files
poli0981andClaude Opus 5.5 7bcbcf59dd docs: maintenance mode — policy, triage bot, issue forms, status badge, docs for 2.3.0 (#139)
* docs: maintenance mode — policy, triage bot, issue forms, status badge, docs for 2.3.0

From v2.3.0 the project takes no new features (CONTRIBUTING.md, in Vietnamese and
English). Accepted: scheduled dependency updates; security fixes (High/Critical
advisories, runtime vulnerabilities); major language/runtime/framework upgrades; bug
fixes including UI/UX and accessibility; language fixes.

- .github/workflows/triage.yml + scripts/triage.mjs (unit-tested): an issue or pull
  request whose title or label asks for a feature is labelled enhancement + out-of-scope,
  answered in both languages and closed (issues as "not planned"). The owner's items, bots,
  `maintenance-exception` and anything the owner does are left alone. It runs on
  pull_request_target but checks out only that one script from the default branch, never a
  pull request's code; workflow_dispatch is a dry run.
- Issue forms: blank issues off, questions and ideas to Discussions, security to the
  private policy; a new language-problem form; the bug form no longer claims the site's
  report button fills it (those reports go to a private repository). The pull request
  template asks which of the five kinds of change it is.
- README: a maintenance-mode badge and a Status section; the admin paragraph describes
  auto-publish. SECURITY.md: High/Critical fixes ship out of schedule; the age-check
  answer is local storage only.
- Docs: decisions D21–D24, maintenance policy and cadence (17 §0, QODANA_TOKEN rotation),
  roadmap frozen, CI (Qodana, whole-tree licences, triage, merge rules), architecture
  tree, the Workers Builds deploy command, licence notes without the stale
  license-checker/GSAP lines.
- CHANGELOG [2.3.0]; sonar.projectVersion 2.3.0.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs: link #138 in the 2.3.0 changelog

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs: album labels come from both language entries

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(ci): triage without a checkout, and linear title patterns

SonarCloud and Qodana on #139:
- githubactions:S7631 flags any checkout in a pull_request_target workflow, even of the
  default branch. The workflow now reads scripts/triage.mjs from the default branch through
  the API and imports it from a data: URL — nothing is checked out at all.
- javascript:S8786: `\s+a?\s*` let two quantifiers compete for the same spaces. The title
  is trimmed once and the patterns are written so no two quantifiers overlap.
- Qodana RegExpRedundantEscape: the bot check is `endsWith("[bot]")`, no regex.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-21 08:48:09 +07:00

5.0 KiB

Contributing

Tiếng Việt ở bên dưới. / Vietnamese below.

Maintenance mode

Since v2.3.0 (November 2026) this project is in maintenance mode. The site is complete; it is kept healthy, but no new features are being added. Only these changes are accepted:

  1. Dependency updates on the regular schedule (Dependabot weekly, a combined update about once a month, always after a 3-day cooldown).
  2. Security: a dependency advisory of High or Critical severity, or a serious vulnerability in the runtime itself (Node.js, the Workers runtime), fixed as soon as possible — together with a feature only when the owner judges it truly necessary.
  3. Major language, runtime or framework upgrades: Node.js 26 → 28, TypeScript 7.1 replacing the TypeScript 6 API alias, the next Astro or Svelte major, and the like.
  4. Bugs: anything that does not work as intended, including UI/UX glitches and accessibility barriers (ACCESSIBILITY.md).
  5. Language: spelling mistakes that could mislead, and wording that does not fit the culture or the local voice, in Vietnamese or English.

Not accepted: new features. An issue or pull request asking for one is labelled enhancement + out-of-scope and closed automatically (.github/workflows/triage.yml). If it was closed by mistake, reply on it and the owner will take another look; an exception the owner accepts carries the maintenance-exception label. Ideas are still welcome in Discussions, without any promise.

How to report

  • A problem on the website: the "Báo lỗi / Report a problem" button on the page itself, or the bug report form under Issues.
  • An accessibility barrier: the accessibility form under Issues.
  • A spelling or wording problem: the language form under Issues.
  • A security vulnerability: privately — see SECURITY.md. Never in a public issue.

Pull requests

Welcome for the five kinds of change above. Keep one change per pull request, follow the checks in the pull request template, and run the commands listed in README.md before opening it. CI must be green — build is required, and the SonarCloud and Qodana gates have to pass too. Commits on main are signed.


Chế độ bảo trì

Từ v2.3.0 (tháng 11/2026), dự án ở chế độ bảo trì. Trang web đã hoàn chỉnh; repo vẫn được giữ cho khoẻ mạnh nhưng không thêm tính năng mới. Chỉ nhận những thay đổi sau:

  1. Cập nhật dependency định kỳ (Dependabot hằng tuần, gộp một lần khoảng mỗi tháng, luôn sau 3 ngày "nguội").
  2. Bảo mật: lỗ hổng trong dependency ở mức High hoặc Critical, hoặc lỗ hổng nghiêm trọng của chính runtime (Node.js, Workers runtime) — sửa sớm nhất có thể; kèm tính năng chỉ khi chủ repo đánh giá là thật sự cần thiết.
  3. Nâng cấp lớn ngôn ngữ, runtime, framework: Node.js 26 → 28, TypeScript 7.1 thay alias API TypeScript 6, bản major tiếp theo của Astro hay Svelte…
  4. Lỗi: mọi thứ không chạy đúng ý định, gồm cả lỗi UI/UX và rào cản accessibility (ACCESSIBILITY.md).
  5. Ngôn ngữ: lỗi chính tả có thể gây hiểu nhầm, câu chữ không hợp văn hoá hay giọng địa phương, ở cả tiếng Việt lẫn tiếng Anh.

Không nhận: tính năng mới. Issue hoặc pull request đề xuất tính năng sẽ được gắn nhãn enhancement + out-of-scope và tự động đóng (.github/workflows/triage.yml). Nếu bị đóng nhầm, hãy trả lời ngay trong đó — chủ repo sẽ xem lại; ngoại lệ được chấp nhận mang nhãn maintenance-exception. Ý tưởng vẫn có thể trao đổi trong Discussions, không cam kết sẽ làm.

Báo lỗi ở đâu

  • Lỗi trên trang web: nút "Báo lỗi" ngay trên trang, hoặc form báo lỗi trong Issues.
  • Rào cản accessibility: form accessibility trong Issues.
  • Lỗi chính tả, câu chữ: form ngôn ngữ trong Issues.
  • Lỗ hổng bảo mật: báo riêng — xem SECURITY.md. Không mở issue công khai.

Pull request

Hoan nghênh cho năm loại thay đổi ở trên. Mỗi pull request một thay đổi, làm theo các mục kiểm tra trong mẫu pull request, chạy các lệnh trong README.md trước khi mở. CI phải xanh — build là bắt buộc, cổng SonarCloud và Qodana cũng phải qua. Commit trên main có chữ ký.