JOCKY Community

Where to find us

Discussions

Questions, feature ideas and show-and-tell. New here? Start with the welcome thread.

Open Discussions

Issue tracker

Report reproducible bugs in the compiler, runtime, standard libraries or tools.

View issues

Contributing guide

How to set up, build, test and submit changes to JOCKY.

Read CONTRIBUTING.md

Security

Report vulnerabilities privately. Please don't post them in public issues.

Report privately

Introduce yourself in the welcome thread

Contribute

You don't need to be a compiler engineer

There are many ways to help, from fixing compiler bugs and improving documentation to designing language features and building forensic tooling. Contributors of every experience level are welcome.

Code

The compiler (lexer, parser, AST, semantic analysis, type checking, LLVM IR generation, optimization passes), JOCKYShield, runtime, standard libraries, forensic and CLI tooling, and CI.

Documentation

Getting-started guides, language and API docs, compiler and architecture docs, tutorials, examples, forensic workflows and troubleshooting.

Testing

Regression tests, compiler edge cases, new language features, other platforms, generated binaries and compiler benchmarks.

Ideas

Start a discussion about language features, compiler architecture, standard library APIs, forensic workflows, tooling, performance or security.

Your first contribution

Fork the repository on GitHub, then clone your fork:

$ git clone https://github.com/YOUR-USERNAME/jocky.git
$ cd jocky

The development workflow section of the guide walks you through the rest.

Code of conduct

Contributors come from different technical backgrounds and experience levels. Please be respectful and constructive. When participating:

Be respectful to other contributors.
Critique code and ideas, not people.
Explain disagreements constructively.
Avoid harassment, discrimination and personal attacks.
Give credit where credit is due.
Assume good intent.
Help newcomers learn.

Project maintainers may remove contributions or discussions that violate these principles.

Reporting a vulnerability

Use GitHub's private vulnerability reporting so the issue can be fixed before it's made public.