Re: trac and pyblosxom

On Thu, 30 Sep 2004, Aslak Raanes wrote:
>
> One idé would be to use trac (the issuetracker, not the language), for 
> as a bugtracker/wiki for pyblosxom? Maybe some time after the pyblosxom 
> 1.1 release?

Well, here's my thinking.  At some point p, the SourceForge staff will 
finally get around to upgrading Python on their web-servers.  When they 
(finally) do that (and I've been waiting for a couple of years now), I'm 
planning to move the planetpyblosxom.org site there and (with Wari's 
permission) unify PlanetPyBlosxom with the PyBlosxom main site.

If/when that happens, I'd like to unify that with a (better) 
bug/idea-tracking system and so on so forth.

So then we end up with one unified site for registered plugins, pyblosxom 
development, flavour plugins, documentation, and information about the 
pyblosxom project as a whole.  A one-stop shop for everything PyBlosxom.

And then maybe we'll just keep on going and end war, solve world hunger, 
and buy everyone in the world a beer.

It's a little dream I have.  And it all starts when SourceForge finally 
updates Python on their web-servers.  The last thing I hear from them, 
they said they're going to upgrade the Linux distro that their web-servers 
are based on.  I don't know what that means in regards to Python as they 
didn't mention Python specifically.

Anyhow....  Trac is a possibility.  I'm not sure what it really buys us, 
though.  I think we can do everything we're doing right now with PyBlosxom 
as a series of plugins off of PyBlosxom.

/will