Re: [pyblosxom-users] Flavours and templates

[will kahn-g. <wi...@bl...>]

On 01/31/2010 05:04 AM, Chris G wrote:
>
> A working example (for me at least) is worth a thousand words of
> documentation, if one could just install one of the flavours, do what
> it says in its README file and have a working flavour that really
> would be all that's necessary I think (at least I'd have had less
> trouble!).

The default flavours that get put in your flavourdir when you run:

     pyblosxom-cmd create <path-to-blog>

should provide the best examples because they come with PyBlosxom 1.5.

It's possible that the bug you ran into last week with "pyblosxom-cmd 
create ..." also didn't copy over the flavour files, so you might not 
have seen them yet.  That's fixed now.

I'll try to get to updating the flavour packs soon.  In the meantime, 
would it be better to remove them until I get the time to spend on them?


> I'm quite happy to put some time into doing minor fixes to the
> flavours and adding to/changing the README files.

I'm seriously thinking about organizing a PyBlosxom documentation sprint 
this week.  I'd probably organize it something along these lines:

1. create a bunch of PiratePad pads--one per chapter that needs work in 
the manual

2. send a list of chapter -> PiratePad URLs to the develop list

3. anyone who wants to work on a chapter goes to the URL for that 
chapter and starts typing

4. at the end of next week, I'd go through the changes, edit them, and 
pull them into svn

Does that sound interesting to anyone?  It alleviates the pain of not 
having svn checkin access and seriously lowers the barriers to entry for 
helping with the documentation.


> ... and thank you Will for continuing to maintain pyblosxom and
> listening to my ramblings patiently.  :-)

Thank you for taking an interest and all the help you've been!

I do want to apologize for being overly curt and rude.  I went through 
all the replies I've sent over the last couple of weeks and there are 
several places I didn't communicate very effectively.  I work for PCF on 
Miro as my day job and we're pushing hard for a release right now.  So 
I'm managing two big releases of software projects at the same time and 
I haven't been spending as much time on replies as I should be.

/will