Re: pyblosxom future (1.3/2.0)

On Mar 26, 2005, at 8:29 PM, will guaraldi wrote:

>
> Now that we've released 1.2, I'm thinking the future of PyBlosxom 
> involves the following big items:
>
> storage api refactoring
>
>    This involves fixing PyBlosxom so that it can handle other storage
>    mechanisms even if at a rudimentary level.  It's likely that we'll
>    only have file entries for the short term, but I figure we might
>    as well fix the storage api stuff while we're fixing things to
>    handle index caching which I think is very important and also fix
>    PyBlosxom to handle metadata files which include the entry mtime.

I think this one is important, but also harder than we think, since 
many plugins rely on the details of
the storage API.

>
> documentation
>
>    I'm still working on this.  The next step is to work on the
>    PyBlosxom architecture components and the "how to build a plugin"
>    content.  Additionally, now that we're in docbook, it'd be nice
>    to take advantage of docbook features like <note>...</note>,
>    <tip>...</tip> and various other things like that.  Indexes would
>    be really cool as well.
>
>    Ultimately, I think I'm going to remove the ReadMeForPlugins and
>    merge that into the manual.

Feel free to include content from the PyCon paper 
<http://www.python.org/pycon/2005/papers/64/> if that will help.

>
> flavours
>
>    It might be a good idea to fix some issues with PyBlosxom to ease
>    the building, sharing, and installing of flavour packs.  Reading
>    through some of the emails Russell has sent might lead to some
>    insights on this.  Though it should be noted that I think some
>    of his issues are less architecture issues and more documentation
>    issues.

I think that we can probably do documentation to improve things.  More 
major changes take us into the realm of being Blosxom incompatible.

>
> other things
>
>    Where do we want to take PyBlosxom from here?  Should we slow down
>    on the core and work on plugins?  Things like the isp plugin that
>    blosxom has--that'd be really useful to some people using PyBlosxom.

I think that we are doing pretty well on the core engine, at least if 
we address the list above.  After that, I think it would be good to 
invest more work in plugins.

>
>
> Whether it's 1.3 or 2.0 will be decided by how big a change the 
> storage api fixes cause in the overall api for PyBlosxom.
>
> I think that's all I can think of at the moment.  I'm going to push 
> hard on the storage api fixes for the next version as well as 
> documentation.
>
> I want to wait a few weeks for PyBlosxom 1.2 to settle in, though, in 
> case there are issues with it.
>
> Anyhow, I think we did a really good job with PyBlosxom 1.2 and I'm 
> pretty happy with how it turned out.  Thanks to Steven who probably 
> did the brunt of the CVS checkins for 1.2.  Thanks to Ted for doing 
> the presentation at PyCon (I'd love to hear how it turned out).  
> Thanks to everyone else (Bill, Wari, etc) for chiming in on big 
> issues!

The presentation went pretty well -- I was in the last block of 
sessions, and so the talks wasn't super well attended.  Most of the 
Google folks at PyCon were in the room, which was kind of weird, 
especially given that they own Blogger.   Afterwards a few people said 
that they had changes that they would try to send to the list, so we 
may pick up a few additional people...

>
> w00t!
>
> /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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Pyblosxom-devel mailing list
> Pyblosxom-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel
>
----
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