Re: quick thoughts on things

Let me also thank you for publicly posting this.  Let me also publicly 
thank you for the work that you've invested in pyblosxom.

Random hiccups like the CVS thing are bound to happen.  I think the 
important thing is that we be able to recover and move on.  I agree 
with Will that it will be healthier for the project for us to split 
things up amongst a number of people.

At the moment, we need to issue a plugins pack so that the Debian folks 
can use it.  I think that the contrib directory in the PYBLOSXOM_1_2 
branch is what we need for this, but we need to go through and make 
sure that we remove any plugins that we don't have a license for.   I 
would volunteer to get this release done, but I can't because I'm going 
to be travelling on business starting Sunday for a week, and I don't 
have enough cycles to do this between now and then.  If it can wait 
till I get back (4/25), I'll do it then.  If someone wants to step up 
and do it before that I think that would be great.

Ted

On Apr 13, 2005, at 7:48 AM, will guaraldi wrote:

>
> I was talking with Ted about some minor issues I found with the 
> comments plugin when upgrading to the latest version on my blog and I 
> figured I'd take the last email I sent him and turn it into a quick 
> thoughts on things email for the list.
>
> In regards to me stepping down, I think the problem was as much me as 
> anything else.  I was frustrated with the CVS situation (which after 
> reading the emails afterwards seems less daunting than I thought), but 
> that's development life and that's ok.  More importantly, I just had 
> too much on my plate and I was spending most of my time flipping 
> between items and not finishing any of them.
>
> I think this will end up being a really good thing because (I hope) 
> the maintainer duties I had put on my plate will end up split among a 
> bunch of people: documentation maintainer, web-site maintainer, 
> release maintainer, and possibly a project coordinator (or some other 
> distribution of tasks).
>
> While I'm not sure how I would have done things differently, I think I 
> screwed up by taking on all the things I took on instead of recruiting 
> other people to work on those tasks.  Stepping down kind of forces all 
> those tasks to distribute themselves among everyone else.  And on the 
> flip side, I was a self-appointed maintainer anyhow.  ;)
>
>
> The project has come a _huge_ distance from when I was writing blog 
> entries like this one:
>
>    http://www.bluesock.org/~willg/blog/dev/pyblosxom/whattodo.html
>
> That's as much my work as it is the work of everyone else here.  In 
> the near term, we're on track to solving some major user headaches 
> revolving around plugins and documentation.  Fixing issues there will 
> be a _huge_ win for the project.
>
> I figured I'd write this and get it into the archives as a closure 
> statement to clarify what the situation was like and the reasons I 
> stepped down.
>
> So, no worries.  PyBlosxom looks like roses in the near term and I 
> think PyBlosxom will be fine in the long term as well.

----
Ted Leung                          Blog: <http://www.sauria.com/blog>
PGP Fingerprint: 1003 7870 251F FA71 A59A  CEE3 BEBA 2B87 F5FC 4B42



-------------------------------------------------------
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