RE: An HTML Entry Parser

> Everyone will have different needs.  Right now we have two
> different places to look for plugins and two different
> development methodologies for those plugins.  The last
> thing I want to deal with is having people send in bug-
> reports and such for plugins that go included in the code-
> base but were written by someone else.  I'd rather they
> contacted the plugin author to make the changes.

As a (somewhat lapsed) developer, I've been on a bit of a
reduction kick myself these past couple of days.  I'm
currently leaning towards removing all the plugins from
the main distribution, but making it very easy for people
to get any plugins they might want.  Perhaps even have a
couple of sets of plugins (beginner/intermediate/advanced)
with links in the README, so that people can get the basic
blog up and running, and then add in the functionality that
they think they'll use with a single mouse-click.  (Uh, and
an unzipping into a directory, I guess.)

Later,
Blake.



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf