Are you looking to write code that improves KiCad?
On Friday, Jan 31 (the day before FOSDEM), we’ll be hosting a Learn to Code KiCad session in Brussels, BE. I will be there as will Wayne and possibly a few other of the lead development team. We’ll help you understand how the various KiCad components fit together and work with you to get your favorite feature from idea to committed code.
What you need:
An identified bug report (or multiple) that you’d like to address. This can be either a legitimate bug or a wishlist feature that is triaged in our system.
A laptop with your development environment
A launchpad account
A compiling version of KiCad
A working knowledge of C++ coding
What we’ll provide:
Space, power outlet, wifi
Coffee
A short introduction to the structure of KiCad and how the parts work together
Up to 8 hours of development time with others who share your interests
Clarifying insights to your KiCad coding questions
At the end of the day, you should be able to get at least 1 and possibly multiple bug report fixes under your belt and into the code base!
If you’re coming to FOSDEM 2020 and would like to participate, please e-mail me directly (do not reserve in-thread here). Send me your name/contact info and the list of 1 or more launchpad bugs you’d like to work on during the day. I’ll add you to our shared sheet (to deconflict bugs people are addressing) and get you all of the relevant information for the meeting.
Back in the 90s, I once taught a course on programming languages. Since the goal was to teach multiple languages, I allowed students to submit their final coursework in the language of their choice. This worked well for a while until a //well-seasoned// coder took the course one year and turned all of her work in in PL/I. It took me as long to grade her assignment as the rest of the class together.
So for now, C++11 only. If someone wants to work on python plugins, we might expand that to SWIG and Python3.