my status until June 3rd

I'm getting married on Saturday and I need to get a bunch done between
now and then.  After that I'm on a honeymoon (and I promised not to
bring my computer).

Ryan is an active developer and has checkin privs.  I defer all
decisions to him until I get back.  I look very much forward to
finishing things up for a 1.4 release.  If there are additional things
that should go in before that time, then that's cool with me--I'm not
hung up on what should and shouldn't go into the release so long as
it's "well tested" and something that many/most/all people agree is a
good thing.

I'd like to do a second release this summer some time.  I think that
gives Z a chance to factor adjustments into PyBlosxom core that make
his GSoC project easier/better/more-robust/etc.  I mention this so
that everyone knows the intention is to do a follow-up release as
opposed to waiting another year and a half.

Having said that, I think the PyBlosxom core is doing pretty well.
There are some things I'd like to fix (I really want flawless WSGI
support [and better documentation] and possibly paste command-line
support), but for the most part I want to focus on better
documentation, better testing, and a better infrastructure for
creating, finding, and using plugins.  In the future, there should be
more effort on plugins and flavours and usability and less effort on
tweaking the core.

That's all theoretical off-the-cuff thinking, though--we may find out
as time continues that we're not quite at that point yet.

Good luck until then.  I'm psyched that the project is moving along
again and that there are so many voices involved.  That's way cool.
w00t!

Rock on!
/will

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/