Blame
|
1 | # Open Source |
||||||
| 2 | ||||||||
|
3 | Open Source explains how public AeThex code, documentation, tools, and community contributions should be managed. |
||||||
|
4 | |||||||
|
5 | <div class="docs-section-heading"> |
||||||
| 6 | <h2>Contribution model</h2> |
|||||||
| 7 | <p>Open-source work should be useful, reviewable, and connected to the platform roadmap.</p> |
|||||||
| 8 | </div> |
|||||||
|
9 | |||||||
|
10 | Open-source contributions can include code, docs, examples, issue triage, templates, and community tooling. This page should link contributors to the right repos, standards, and decision processes as they become public. |
||||||
| 11 | ||||||||
| 12 | ## Contribution areas |
|||||||
| 13 | ||||||||
| 14 | - Documentation updates. |
|||||||
| 15 | - SDK examples and integration samples. |
|||||||
| 16 | - CLI improvements. |
|||||||
| 17 | - Community tooling. |
|||||||
| 18 | - Bug reports and reproduction cases. |
|||||||
| 19 | - Governance or standards proposals. |
|||||||
| 20 | ||||||||
| 21 | ## Maintainer expectations |
|||||||
| 22 | ||||||||
| 23 | - Keep contribution instructions current. |
|||||||
| 24 | - Label beginner-friendly and high-priority work. |
|||||||
| 25 | - Require review for security-sensitive changes. |
|||||||
| 26 | - Archive decisions in docs or governance notes. |
|||||||
| 27 | ||||||||
| 28 | <div class="docs-grid"> |
|||||||
| 29 | <a class="docs-card" href="/Governance">Governance</a> |
|||||||
| 30 | <a class="docs-card" href="/Policies">Policies</a> |
|||||||
| 31 | <a class="docs-card" href="/SDKs">SDKs</a> |
|||||||
| 32 | <a class="docs-card" href="/CLI">CLI</a> |
|||||||
| 33 | </div> |
|||||||