I've been fleshing out more of the PyBlosxom Manual to give Ted more material for a possible PyCon 2005 talk and also to fill in documentation gaps which will make a PyBlosxom 1.1 release easier for people.

I encourage folks to skim the manual as it is thus far. I'm still doing some minor organizational changes, but for the most part what's there will form the basis of the continuing manual saga. If you have comments, complaints, interesting stories, or even additional manual material, toss it in the comments at the bottom of the relevant chapter.

Rock on!

/will (willhelm at users dot sourceforge dot net)

More changes:

• added some more chapters to the pyblosxom manual covering topics like flavours and templates, plugins, and static rendering
• added a "printer-friendly" link to the manual pages
• fixed some bugs in some of the plugins that this site uses
• went through and made sure the site validates as HTML 4.01 transitional (which caused me to discover some issues here and there with the HTML)
• added a colophon

Ben asked on the pyblosxom-users list whether there's anything other folks can do to help with this site. The answer is yes, but it's nothing that's wildly exciting or glamorous.

It would help if people could review the content in the manual. There are a couple of ways you could send fixes, adjustments, and your thoughts on the content. The first is to post a comment at the bottom of the chatper in question. The second is to send an email to willhelm at users dot sourceforge dot net. The third is to send an email to the pyblosxom-users mailing list. Try to be as clear as you can about what you're trying to say. Feel free to quote the sections you have issues with. I'll incorproate any comments, thoughts, and additional content into the manual as I get them. I'll create a contributors section on the content page with a list of contributors.

Additionally, people are looking for flavours so if you have any to register, please do.

I think that's about it. We're still moving along at a steady clip. Assuming we can maintain this clip, we should have a solid PyBlosxom manual in a month or so--that's a huge step in making PyBlosxom more user-friendly for all of us.

/will (willhelm at users dot sourceforge dot net)

Seems a little silly to have yet-another-pyblosxom site, but here's the thinking: we need a site that supports users, supports developers, has a manual, and centralizes flavours and plugins and stuff. We're putting it on SourceForge with the rest of the project stuff. We couldn't put it here until a week ago because their servers didn't have a version of Python installed that could run PyBlosxom. But it does now, so everything's cool again.

So far I have the following things working on this site:

• news entries
• plugin registry
• flavour registry
• registry submissions
• comments with secret number comment-spam prevention
• rss for news and rss for registry
• the start of a pyblosxom manual

Still to do:

• need a way to administrate comments (web-form?)
• need to implement bloggar entry creation
• continue working on pyblosxom manual
• need to add comment preview (use Steven's version?)
• need to add a link for archives

Overall, though, things are looking good. Hopefully it shouldn't take too long to put the rest of the critical pieces together.

/will (willhelm at users dot sourceforge dot net)

I posted my todo list (culled from who-knows-what sources) on the wiki because I'm no longer doing active development.

Anyone who is interested in doing PyBlosxom development and want something to work on could work on items on the list.

Anyone who wants things implemented (plugins included), should add things to the todo list.

Just know that if we have lots of people adding todo items and no one working on them then nothing will get done. I encourage people who are adding items to work on completing other items. More details on this page:

http://wiki.subtlehints.net/moin/PyBlosxomToDo

That's about it. 1.0.1 coming soon--mostly when I get around to releasing it.

Rock on!

/will (willhelm at users dot sourceforge dot net)

We've cleaned up a lot code and documentation and fixed a lot of bugs. We've stabilized the API and added static rendering. In short, this should be a pretty solid 1.0 milestone for PyBlosxom.

I encourage people to upgrade. When you untar the distribution tarball, read through INSTALL and README. These files will walk you through installation and upgrading from 0.9.

Download now! (sourceforge.net)

Rock on!

/will (willhelm at users dot sourceforge dot net)

I'm releasing pyblosxom 1.0 RC1 right now. I overhauled the callback documentation in the ReadMeForPlugins file and read through other documentation and I think we're good enough for a 1.0 release now.

The RC1 is here (bluesock.org)

Feel free to download it and test it out--it's very much like alpha1 with a few differences:

• I threw in a logdir property into config.py and adjusted plugins that use logfiles to use it.
• Documentation fixes.

That's about it, I think.

In the tar.gz file is an INSTALL file which details installing PyBlosxom. There is also a README which talks about differences between 0.9 and 1.0 (which will help you upgrade an existing PyBlosxom installation).

Let me know what you think. I plan on doing a 1.0 release in the next few days. Probably Thursday.

/will (willhelm at users dot sourceforge dot net)

This is a maintenance release to fix some minor nits that were discovered after 0.9 was released. If you have 0.9 installed and it's working fine, then don't worry about upgrading.

This release has the following changes in it:

• Fixed MANIFEST.in file to include comments flavour files and README
• Fixed make_logger to work better for Python 2.2 and earlier versions
• Fixed the entryshelve caching plugin
• Update pytextile entryparser to 2.0
• Fixed verify_installation code to work when load_plugins is not set
• Fixed a bug with pycategories plugin

That's it!

If you have any problems, let us know on the pyblosxom-users list.

Download now! (sourceforge.net)

This is my quick plug for PlanetPyblosxom. The site will focus on Pyblosxom users and using Pyblosxom. I'm slowing moving all my material from my blog to the PlanetPyblosxom blog. We're also moving the plugin registry there as well.

Please check out the site and if you have any comments, let me know at willg at bluesock dot org.

Rock on!

/will (willhelm at users dot sourceforge dot net)

After several months of hard work by all the developers and members of the community, we've released the next version of Pyblosxom.

0.9 has the following changes in it:

• Added a logger and locking code
• Overhauled the xmlrpc system
• Added the verify_installation code
• Added handle callback
• Added Atom 0.3 flavour
• Overhaul of code base to fix concurrancy issues
• Added support for Metaweblog API
• Bug fixes, security fixes, and optimizations

It's highly encouraged that all people upgrade since plugins written for 0.9 will not work in previous versions of Pyblosxom.

If you have any problems, let us know on the pyblosxom-users list.

Download now! (sourceforge.net)

/will (willhelm at users dot sourceforge dot net)

This is the first time I've posted to the pyblosxom site, so bear with me.

PyBlosxom took a small nap after 0.8.1 was released in order to let us all catch up and figure out where we want to go and what is required for a 1.0 release. About a month ago, developement started up again with several focii:

• clean up the code-base
• add support for locking (which may be taken out)
• add support for logging
• fix concurrancy issues
• fix bugs (architectural and behavioral)
• add support for unit testing
• add support for static rendering

There isn't a set timeline or a roadmap. For the most part, we're working diligently and when we're ready for a release, we'll release then. It's likely the next release will be 0.9.0 and it'll be in the next few weeks since it's been a long time since the last release and there have been some major architectural changes made.

So that's the status as I understand it at this stage in the game.

/will (willhelm at users dot sourceforge dot net)