mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-06 02:54:26 +00:00
kevinveenbirkenbachandClaude Opus 4.7
16bdbf03d7
Three classes of drift cleaned up across 85 .md files:
- Em-dashes: replaced ` — ` with the contextually correct separator
(colon for `term: explanation`, period to split clauses across
sentences/source lines, parentheses for asides, semicolon for
tight-linked continuations). Two intentional exceptions remain
in `docs/contributing/documentation.md` (the rule literal) and
inside a fenced ```sh block in `docs/contributing/actions/debugging/ci.md`.
- SPOT self-labels: rewrote "This is the SPOT for X" to describe
the subject directly ("This directory holds X" / "This file
describes X"). Cross-references to other artefacts' canonical
role remain unchanged.
- Heading-emoji position: moved leading-emoji headings (`# 🧩 Title`)
to trailing position (`# Title 🧩`) per the headline rule that
emojis MUST come after the title text.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
71 lines
3.0 KiB
Markdown
71 lines
3.0 KiB
Markdown
# Communication 💬
|
|
|
|
This document defines the communication conventions for all contributors and community members.
|
|
|
|
## Channels 📡
|
|
|
|
Communication is divided into public and internal channels depending on the sensitivity of the topic.
|
|
|
|
Infinito.Nexus is committed to transparency and actively encourages communication in public channels. Openness strengthens trust within the community and makes the project more accessible to everyone. Internal channels SHOULD only be used when a topic genuinely requires confidentiality.
|
|
|
|
### Public Channels 🌐
|
|
|
|
Public communication MUST be conducted through the following channels:
|
|
|
|
- **Matrix**: `#public:infinito.nexus` for general community discussion.
|
|
- **Hub**: [hub.infinito.nexus](https://hub.infinito.nexus) for tutorials, FAQs, and community support.
|
|
|
|
Examples of topics suitable for public channels:
|
|
|
|
- General questions about usage, setup, or configuration
|
|
- Feature ideas and community feedback
|
|
- Bug discussions that do not involve security vulnerabilities
|
|
- Contribution questions and workflow clarifications
|
|
- Announcements and release notes
|
|
|
|
### Internal Channels 🔒
|
|
|
|
Business, strategic, and security-relevant topics MUST be discussed in internal channels only and MUST NOT be shared in public rooms or forums.
|
|
|
|
Examples of topics that MUST stay internal:
|
|
|
|
- Business decisions, contracts, and partnerships
|
|
- Strategic planning and roadmap discussions
|
|
- Security vulnerabilities and incident response
|
|
- Personnel matters and team-internal coordination
|
|
- Financial and legal topics
|
|
|
|
## Reporting 📋
|
|
|
|
### Bugs and Issues 🐛
|
|
|
|
- Bugs and actionable issues MUST be reported at [s.infinito.nexus/issues](https://s.infinito.nexus/issues).
|
|
- Security vulnerabilities MUST NOT be reported there. See [SECURITY.md](../../../SECURITY.md) instead.
|
|
|
|
### Features and Work Items 🗂️
|
|
|
|
- Feature requests and all other work items MUST be tracked at [project.infinito.nexus](https://project.infinito.nexus).
|
|
|
|
## Threads 🧵
|
|
|
|
Element and Mattermost both support threaded replies. You MUST use threads to keep discussions focused and avoid cluttering the main timeline of a room or channel.
|
|
|
|
- You MUST reply in a thread when responding to a specific message or topic.
|
|
- You MUST NOT post follow-up messages to the main timeline if they belong to an ongoing thread.
|
|
- You SHOULD start a new thread for every distinct topic rather than continuing an unrelated conversation inline.
|
|
|
|
This keeps the main timeline readable as a high-level overview and prevents important messages from being buried in back-and-forth discussion.
|
|
|
|
## Language ✍️
|
|
|
|
- You MUST write in English in all public channels and threads.
|
|
- You SHOULD keep messages concise and on-topic.
|
|
|
|
## Ethics 🧭
|
|
|
|
In all communication and when handling data, you MUST respect the [Hacker Ethics](https://www.ccc.de/de/hackerethik) as defined by the Chaos Computer Club. This means treating information responsibly, protecting privacy, and acting in the interest of the public good.
|
|
|
|
## Conduct 🕊️
|
|
|
|
All communication MUST follow the project [Code of Conduct](../../../CODE_OF_CONDUCT.md).
|