I have been brushing up on my c++ skills lately so that I can be more adept with embedded systems programming.
I would like to contribute to MySensors and would like some guidance on where help is needed.
I see there are a few things here:
Do you have some special areas of interests? Usually, contributing something that you you need yourself is the most fun way to get started.
You can also browse https://github.com/mysensors/MySensors/issues and see if anything looks interesting.
thank you for the encouragement. My dream is to become proficient in small-scale industrial applications. For example, I would like to build a kitchen countertop food processor to process larger batches of fruits, pour them in (recycled) glasses in a protected sterile atmosphere, and seal them. Basically it would be a canning machine for the lazy :).
For now I want to apply my c++ skills.
The contribution guidelines are great, especially regarding coding style.
I'll have a look at the issues.
I can't find anything about writing tests. I see you have mentioned tests for building on different hardware. That's pretty neat. Did you document you testing infrastructure. I would be very interested in how you set that up. I imagine it being a pretty messy job.
I find it helpful to have a policy on testing code.
https://github.com/mysensors/MySensors/tree/development/tests/Arduino/sketches could give some insight
We don't have a unit testing framework in place, and we don't have a hardware setup for a system testing setup.
What we do currently is to let the buildserver attempt to build a number of sketches design to enable certain features in the library for all board types to validate that the features at least compile and don't produce warnings for the boards we support. Any sketch placed in the tests folder mentioned above will be automatically picked up and evaluated for all boards by the build server.