contributed plugins

The recent emails from Lance and Michael are related to the issue of 
maintaining and organizing plugins that are related to a specific 
version of PyBlosxom.  I talked with Ryan about this a week or two ago 
and that resulted in this half-finished proposal:

    http://pyblosxom.sourceforge.net/wiki/index.php/Contributed_Plugins

Given that we're experiencing some of the issues right now, I'd like to 
get input from anyone who can render it on the following questions:

1) Does the proposal adequately describe all the problems we're having 
with managing plugins in the PyBlosxom universe?

2) Are there better solutions that minimize the efforts of specific 
people (i.e. me and Ryan) and maximize solving of the issues involved?

3) Any other thoughts on the proposal?

The changes described are pretty easy to do--I think I could do them in 
a half day of work.  If the proposal is kosher and more than one or two 
people give it a stamp of approval, I'd be interested in pushing through 
it in the next couple of days.  This would alleviate some of the 
problems we're incurring regarding 2.0 development breaking APIs and 
being generally unstable.

/will

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/