From PyBlosxom

Contents 1 Summary 2 2.0 Mission 3 How can you help 4 Adding a specification 5 Other notes

Summary

We're trying to make sure we have a good understanding of where we've been and where we're going for PyBlosxom development. The following pages address specific functionality and how it should be changed for future versions.

2.0 Mission

The mission for PyBlosxom 2.0 is:

1. to fix bugs
2. to reduce complexity, but increase flexibility
3. to push functionality out to plugins
4. to refactor code that is demonstrably inefficient, inflexible or overly complex
5. to increase PyBlosxom's user-friendliness in terms of installation, setup and personalizing
6. to add more tests: unit, functional, regression

This is a big cleanup release. We're breaking the API where needed but only when necessary.

In parallel with the 2.0 coding, we'd also like to rework the plugin registry, flavour registry and documentation.

How can you help

You're a user, developer or otherwise involved with PyBlosxom. If you want to join the effort, you can:

1. write specifications for features you want to see implemented
2. flesh out out existing specifications by commenting on them in the discussion page -- even a "this spec is really helpful because it allows me to do xyz" is really useful because it adds use cases for us all to frame our thinking
3. write unit, functional and regression tests for existing and new functionality in PyBlosxom
4. fix existing documentation and write new documentation -- how did you set up your blog? what's interesting about your setup that you think would be a good recipe that other people would be interested in?
5. help us to figure out how to better manage the plugin and flavour registries

This isn't an ongoing initiative--we're looking to push 2.0 out by June 2008. Whatever gets changed/fixed by then is in. Whatever doesn't, will get deferred to another release.

Discuss issues on #pyblosxom on irc.freenode.net, the pyblosxom-devel mailing list and the discussion pages here.

Adding a specification

When adding a specification, make sure to add the tag:

 [[Category:Planning]]
 

somewhere and that puts it in the Planning category.

Other notes

Will lives in Somerville, MA and would like to put together one or two sprints to work through issues and implement code/tests/documentation. If you're interested in that, drop him an email at willhelm at users dot sourceforge dot net.

Articles in category "Planning"

There are 8 articles in this category.

A Archive access specification B Blog.ini config values

C Contributed Plugins E Entry level caching specification F Filelist and sorting specification

T Templates specification Tests U UTF8