Getting started as a KiCad contributor

Hi all,

I’m a hardware developer with experience in ECAD tools (including KiCad) and a strong background in C++. I’d love to contribute to KiCad, especially in core areas like GUI or backend logic.

The repo is set up and building – what’s the best way to start? Are there beginner-friendly issues or small tasks to dive into? Is it okay to just comment on an issue and go ahead?

Thanks for any pointers – looking forward to contributing!

Best,
Tobias

4 Likes

The developer mailing list is the place to start from. This forum is mainly about end user things.

https://groups.google.com/a/kicad.org/g/devlist?pli=1

1 Like

You can take a look at the bug tracker:

I would recommend to pick a few bugs that seem easy and commit fixes for them.
Once the team gets to know you and your work, you can start taking on features.

For features and bigger changes there is usually a specification or other types of communication first. If you start implementing $Feature it is quite likely that it won’t get merged since it conflicts with other plans that you can’t know of.