Skip to content

filesdot/.github

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

15 Commits
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

Code of Conduct 🀝

Version: 2.0
Adopted: June 2026
Based on: Contributor Covenant 2.1


🎯 Our Pledge

We as members, contributors, and leaders pledge to make participation in the Awesome Linux Ricing community a harassment-free experience for everyone, regardless of:

  • Age, body size, visible or invisible disability
  • Ethnicity, gender identity, and expression
  • Level of experience, education, and socio-economic status
  • Nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation
  • Technical preferences (WM, DE, distro, editor, shell, etc.) 🐧

We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.


✨ Our Standards

🟒 Examples of behavior that contributes to a positive environment:

  • Being respectful of differing viewpoints, experiences, and ricing philosophies
  • Giving and gracefully accepting constructive feedback
  • Acknowledging mistakes, apologizing to those affected, and learning from the experience
  • Focusing on what is best for the community and the project
  • Using welcoming and inclusive language (e.g., "they/them" pronouns, avoiding ableist terms)
  • Helping newcomers feel welcome, regardless of their skill level
  • Celebrating diversity in desktop setups, there's no "one true way" to rice! 🎨

πŸ”΄ Examples of unacceptable behavior:

  • The use of sexualized language or imagery, and sexual attention or advances of any kind
  • Trolling, insulting, or derogatory comments, and personal or political attacks
  • Public or private harassment, including doxxing or sharing private information without consent
  • Publishing others' private information (e.g., physical/email address) without explicit permission
  • Dismissing or belittling others' preferences (e.g., "X11 is dead", "Wayland users are elitist", "Vim is superior")
  • Spamming, self-promotion without value, or malicious link submissions
  • Any conduct which could reasonably be considered inappropriate in a professional setting

πŸ›‘οΈ Enforcement Responsibilities

Community leaders (maintainers) are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.

Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, pull requests, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.


🌍 Scope

This Code of Conduct applies:

  • βœ… Within all community spaces (GitHub Discussions, Issues, PRs, README comments)
  • βœ… In official community channels (Discord, Matrix, forums linked by maintainers)
  • βœ… When an individual is officially representing the community in public spaces (e.g., conference talks, blog posts tagged with the project)
  • βœ… In interactions related to the project, even outside official channels

βš–οΈ Enforcement Guidelines

Community leaders will follow these guidelines when determining consequences for violations:

1️⃣ Correction

Community Impact: Use of inappropriate language or other behavior deemed unprofessional or unwelcome.

Consequence: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.

2️⃣ Warning

Community Impact: A violation through a single incident or series of actions.

Consequence: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period. Violating these terms may lead to a temporary or permanent ban.

3️⃣ Temporary Ban

Community Impact: A serious violation of community standards, including sustained inappropriate behavior.

Consequence: A temporary ban from any sort of interaction or public communication with the community for a specified period. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.

4️⃣ Permanent Ban

Community Impact: Demonstrating a pattern of violation of community standards, including sustained harassment, aggression, or disparagement of individuals or groups.

Consequence: A permanent ban from any sort of public interaction within the community.


πŸ“¬ Reporting Guidelines

If you experience or witness unacceptable behavior:

  1. Document the incident: Save screenshots, links, or quotes if possible
  2. Contact a maintainer directly via:
    • πŸ™ GitHub: @flessan (via Issue or Discussion)
    • πŸ’¬ Discord: DM a moderator with the @Maintainer role
    • βœ‰οΈ Email: [email protected] (replace with actual)

What to include in your report:

## Incident Report

### Your contact info (optional but helpful):
[GitHub username / Discord handle]

### What happened:
[Clear, factual description with timestamps if possible]

### Where it happened:
[Link to Issue/PR/Discord channel/etc.]

### Who was involved:
[Usernames/handles of people involved]

### Any evidence:
[Screenshots, logs, links]

### What you'd like to see happen:
[Your desired outcome]

What to expect:

  • βœ… Acknowledgment: We'll confirm receipt within 48 hours
  • πŸ” Review: A maintainer not involved in the incident will investigate
  • 🀝 Confidentiality: Your report will be kept confidential; details shared only with those who need to know
  • βš–οΈ Resolution: We'll communicate the outcome and any actions taken (while respecting privacy)

πŸ›‘οΈ Protection against retaliation: We will not tolerate retaliation against anyone who reports a concern in good faith.


πŸ”„ Attribution & Updates

This Code of Conduct is adapted from:

Version History

Version Date Changes
2.0 June 2026 Added Linux-ricing-specific examples, expanded reporting guidelines
1.0 Initial Based on Contributor Covenant 2.1

Future Updates

This document may be updated to better serve our community. Changes will be:

  • Announced in GitHub Discussions
  • Versioned with clear changelogs
  • Applied only to new reports (grandfathering prior behavior unless severe)

🌱 Community Values

Beyond rules, we aspire to embody these values:

Value What it means for us
Inclusivity Your desktop, your rules. We celebrate all ricing styles, from minimal tiling to eye-candy extravaganzas.
Learning No question is too basic. We remember being beginners too.
Collaboration Share configs, tips, and inspiration. Ricing is better together.
Respect Disagree about WM philosophy? Debate ideas, not people.
Joy At its heart, ricing is about creativity and fun. Let's keep it that way. 🎨✨

❓ Frequently Asked Questions

"Is it okay to joke about other WMs/distros?"

Light-hearted, good-natured humor is fine, if everyone involved is in on the joke. But avoid:

  • Punching down at newcomers or less technical users
  • Using stereotypes to dismiss preferences ("Only script kiddies use X")
  • Repeatedly mocking a choice after someone has expressed it's important to them

When in doubt: Ask, don't assume. 😊

"What if I see a toxic comment in a linked external resource?"

We can't control external sites, but you can:

  1. Report the content to that platform
  2. Let us know via an Issue so we can consider removing the link if it's consistently problematic
  3. Suggest alternative resources that align with our values
"I made a mistake and violated the CoC. What now?"

Thank you for reflecting. Here's what to do:

  1. Pause: Step back from the conversation
  2. Apologize sincerely: Acknowledge the impact, not just the intent
  3. Learn: Review this CoC and ask how to do better
  4. Move forward: Apply what you've learned in future interactions

We believe in growth. One mistake doesn't define you, how you respond does.



πŸ™ Thank You

By reading this Code of Conduct, you're helping build a community where everyone can share their passion for Linux customization safely and joyfully.

🐧 "The best desktop is the one that makes you happy."

Made with ❀️ by the Awesome Linux Ricing Community

About

No description, website, or topics provided.

Code of conduct

Contributing

Security policy

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors