I re-worked the web-site so that it's checked into SVN along with the code and it's generated using the static renderer. I did this for a couple of reasons:

1. the web-site, except the wiki, is already static because we have read-only permissions to the file system on SourceForge
2. putting it in SVN allows enterprising individuals to pull the whole thing down and work to make it look way better
3. it makes it easier for us to move the PyBlosxom project to some other system
4. it provides me a really solid testing ground for static rendering

If you bump into any issues, let me know.

If you want to help overhaul the site so that it's way better, let me know.

/will (willhelm at users dot sourceforge dot net)

PyBlosxom is participating under the PSF in Google Highly Open Participation and it's been a huge help for our project.

In the first week, PyBlosxom had four tasks all focused on testing plugins in the PyBlosxom registry with PyBlosxom 1.4.2, reporting/fixing issues, adding documentation, ... From that we've updated five plugin entries:

• pygallery
• contact
• filter
• autoping
• latest

Many thanks to darkmessenger and CanadaBear for their work!

There are two plugin-status related tasks left in GHOP (both expired today) and four new tasks focusing on performance testing PyBlosxom and writing code in the wake of changes for PyBlosxom 2.0.

Ryan and I are writing up a task for continued work on unit tests in PyBlosxom. I'll be adding that as a task in the next round of adding tasks.

Additionally, this project has given me some ideas on how to better organize outstanding tasks so that it's easier for people to figure out how to help out. I'll be working on that going forward as well.

/will (willhelm at users dot sourceforge dot net)

I installed MediaWiki on SourceForge to manage and coordinate work on PyBlosxom 2.0. We're slowly building specifications which specify what PyBlosxom does in 1.4, problems with that behavior and how it should be changed for 2.0.

Discussion of the specifications should be kept in the discussion pages of the wiki and on IRC at #pyblosxom on irc.freenode.net.

As of this point, we've successfully moved all our code from a CVS repository to a Subversion repository. I went through the web-site and updated it to reflect the move to Subversion. I'm in the process of re-organizing some things in the repository to make them easier to deal with.

If you see any problems, let me know. Thanks!

/will (willhelm at users dot sourceforge dot net)

SourceForge switched the mount to read-only so we've taken down comments and other interactive features from this web-site.

I'm working on PyBlosxom 1.3 and project infrastructure. In the queue:

• pyblosxom 1.3 changes
  • fix bugs
  • flesh out variables for native RSS 2.0 and ATOM 0.3 flavours
• generate a todo list for the web-site
• add CVS usage blurbs to the development howto

/will (willhelm at users dot sourceforge dot net)

Thanks to work from both Robert Wall and David Geller, I've added a list of PyBlosxom users to the site. David did some work that makes the output a lot nicer, but I haven't quite gotten to working his script into the system. So this is a semi-temporary kluge for the time being.

I've been continuing to work on the PyBlosxom manual. I've put the latest version on the site. You can find the following information there:

• information installation
• information on setup and configuration
• a list of config.py variables and what they do
• information on plugins
• information on flavours
• information on static rendering
• information on syndication options
• how to write entries
• ...

If you're new to PyBlosxom, having problems with PyBlosxom, or are curious about things, check out the latest PyBlosxom 1.2 manual.

/will (willhelm at users dot sourceforge dot net)

I updated the site to use PyBlosxom 1.2. I also made some minor changes to the registry plugin that drives the Plugin Registry and the Flavour Registry. If you notice any problems, let us know on the pyblosxom-devel mailing list.

/will (willhelm at users dot sourceforge dot net)

I did a quick update to the links on the menu bar of the web-site (you can see the menu bar to the left there). We need to maintain separate versions of the documentation for prior versions of PyBlosxom and it was getting messy so I moved all documentation links to the new documentation page. Hopefully it's clear enough for new users and old users alike.

The list of things we've been thinking about doing for PyBlosxom is really long and contains items that have been fleshed out as well as items that haven't been fleshed out at all and are currently just looking for someone to do some more analysis. I'm going to take my notes and dump a bunch of "feature requests" in the feature tracker on the SourceForge section. The trackers are mildly crappy, but it's better than spending the time right now to build something on our own.

The plan right now is to let PyBlosxom 1.2 simmer a bit and shake out some of the issues it might have. Additionally, I'm going to try to spend some more time on fleshing out the manual and fixing up the contributed plugins that I either wrote or had a hand in writing.

We've got some ideas about what the next version will entail, but nothing is set in stone. It's likely we'll know more in a month.

And lastly, Planet PyBlosxom is no more. I had the domain name for a year and ran the site, but then decided I didn't want to run it any more. At some point, I'll set up something on here, but it's low-ish on my todo list at the moment.

I think that about covers it for this status update.

/will (willhelm at users dot sourceforge dot net)

Up until PyBlosxom 1.1, we included a series of contributed plugins in the ./contrib directory. These plugins were also listed in the registry. When PyBlosxom 1.1 released without this contrib directory we created the problem where no one was able to get a hold of the contributed plugins without downloading a previous version of PyBlosxom.

We're going to split up the release schedules for PyBlosxom and the contributed plugins pack. This makes it easier for us to fix problems with plugins without having to do another release of PyBlosxom.

We've released the first contributed plugins pack. It's versioned along-side PyBlosxom. So contrib.1.1 goes with PyBlosxom 1.1.

You can find the contributed plugins pack here.