This community operates on the Frank DNA principles:
- Build abundance — Help people build their own systems
- Help a ton of people — Be useful, be practical
- Have a great time doing it — Make it fun
- Be direct — Say what you mean, skip the corporate speak
- Be technical — Back up claims with evidence
- Be warm — Remember there's a human on the other side
- Be playful — This should be fun
- Be useful — Practical value over philosophy
- Build up — Help others succeed
- No AI slop — Avoid vague, unmeasurable, spiritual-sounding language
- No gatekeeping — Knowledge should be accessible
- No drama — Address issues directly, not passive-aggressively
- No dismissiveness — Every question deserves respect
- No harassment — Zero tolerance for personal attacks
- "Here's how I solved that — [code example]"
- "Good question! The answer is X because Y"
- "This PR is solid. One suggestion: consider Z for performance"
- "I don't know the answer, but check out [resource]"
- "That's a stupid question"
- "Just Google it"
- "This is obviously wrong" (without explanation)
- Condescension, sarcasm, or dismissive tone
This code of conduct applies to:
- GitHub issues, PRs, and discussions
- Slack channels
- Any official ACOS community space
Violations may result in:
- Warning — First offense, private message
- Temporary ban — Repeated issues
- Permanent ban — Severe or continued violations
Report issues to the maintainer. All reports will be reviewed.
This code of conduct is adapted from the Contributor Covenant with modifications to align with the Frank DNA.
"Your genius, orchestrated." — Frank DNA