Get involved

Helion is Apache-2.0 OR MIT. One owner today. That only changes if people show up.

1. Get connected

   Ask in GitHub Discussions. Bugs and features go in Issues. There is no Discord yet. Do not wait for one.

2. Decide what to work on

   Pick a good first issue, or say what you want to own (SV ingest, STA, IDE tests, docs, CI). Current release is v2.0.4. Shipped 1.4 to 2.0 and the 2.0.x grind are on the roadmap and milestones. The crate map is on Architecture.

3. Build your own copy

   Follow Start. Empty-XDC examples/counter.sv must print WNS_PS=9640. Work on master.

4. Find the code

   See the crate map on Architecture and the table in Contribute. GUI paint is not the engine. IdeModel is.

5. Ship a patch

   One crate when you can. One test name while iterating: cargo test -p CRATE --lib TESTNAME. Open a PR and fill the template. Read the legal fence first.

Ways to help that are not CAD

• Review PRs and test them on macOS / Linux.
• Improve this documentation site (docs/).
• Triage issues; turn “it broke” into a command + log.
• Sponsor hosting, domain, and time until a treasurer is named.

Code of conduct

Helion follows the Contributor Covenant. Disagreement about CAD is expected. Personal attacks and vendor-IP dumps are not. Enforcement: @saksham-45.

Help wanted Coding guide