Status 09/15/2005

, Will Kahn-Greene | share this (mastodon)
Note: This is an old post in a blog with a lot of posts over a long span of time. The world has changed, technologies have changed, and I've changed. It's likely this is out of date, the code doesn't work, the ideas haven't aged well, or the ideas were terrible to begin with. Let me know if you think this is something that needs updating.

I started grad school last week. The last few weeks have been pretty work-intensive as I squared away a lot of stuff so I didn't have to worry about it while I'm studying.

Also, bluesock suffered a hard drive failure and that took a few days to sort out.

I haven't finished the things I wanted to finish with PyBlosxom. I have been doing some research on Leonardo to see what sorts of things we can do to make installation, configuration, and extending PyBlosxom easier.

One thing I've been thinking about a lot is the current state of PyBlosxom plugins. I'm not as psyched about splitting plugins off into a separate project anymore. Lyntin had a core set of plugins that came with Lyntin and formed most of the functionality. Then users could add additional plugins if they so desired on a user-by-user basis. I think it's prudent to do the same thing with PyBlosxom. I think this will help the typical PyBlosxom installation. I'm not sure why I didn't think of this 8 months ago or so. I'd like to do this work for PyBlosxom 1.3.

Want to comment? Send an email to willkg at bluesock dot org. Include the url for the blog entry in your comment so I have some context as to what you're talking about.