Blame
|
1 | # Community |
||||||
| 2 | ||||||||
|
3 | Community documents how people participate in the AeThex ecosystem: contributors, users, creators, developers, moderators, and partner groups. |
||||||
|
4 | |||||||
|
5 | <div class="docs-section-heading"> |
||||||
| 6 | <h2>Community model</h2> |
|||||||
| 7 | <p>Community is the human layer around the technical platform.</p> |
|||||||
| 8 | </div> |
|||||||
|
9 | |||||||
|
10 | AeThex community spaces should connect back to clear systems: identity through [[Passport]], contribution rules through [[Open-Source]], governance through [[Governance]], and support through the support site and related docs. |
||||||
| 11 | ||||||||
| 12 | ## Community spaces |
|||||||
| 13 | ||||||||
| 14 | - Public announcements and updates. |
|||||||
| 15 | - Developer and creator discussion. |
|||||||
| 16 | - Support and troubleshooting channels. |
|||||||
| 17 | - Project-specific groups. |
|||||||
| 18 | - Foundation and governance conversations. |
|||||||
| 19 | ||||||||
| 20 | ## Operating principles |
|||||||
| 21 | ||||||||
| 22 | - Keep public guidance clear and archived where possible. |
|||||||
| 23 | - Move durable knowledge from chat into docs. |
|||||||
| 24 | - Use roles and permissions intentionally. |
|||||||
| 25 | - Separate support escalation from general discussion. |
|||||||
| 26 | - Keep governance proposals visible and traceable. |
|||||||
| 27 | ||||||||
| 28 | <div class="docs-grid"> |
|||||||
| 29 | <a class="docs-card" href="/Governance">Governance</a> |
|||||||
| 30 | <a class="docs-card" href="/Open-Source">Open Source</a> |
|||||||
| 31 | <a class="docs-card" href="/Foundation">Foundation</a> |
|||||||
| 32 | <a class="docs-card" href="/Policies">Policies</a> |
|||||||
| 33 | </div> |
|||||||