Re: quick thoughts on things

On 04/13/05 16:48, 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.
> 
> /will
> 

I'm glad you posted this to the list. I had sort of a weird feeling
after your post about stepping down as the maintainer and beeing
frustrated and all.

Regarding distributing tasks I guess I could take the job of the
website-maintainer, as that's an area where I'm pretty experienced and
have been working in for years.

I've also started writing up some documention on how to use Pyblosxom
with wsgi/mod_python/twisted. I hope to get that finished by the end of
the week or so.

The plugin registry rewrite is also slowly starting to look like
something. Major differences to the current solution beeing that plugins
can be uploaded and are stored/managed in CVS.

A question to Will on this: Is the website hosted on the same server as
our CVS repo? Do I have local access (without pserver/ssh) to the repo
from a CGI/Pyblosxom which runs on the project website? If not, can we
create an account for this? I don't want to put my own username/password
in a script on the server.

A question to all:
I have a few fixes/enchancements to the logging system which I'ld like
to check in. So, where do I put my new code? Should it be HEAD or DEVEL?
I don't really care, but we need to decide how we handle this, the
sooner the better.

cheers
Steven




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