Re: pyblosxom.sourceforge.net

On Wed, 22 Dec 2004, Ben Finney wrote:
>
> Thanks for your efforts on the site, it looks good.  Thanks especially 
> for *not* delaying its release, waiting for perfection -- in this form 
> it's already very useful.

Everything on the site with the exception of the development howto has 
been culled from PlanetPyBlosxom and all the work Wari, Ted, LionKimbro 
and others have done in the PyBlosxom wiki on the RoughingIt site.  So 
that's helped a huge amount in bootstrapping the site.


>> There are still a few things that need to be done--I'll be getting to 
>> them over time.  If anyone wants to help out, let me know.  Most of it 
>> involves writing sections of the PyBlosxom manual.
>
> Does "writing" here involve creating content, or transcribing from other 
> places?  I don't yet use PyBlosxom, but want to, and am willing to put 
> effort in to see that it thrives.

Well, I'm not wholly sure.  Right now I'm skimming the wiki and pulling 
content out and stuffing it in the manual with a bunch of re-writing.  I'm 
re-writing things to make the manual more organized, comprehensive, and 
accurate.

In the process of doing this, I'm discovering some gaps in the content. 
So I'm filling those as I go along.


> What can those of us without specific knowledge about PyBlosxom do to 
> help the site?

Mmm...  Well, the best thing you can do is review what's been written, 
check it for accuracy, and see what questions it leaves unanswered.  Then 
you can either post a comment on that specific manual chapter (assuming 
that works--I haven't tested it yet) or you could send an email to me.

I expect the manual to be pretty basic right now and not comprehensive. 
As time goes on, I'm hoping to add to the manual (either content I've 
written or other people have written) to reflect use cases and problems 
people have.  Things like "how can I run PyBlosxom in an ISP fashion". 
I'd bet there are a bunch of folks who are interested in that and some 
folks have already solved that problem probably using a couple of 
different methods.

So on and so forth.  My next step for the manual is to check it into CVS. 
That way anyone with CVS checkin access can checkin fixes.  Additionally, 
anyone else, can use the anonymous CVS access, get the actual code for the 
manual, and send in diffs to fix things.

The manual is currently written in HTML using my pystaticfile plugin--so 
it's got blocks of Python code in it to render things like tables more 
easily.  I tossed around using another format like docbook or wiki or 
reST, but I just couldn't muster up the energy to go deal with the bizarre 
formatting issues that all of these formats have.

Getting there...

/will

-- 
whatever it is, you can find it at http://www.bluesock.org/~willg/
except Will--you can only see him in real life.


-------------------------------------------------------
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://productguide.itmanagersjournal.com/