Re: [Pyblosxom-devel] new issue tracker

[Marius G. <ma...@ge...>]

On Sat, Jan 08, 2011 at 12:18:34PM -0500, will kahn-greene wrote:
> I haven't heard anything from anyone except for Tim.  I (manually)
> copied the bugs over from SF and closed two of them.  Other than that,
> no one has added any new bugs or continued this thread.

Yes, well, you know how it is.

My blog is running on 1.4.something as packaged in Ubuntu, with lots of
tweaks in the plugins to make it work with my configuration.  Given the
amount of breakage I've had to manually fix, I'm reluctant to upgrade
without first writing a test suite for my blog.  And I'm unsure how to
start with that -- WebTest?  Twill?  Selenium?

Also, I don't see any compelling benefits of upgrading, other than the
ability to test latest code and contribute plugin fixes back...  And I'm
not convinced that people are interested in my fixes and enhancements --
my emails on that topic back in 2009 never received any response, and my
last attempted plugin contribution was answered by "why do people even
care about this?".

So that perhaps explains my lack of enthusiasm.

> Is this not the system you were hoping for?  Have the fires of PyBlosxom
> development cooled so much due to my ridiculous amount of bottlenecking
> and business?

Hey, I've seen worse-run open-source projects.  I myself run some of
them, with patches languishing in my inbox for _years_ when I was
suffering from burnout.

I'm happy to see new activity with the website, documentation (Sphinx
rules), Git repositories, bug trackers.

Marius Gedminas
-- 
Life was simple before World War II. After that, we had systems.
        -- Grace Murray Hopper, 1987