good-enough/core-docs/good-enough-4u0-bylaws-outl...

38 lines
1.3 KiB
Markdown
Raw Permalink Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# Good Enough 4u0
### Bylaws (Outline, Hacker Edition)
**File:** `good-enough-4u0-bylaws-outline.md`
## 1. Membership
- Anyone can join.
- No degrees, no credentials required.
- To stay a member, you must contribute at least one *Documented Substandard Design* (DSD).
## 2. Contributions
- Every member submits one DSD: a design that is *not flawless, not useless, but good enough*.
- Each DSD must include:
- The defect (what makes it substandard).
- Documentation (enough for someone else to build it).
- License: free for anyone, no strings attached.
- Flawless designs are forbidden.
## 3. Competency
- Competency = knowing the line between “good enough” and “bad.”
- Members evaluate each others work for judgment, not perfection.
- Failed attempts are fine; hiding failure is not.
## 4. Governance
- Flat structure: no hierarchy, just maintainers.
- Maintainers = members who consistently contribute and document.
- Decisions: rough consensus and running code (or parts).
## 5. Commons
- Everything we make is public domain / commons.
- Industry can take it, fix it, commercialize it—we dont care.
- Our value is the shared pool of imperfect-but-useful knowledge.
## 6. Culture
- Celebrate imperfection.
- Share openly, document clearly, fail loudly.
- The only hard rule: **dont ship flawless.**