FAQ/Guidelines

Community Guidelines

TL;DR: Good communities run on good conversations. Post things worth reading, be honest when you disagree, keep it vendor-neutral, and flag problems instead of feeding them.


These guidelines keep this a useful, welcoming place to learn and contribute. They’re not a rulebook. They’re a shared standard we hold ourselves to.


Posting

Good posts are specific, reproducible, and easy for someone else to learn from.

Every post should:

  • Have a clear, searchable title
  • Include relevant versions, environment details, and steps
  • Put code, configs, and logs in fenced code blocks
  • Link to repos or references where relevant
  • Remove secrets, credentials, and internal data before posting
  • Summarize the solution or outcome at the end

Avoid:

  • Posting credentials or sensitive internal data
  • Attacking people. Critique ideas and implementations, not the person
  • Promotional or marketing content

Asking Questions

A good question is specific and reproducible. The more context you provide, the faster you’ll get a useful answer.

Include:

  • Your environment: versions, OS, cluster, backend
  • Steps to reproduce the problem
  • What you expected vs. what actually happened
  • What you’ve already tried

When your question is resolved, mark the Accepted Solution. It helps the next person with the same problem find the answer quickly.


Vendor-Neutral Policy

Technical product mentions are fine when they’re relevant and reproducible. Sales copy and promotional content are not.

Focus on open standards and broadly applicable patterns. If you mention a specific product, keep it technical and neutral, not a pitch.

Posts that read as marketing will be removed. Repeated violations may lead to moderation action.


Be Respectful

Disagree with ideas, not people.

Avoid name-calling, personal attacks, and responding to someone’s tone rather than their actual content. If you’re not sure a reply adds anything, sit on it.

Harassment is never tolerated. Constructive disagreement always is.


Keep It Tidy

  • Post in the right category
  • Don’t cross-post the same thing across multiple topics
  • Don’t derail a thread by taking it somewhere unrelated
  • Use the Like button instead of posting “+1” or “Agreed”

Staff may retitle, move, or retag posts for clarity. We’ll leave a brief note when we do.


Post Only Your Own Stuff

Don’t post content that belongs to someone else without permission. Don’t link to or describe methods for circumventing intellectual property or breaking any law.


Staying in the Loop

Keep up with new challenges, tutorials, and events by managing your notifications.

Categories:

Subscriptions:

  • Watch categories you care about (bell icon, then Watching)
  • Keep weekly digests on for highlights
  • Mute categories you don’t need to reduce noise

Events:

  • Watch Events & Talks for upcoming sessions
  • Add events to your calendar and check recaps for slides, repos, and recordings

Preferences:

  • Manage notifications under Preferences, then Notifications
  • Control email frequency and per-category watching or muting
  • Enable desktop or mobile notifications if you want real-time alerts

Recognition

Progress through the contributor ladder, earn badges, and appear on the leaderboard. Outstanding solutions and tutorials are highlighted periodically.


If Something Feels Off

Don’t reply to bad behavior. Flag it. Replying gives it attention; flagging gets it dealt with. If the issue is sensitive, DM @moderators directly.

Moderators can remove content or accounts at any time to maintain the health of the community.

Have feedback on how to improve these guidelines or the community? Share it in Site Feedback.


Public Forum Reminder

This forum is search-indexed. Anything you post is publicly visible. Don’t share credentials, secrets, or internal data, even as examples.


For enforcement details, see the Code of Conduct and Privacy Policy.

Edit the first post in this topic to change the contents of the FAQ/Guidelines page.