Community Guidelines

Purpose

ArchForge welcomes constructive development, open-source collaboration and Arch Linux discussion. These Guidelines apply to issues, pull requests, discussions, chat, groups, tutorials, showcases, profiles and other interactive content.

Respect and safety

Be civil. Do not threaten, harass, intimidate, stalk, dox, sexually exploit or encourage targeted abuse. Do not discriminate unlawfully against people or impersonate another user or organization. Avoid publishing personal addresses, credentials, private communications or screenshots containing secrets without permission. Disagreement about software choices and constructive criticism are permitted; personal attacks are not.

Relevant, authentic participation

Keep posts relevant to their forum, issue or channel. Avoid automated spam, manipulative engagement, duplicate promotional links and deceptive verification claims. Clearly identify when sharing third-party material or AI-generated content where its provenance matters. Do not manufacture maintainership or Git author affiliation; a Git commit author name alone is not proof of an ArchForge identity.

Responsible security topics

Security research and discussion are welcome when lawful and responsibly disclosed. Do not use tutorials, attachments or repositories to attack others, spread active malware or collect unauthorized credentials. Use the Security Policy to report actual platform vulnerabilities, not a public issue exposing exploit details.

Reports and moderation

Use the Report Illegal Content form for allegedly illegal content and the site's existing report tools for community-rule concerns. A report is an allegation, not proof. Moderators may warn, label, hide, restrict, suspend or remove content when authorized and proportionate, documenting reasons and review procedures. Availability and timing of appeals depend on law and published processes. Repeated malicious reports may be treated as abuse.

Helpful contributions

Credit contributors, respect maintainers' time, use clear issue reports with reproductions, mark solutions when appropriate and avoid demanding personal support. Treat people who are new to Arch Linux or Git respectfully.

Changes and version history

This policy applies from its stated effective date once published. Material changes are dated and versioned. Earlier versions remain available to administrators for audit, and any notice or renewed agreement required by applicable law is handled separately. Questions and legally valid notices may be sent using the contact details in the Legal Notice.