Re: pycon talk?

On Thu, 30 Dec 2004 00:42:42 -0800, Ted Leung <[email protected]> wrote:
> 
> On Dec 29, 2004, at 1:00 PM, Bill Mill wrote:
> 
> > On Wed, 29 Dec 2004 11:25:24 -0800, Ted Leung <[email protected]> wrote:
> >> Ok, the deadline is Friday, so if we're serious about a talk, we need
> >> to get moving.  Here's a first real cut at something we could submit.
> >> Please don't be bashful for suggestions about the intro paragraphs or
> >> the outline.   I want to be able to post this by mid afternoon Friday
> >> PST.
> >>
> >> Ted
> >>
> >> -----------------
> >> pyblosxom is a weblogging system written in Python.  It uses the
> >> filesystem storage model pioneered by blosxom, but has diverged in
> >> terms of internal architecture and organization.  pyblosxom takes a
> >> microkernel approach to blogging software by providing a small core
> >> framework that embodies the blogging data flow.  This framework
> >> provides a plugin mechanism that allows users to insert their own
> >> functionality at specific points during the data flow.
> >
> > Not sure about this (This framework...) sentence. How about something
> > like "Callbacks are placed at strategic points so that users may
> > override as much or as little of the framework's default functionality
> > as they desire."
> 
> ok
> 
> >
> >> This
> >> functionality can range from alternate page rendering to comments to
> >> calendar based archives.
> >
> > Maybe plugins should have their own paragraph? We can talk about the
> > wide range of plugins that already exist, the ease of development,
> > their flexibility, etc. Just a thought
> 
> Well, I'll certainly mention all that in the talk.  Not sure if we need
> to say
> all that in the proposal.

Sounds good to me.

> 
> >
> >>
> >> pyblosxom has a growing user base and a small, friendly development
> >> community.  Our goal for this presentation is to increase awareness of
> >> blogging in the Python community, provide an introduction to pyblosxom
> >> and its capabilities, and describe enough of the pyblosxom internals
> >> to
> >> attract additional developers to the community.
> >>
> >> The outline for this talk will be:
> >>
> >> * Introduction/Overview
> >> * Installing and Configuring Pyblosxom
> >>    * flavors
> >>    * plugins
> >>       * comments
> >>       * categories
> >>       * archives
> >>       * searching
> >>       * metaweblog
> >>       * caching
> >>       * conditional http
> >
> > Seems to me that the natural place to talk about plugins is after we
> > talk about the architecture of pyblosxom. That way, we can speak more
> > intelligently about them, and choose strategic examples of plugins
> > which demonstrate features we want to highlight.
> 
>  From a developer point of view, I agree.  But Installing and
> Configuring is
> aimed at helping people get started, which is why there are 2 sections
> on
> plugins, one for users, one for developers.
> 

Fair enough. I thought we would be speaking mainly to developers? And
isn't our platform useful mostly to people who are developers? I know
I wouldn't be using pyblosxom if I didn't hack python...

> >
> >> * Pyblosxom Architecture and Internals
> >> * Example plugin source code
> >
> > Maybe we could start with the word count plugin, which can be
> > implemented in just a few lines? I think that shows off the power of
> > pyblosxom nicely.
> 
> This sounds like a good idea.
> 
> >
> >>     * comments
> >>     * categories
> >>     * XMLRPC related plugins, xmlrpc_metaweblog
> >> * Future directions
> >
> > better internationalization, caching, mod_python integration, and
> > better static rendering come immediately to mind.
> 
> I intentionally left this vague, because some things may get done
> between now and then.
> 

True.

Peace
Bill Mill
bill.mill at gmail.com


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt