Thank you for your interest in contributing to Aether — the AI-centric programming language.
- Fork the repository and create a feature branch from
main. - Make your changes — keep commits focused and atomic.
- Test your changes:
cargo build --release && cargo test - Sign your commits with a DCO sign-off (see below).
- Open a pull request against
mainwith a clear description of what and why.
All contributions must be signed with the Developer Certificate of Origin. This certifies that you have the right to submit the contribution under the Apache 2.0 license.
Sign each commit with -s (or --signoff):
git commit -s -m "feat: add new intent to ASL registry"
This adds a Signed-off-by: Your Name <your@email.com> trailer to the commit message. Pull requests without DCO sign-offs will not be merged.
- Grammar / Parser (
src/aether.pest,src/parser.rs) — new syntax proposals should include spec updates inspec/aether.ebnf - ASL Registry (
asl/registry.json) — new standard intents should include description, safety level, recommended language, and rationale - Executor (
src/executor.rs) — performance improvements, new guest language support - Documentation (
docs/) — corrections, examples, and clarifications always welcome - Examples (
examples/) — real-world.aeprograms demonstrating Aether capabilities
- Run
cargo clippybefore submitting — zero warnings expected - Run
cargo fmtto format your code - Public functions should have doc comments (
///)
Open a GitHub Issue with:
- Aether version (
aether --version) - The
.aeor.asprogram that triggers the bug - Expected vs. actual behavior
- Full error output
Please do not open public issues for security vulnerabilities. See SECURITY.md for the responsible disclosure process.
By contributing, you agree that your contributions are licensed under the Apache License 2.0.