EloPhanto is maintained by its creator under a BDFL (Benevolent Dictator For Life) model. All major architectural decisions go through the project lead.
See CONTRIBUTING.md for setup and guidelines.
- Bug fixes: Submit a PR directly.
- Small features: Open an issue first for discussion, then PR.
- Major changes: Write an RFC (see docs/RFC-TEMPLATE.md), discuss in an issue, get approval from project lead, then implement.
- New skills: Follow SKILL_GUIDE.md, submit to EloPhantoHub.
For major architectural changes (new subsystems, protocol changes, breaking changes), write an RFC:
- Copy
docs/RFC-TEMPLATE.md - Fill in the template
- Open a PR with the RFC
- Discuss in PR comments
- Project lead approves or requests changes
- Merge RFC, then implement
Be respectful. Technical disagreements are welcome; personal attacks are not. The project lead has final say on disputes.
Releases follow calendar versioning: v2026.MM.DD. The project lead
decides when to cut a release.