<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Thank you for volunteering. <div class=""><br class=""></div><div class="">I had a bit of time to think about what project you might enjoy. </div><div class=""><br class=""></div><div class="">And of course that is the first rule of open source software, you should work on what you enjoy. </div><div class=""><br class=""></div><div class="">Unlike a job. ;-)</div><div class=""><br class=""></div><div class="">So tell us what interests you and we will see what we can recommend.</div><div class=""><br class=""></div><div class="">In the meantime, I have some ideas. testing out grok.project is a good start. Whenever I approach an open source project, I find the best thing to do is to write documentation. I read the code, maybe I do not quite understand it, so I write what I understood. If I get it right, perfect. If I get it wrong, the senior developers are always keen to correct it. Either way, my understanding of the software increases.</div><div class=""><br class=""></div><div class="">Some people like to write docs, some do not. It all depends on you. Paul is wonderful, both a good software developer, and good at docs. You might want to start by reviewing the grok tutorial he wrote..</div><div class=""><br class=""></div><div class="">You can find the link here:</div><div class=""><a href="https://pythonlinks.info/grok" class="">https://pythonlinks.info/grok</a></div><div class=""><br class=""></div><div class="">Look for “Grok tutorial"</div><div class=""><br class=""></div><div class="">Chris</div><div style="font-size: 36px;" class=""><br class=""></div></body></html>