From e056df42471eac80641f917a749109dedb352f4b Mon Sep 17 00:00:00 2001
From: Hiroshi Shinaoka <h.shinaoka@gmail.com>
Date: Thu, 29 Oct 2026 19:30:18 +0900
Subject: [PATCH] readme: say where the fork's questions and reports go

A short Community section under the fork description, the same shape tenferro-rs uses: questions and
discussion in the tensor4all Matrix space (`#tensor4all:matrix.org`), bug reports and feature requests
in the GitHub issues. The upstream zulip stays as the upstream community, and the section says plainly
that the fork's own channel is Matrix.
---
 README.md | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/README.md b/README.md
index a9087983..f7c9dc6e 100644
--- a/README.md
+++ b/README.md
@@ -20,6 +20,15 @@
 > also reproduce on the published upstream crates are written up in
 > [`upstream-reports/`](upstream-reports/). Published versions follow semver.
 
+# Community
+
+Questions and discussion about this fork go to the tensor4all Matrix space:
+[#tensor4all:matrix.org](https://matrix.to/#/#tensor4all:matrix.org). Bug reports and feature
+requests go to the [GitHub issues](https://github.com/tensor4all/faer/issues).
+
+The upstream community is the [zulip server](https://faer.zulipchat.com), for questions about upstream
+faer itself. The fork's own channel is the Matrix space above.
+
 <p align="center">
   <img src="https://faer.veganb.tw/faer-logo-color.png" alt="faer logo"/ width="25%">
 </p>