Re: filestat - a different perspective

That's the "main" todo list.

   http://wiki.subtlehints.net/moin/PyBlosxomToDo

In regards to the "new release", I haven't figured out whether we should
release what we have (there are a few fixes in CVS that are probably worth
using for people) or wait until we solve some more fundamental problems.

I don't really want to release a bugfix release, get a bunch more people
to go try it out, and then go through another bunch of discussions on the
problems with pyblosxom via the mailing list and blogspace.  So...  we
can do a 1.0.1 release whenever we want to.  The todo list on the wiki is
a list of things people have requested someone else do.

Going to mission stuff, PyBlosxom is not a fork of blosxom.  But PyBlosxom
is defined as "blosxom with a touch of python".  Everyone has an opinion
on whether that should or should not be the mission.  Most of the *osxoms
share a series of fundamental features with blosxom and then have a few
features of their own.  I see PyBlosxom like that as well.

/will


On Fri, 20 Aug 2004, Christopher Baus wrote:

> I just found pyblosxum, which by coincidence happened to be at about the
> same time Will posted to his blog about not having enough help with the
> project.
>
> I've been doing Unix stuff for about 10 years.  I have been looking for
> a publishing system that is flexible and hackable.  I'm not afriad of
> editing config files directly.  I've used MT for a while, and I have to
> admit I'm not happy with the model.  They are geared toward LCD end
> users= , which is fine, its just not for me. Also, I'm not hacking on
> someone else's commercial product for free.
>
> > LiveJournal.  I see PyBlosxom's audience as other
> > developers/hackers--people who just want a framework to build off of.
>
> Sounds good to me.
>
> > And I also realize gearing things towards hacker-types doesn't
> > necessarily get us out of the business of making things work better
> > out of the box.
>
> Totally agree.
>
> The question I have is how important is backward compatibility of blosxom
> features?  In my opinion I think pyblosxom isn't the best name.  It makes
> it sound like a will be compatible with blosxom.  If I'm going to provide
> patches to the framework, I don't want to be limited by that constraint.
>
> PyBlosxom isn't just a fork of blosxum, which would make staying in
> feature parity difficult but doable, it is a complete rewrite in another
> language.  One that I find far more productive than say Perl.  Staying in
> feature parity with blosxum is going to be very difficult, and may not be
> the best use of hackers' time.
>
> Will, in your blog posts you discuss getting a new release out.  Do you
> have a list of exactly what needs to be done.  I've found that the best
> way to approach something that seems overwhelming is to just break it dow=
> n
> into small milestones, and attack them one at a time.  Fortunately in the
> FOSS world the attack can be multi-fronted.
>
>

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


-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285