[#23] List primary communication channels

[interact]: https://www.bestpractices.dev/en/criteria/0?details=true&rationale=true#0.interact

(close #23)

Signed-off-by: Vitaliy Potyarkin <v.potyarkin@yadro.com>

config.toml

@@ -73,3 +73,8 @@ weight = 2
 name = "About"
 url = "about/"
 weight = 3
+
+[[Languages.en.menu.main]]
+name = "Contact"
+url = "about/contact/"
+weight = 4

content/about/contact.en.md

@@ -0,0 +1,32 @@
+---
+title: Contact us
+date: 2025-02-18
+---
+
+## Bug reports
+
+Bugs should be reported to the relevant FrostFS component repository,
+available at [git.frostfs.info](https://git.frostfs.info/TrueCloudLab).
+
+If you are unsure which repo your bug belongs to you may contact us privately
+at [info@frostfs.info](mailto:info@frostfs.info) or ask in [chat](#chat).  You
+may also report the bug to
+[frostfs-node](https://git.frostfs.info/TrueCloudLab/frostfs-node) and let the
+maintainers handle it from there.
+
+## Enhancement proposals
+
+Significant technical and process changes should be submitted as
+FrostFS Enhancement Proposals, see [FEP-1]({{< ref "proposals/proc/fep-0001" >}}).
+
+## Security vulnerabilities
+
+Security vulnerabilities should be reported through private mailing list
+[security@frostfs.info](mailto:security@frostfs.info).
+Please refer to the [security policy page]({{< relref "security.md" >}}) for more information.
+
+## Chat
+
+For real-time chat with FrostFS developers and other community members please
+join our channels in Matrix:
+[#frostfs:matrix.org](https://matrix.to/#/#frostfs:matrix.org)

content/about/security.md

@@ -0,0 +1,30 @@
+---
+title: Security policy
+date: 2025-02-18
+---
+
+
+## How To Report a Vulnerability
+
+If you think you have found a vulnerability in any FrostFS component, please
+report it to us through coordinated disclosure.
+
+Contact TrueCloudLab security team at
+**[security@frostfs.info](mailto:security@frostfs.info)**
+
+Please do not report security vulnerabilities through public issues,
+discussions, or change requests.
+
+Please include as much information as you can to help us better understand and resolve the issue:
+
+- The type of issue (e.g., buffer overflow, or cross-site scripting)
+- Affected components and their versions
+- Impact of the issue, including how an attacker might exploit the issue
+- Step-by-step instructions to reproduce the issue
+- The location of the affected source code (tag/branch/commit or direct URL)
+- Full paths of source file(s) related to the manifestation of the issue
+- Any special configuration required to reproduce the issue
+- Any log files that are related to this issue (if possible)
+- Proof-of-concept or exploit code (if possible)
+
+This information will help us triage your report more quickly.