[Pam-mysql-general] Short-term Road Map

[James O'K. <jo...@mi...>]

This weekend I merged the differences I could see from the sql-logging 
branch into the main branch, and it currently has 'works for me' status. I 
currently don't have a production environment, so I can't test it under 
any kind of load or anything.

I've received email from several different people wanting to merge a few 
different projects including the postgresql pam module, the db-pam module 
that allows arbitrary queries, and possibly some of the nss-mysql code. 
Before I start piling code into this, I want to do some housekeeping and 
reorganization because pam_mysql.c is currently over 1200 lines and is 
getting a bit messy.

My rough todo list:
If no one complains about the HEAD branch of CVS, I'm going to make that 
0.5 and do a release.
Do a reorganization and possibly call that 0.6
Add in one of the suggested features above, probably nss-mysql since that 
will hit the most people. Call that 0.7
Add in the next feature, call that 0.8
lather, rinse, repeat.

I currently don't have a timebased deadlines, so things will happen when I 
have time. It's been over 2 years since the last release, what is an extra 
few months? :)

-james