Community
Fid is developed in the open by one maintainer, Mehdi Berel at Pledge & Grow, and every design decision, rejected direction, and known limitation is written down in the repository. The community is young; this page is the map of where it lives.
Get help
- GitHub Discussions: questions, design debates, show-and-tell. Search before posting; the maintainer reads every thread.
- Issues: bugs and wrong-code reports. The best report is the smallest
.fdfile that reproduces the problem plus the output offid version. - The docs and Feature Status answer “does Fid do X?” honestly before you ask.
- The playground runs
fidesc, the Rust compiler, in your browser, so a question can come with a share link.
Contribute
The language, the compiler, the standard library, the docs, and this website all take contributions. Start with the contributing guide: it explains the two compilers, how to run the test suites, and what makes a change easy to review. Good first contributions are documentation fixes, new test programs, and standard library modules; none of them touch the compiler’s high-risk files.
Stay informed
- Changelog: every compiler update as it lands, with its own RSS feed.
- Blog: announcements and engineering deep dives (RSS).
- Releases: installers and archives, watch the repository to be notified.
- The roadmap: the plan from 1.1 to 2.0, in the repository where it is kept current.
Projects built with Fid
- The Fid compiler itself: 72 modules and about 210K lines of Fid that build themselves to a byte-identical fixpoint.
Shipping something in Fid? Open a Discussion in the “Show and tell” category; adopters get a place on this page.
The rules
Every Fid space runs under the Code of Conduct. Security-sensitive findings go through the Security Policy, not the public tracker. Decisions about the language itself are made as described on the Governance page.