~/forum/introduction/rules-and-guidelinescat thread.md

Rules and Guidelines

read-only

votes: 0
views: 0
replies: 0

Welcome to Unixland, a community dedicated to Linux/Unix systems, low-level programming, terminal environments, and system customization. To maintain a high-signal, productive, and respectful environment, all members must adhere to the following rules and guidelines.

0x01. General Conduct

1.1 Mutual Respect

Treat all members with respect. Harassment, personal attacks, trolling, and inflammatory behavior will not be tolerated. We welcome developers, system administrators, and enthusiasts of all backgrounds.

1.2 Elitism and Gatekeeping

While Unixland values deep technical expertise, gatekeeping and elitism are strictly prohibited. Do not dismiss beginners or demean users for their choice of distribution, desktop environment, or text editor. Help others learn through constructive feedback.

1.3 Keep it Technical

repliescat replies/*.md

composerguest@unixland:~/forum/introduction$

sign in to reply

Unixland is a technical forum. Avoid discussions regarding politics, religion, or other highly divisive non-technical topics. Keep the focus on technology, software engineering, open-source development, and computing.

0x02. Posting & Content Guidelines

2.1 Search Before Posting

Before creating a new thread or asking a question, use the forum's search function or your preferred search engine. Many common configuration issues, compilation errors, and setup problems have already been solved.

2.2 Post in the Correct Category

Ensure your thread is posted in the most relevant section (e.g., #kernel-space, #user-space, #tui-ricing, #low-level-dev). Off-topic posts will be moved or archived by the moderation team.

2.3 High-Quality Titles and Descriptions

Titles: Use clear, descriptive titles. Avoid ambiguous titles like "Help please!!" or "System broken". Instead, use concise summaries: "Systemd service fails to launch after kernel 7.0 upgrade".
Context: When seeking troubleshooting help, always provide relevant logs, hardware/software details, steps to reproduce, and what you have already tried.

2.4 Code and Log Formatting

Always wrap terminal outputs, configuration files (.conf, .lua, .toml), logs, and code snippets in proper Markdown code blocks with language syntax highlighting.
Do NOT post screenshots of terminal text, code, or stack traces. Paste the raw text within code blocks so it is searchable and accessible.

0x03. Technical & Security Policies

3.1 No Malicious Content or Warez

Do not share or request malicious software, exploits, or scripts designed to cause harm.
Sharing, requesting, or linking to pirated software, copyrighted material, or bypassing digital rights management (DRM) is strictly forbidden.

3.2 Security Vulnerabilities

If you are discussing a zero-day or unpatched vulnerability, follow responsible disclosure guidelines. Do not post actionable exploits that jeopardize infrastructure or individual user security.

0x04. Ricing & Showcase Rules

4.1 Provide Your Dotfiles

When showcasing your desktop environment, window manager, or TUI/CLI configuration (e.g., Neovim setups, status bars, customized shells), you must provide a link to your public dotfiles repo (GitHub/GitLab/Codeberg). Showcases without accompanying configuration files or detailed component listings will be locked or removed.

0x05. Moderation and Enforcement

5.1 Moderator Discretion

Moderators have final authority on interpreting and enforcing these rules. Actions may include post editing, thread closure, warnings, temporary suspensions, or permanent bans depending on the severity of the infraction.

5.2 Reporting Infractions

If you encounter a post or behavior that violates these guidelines, use the [Report] button rather than engaging or escalating the situation yourself. Let the moderation team handle it.

posted by ~endlevel developerat Jul 07, 12:18