The Drizzle project regularly gets people asking what they can do to get involved in the project.
One very easy way to brush up on your C++ skills and dip your toe into our open development process is to fix minor warnings.
We are very proud that Drizzle builds with zero warnings for with "gcc -Wall -Wextra".
But we can be even better! Our JenkinsCI system has a target that is even more picky, and also a target that runs cppcheck.
Go to one of those pages, pick a build log off the build history, find a warning that you think you can fix, and then ask us in the #drizzle channel on Freenode how to send your fix to us.
After you've done that a few times, you'll be ready to fix some low hanging fruit.
We've had people graduate from this process into becoming a Google Summer of Code student, and eventually having a full time paying job hacking on Drizzle and other open source software.
And it all starts with writing a simple warning fix.
No comments:
Post a Comment