my role

I _really_ wish we hadn't started screwing with CVS until we had a policy 
in place that we all agreed on.

My understanding was that 1.2 was in maintenance mode and thus all 1.2 
work would be in the PYBLOSXOM_1_2 branch and not in HEAD.  We're also 
working on new code for the next release of PyBlosxom.  That new code is 
in HEAD or any one of a dozen other branches depending on who's working on 
what.  After reading the last few emails, it seems we're all on different 
pages in regards to CVS usage.

I had wanted to put out a contributed plugins pack update for PyBlosxom 
1.2 today, but I don't know what's going on.


I don't want to be the maintainer of this project any more.  I've said as 
much over the last 6 months, but I felt that the project needed a strong 
driver that could establish an infrastructure that would allow the project 
to mature and continue growing.  So I figured I'd stick around for that 
and help push that through.

But this CVS situation fucking sucks and I don't have time to figure out 
what's going on in order to do the things we need to do, like release a 
contributed plugins pack for PyBlosxom 1.2 with the changes that the 
Debian folks need and various other updates that have happened over the 
last week.

I'm frustrated which is fine--that's the way things go sometimes.  But I 
don't have the time or inclination to deal with this.


As such, I'm dropping back to being an occasional PyBlosxom contributer. 
I'll hang out on the mailing lists, but I'm not doing any more maintainer 
duties.

When you guys figure out who's going to be the next maintainer, I'll 
happily help that person out with everything I know in regards to this 
project.

/will


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click