Hi! As Jay and Monty had mentioned, it's definitely worth it and I'm more than happy to mentor this also.
I suspect no one will get everything done in 12 weeks since this is one of those never ending stories that will keep going on. There's still a lot of reinvented code in the repository so porting them to use libc/STL and POSIX compliant calls itself should keep you busy for the summer :) Cheers, Toru On Fri, Apr 3, 2009 at 2:35 AM, nlws <[email protected]> wrote: > I have been interested in applying to Google's Summer of Code this > year but hadn't been able to decide on an project yet. I know I'm > pushing it close to the application deadline tomorrow, but I > just saw Brian Aker's blog post [1] about working on Drizzle! The > 'code clean up / c++ standardization' task [2] is what really jumped > out at me. > > In short, I was hoping to get some feedback about doing that, what > would be a good schedule, any suggestions, etc. For example, the > blueprints for that task have 7 areas of focus. For the 12 weeks of > work would a week and a half per area be reasonable / acceptable / > enough work / too much work? > > Thanks, > Nathan WIlliams > > > [1] - http://krow.livejournal.com/633660.html > [2] - http://drizzle.org/wiki/Soc#Code_Cleanup > > _______________________________________________ > Mailing list: https://launchpad.net/~drizzle-discuss > Post to : [email protected] > Unsubscribe : https://launchpad.net/~drizzle-discuss > More help : https://help.launchpad.net/ListHelp > -- Toru Maesaka <[email protected]> _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
