pyblosxom 3000

Hey all,

Well, now that pyblosxom 1.1 is out the door, we should be revving up
to change big stuff while we have a new branch. As far as I see it,
and in no particular order, here are things that are waiting to be
done:

1) Caching - we should make infrastructure to assist with caching. My
latest patch (which I haven't looked at in about a month - may not
still be valid) is available at
http://llimllib.f2o.org/files/cache.tar.gz , and is described in a
previous email to this list
(http://sourceforge.net/mailarchive/message.php?msg_id=10236127)

The big question for me is still this: how and when should the cache
be refreshed? Anybody have any ideas?

Any other suggestions about this will be appreciated. Ted, how have
you gotten along with the patch? are you still using it?

2) Internationalization - it's on my list, but it's low. I write in
english, and my blog seems to magically handle unicode in comments
pretty well. Somebody want to volunteer to work on internationalizing
pyblosxom?

Basically, from what I understand, we should be converting any ASCII
strings we have to unicode as soon as we get them. I'm an idiot on
this though, so if somebody else wants to do it, go on ahead.

3) Unit tests - I've never written unit tests, nor do I know how one
would test such an application as pyblosxom. Anyone want to step up?

4) Contrib stuff - Will's still asking for a contrib maintainer. I
can't reliably concentrate on anything for more than 5 minutes, so I
don't want to volunteer. Anyone?

5) Comment Administrator - I have one that works, more or less, except
it can't change the dates on comments. This is because I want to
change the comments module to use the date field inside the comments
file instead of the time embedded in the filename.

6) Static Rendering - I said I would take this one up, but it's
slipped way down on my list. Anybody interested? Anybody using this
feature right now? (Roberto?)

We pretty much need someone to clean this up and document it, as I see it.

7) mod_python / WSGI integration - Didn't somebody submit a patch/some
patches that do this? Are we going to try and integrate it for 1.2? I
think it's a good idea.

A quick search shows
http://sourceforge.net/mailarchive/message.php?msg_id=10250388 .
Steven, you still hanging around here? Want to step up for the effort
to patch it in?

I'd like to start running this on my personal blog.

8) refactoring - There are some really ugly functions in pyblosxom.py
that could use refactoring. Especially blosxom_file_list_handler
(which sets some magic undocumented variables in the Request['data']
array to work) and blosxom_process_path_info (which is just pretty
awkward).

9) documentation - This is getting better (excellent work will), but
always needs to be maintained. The new website is the hottness.

hmmm....that's all I got for now. Anybody else got suggestions?
Anybody want to sign on the dotted line?

Peace
Bill Mill
[email protected]


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt