Renaming things

There is an ongoing task to do a smart version of s/mysql/drizzle/gi on the code. (Running the actual regex isn't so much a good idea)

https://blueprints.launchpad.net/drizzle/+spec/rename-mysql-to-drizzle

Removing old crypt-like functions

No legacy == remove all the crappy crypt()-like functions which are completely breakable

http://twitter.com/brianaker/statuses/874887218

Compiler warnings / Static analysis

Andy Lester's favorite task!

gcc warnings should be ratcheted up as picky as possible, and configure should sniff out which ones are available. Parrot does this.

Work on a meaningful Splint target. Splint will generate crazy amounts of warnings, but the potential for tracking down memory leaks and invalid pointer use is huge. Andy has made much progress on this in Parrot.

Brian Aker has specifically asked for:

BTW at some point soon I want to get gcc to start flagging where we are not checking return types.

Documentation, Website and other "soft" topics

A web form for submitting blogs to the planet drizzle feed (blogs won't be added automatically, they will require approval).

Major Drizzle Developer Day 2009 task: Figure out organizational stuff for documentation:

- Manual
- Tutorials
- HOWTOs

Marketing buzz

- Get quotes about drizzle from #mysqlconf

Retrieved from "http://drizzle.org/wiki/Tasks_that_need_help"

Site generously hosted by SoftLayer Technologies

Contents

Renaming things

Removing old crypt-like functions

Compiler warnings / Static analysis

Documentation, Website and other "soft" topics