Re: Re: pybloxsom (fwd)

You're right, Bill--it sounds like we're on the same page, though I'd like 
to further clarify subsection 5 of the previous RFE to the development 
process as it applies to CVS version control.  (kidding)

But seriously, I think there's one minor point that I want to clarify.  I 
think people should prototype things before they send out a spec that 
everyone then discusses.  After the spec (which should specify the purpose 
of the changes, what changes should be made, and what possible issues may 
come out of those changes), is discussed and everyone is on board, then 
the developer should just start checking stuff in.  At that point everyone 
knows where the potential points of conflict should be between that 
developer's work and other developers' work, so we should be fine.  If 
it's overly complicated, maybe we should spin it off into a branch.  Or 
in the case of refactoring everything, maybe we should spin it off into 
its own CVS module.  (shrug)  We can figure stuff like that out when we're 
discussing the spec.

In regards to your index caching, you were storing things globally which 
won't work with the frameworks.  At least, I'm pretty sure that's where we 
left the issue.  Then we decided that after 1.2 we were going to fix the 
storage api which would account for most of your changes and allow for 
plugins that handle the actual index caching.  That's what I thought we 
decided after looking at the code changes you had.  So while you're right 
in that you're now sitting on a bunch of code and you may not remember 
what you changed or why, I'm not sure it really matters in the grand 
scheme of things because we decided to go in a different direction than 
the one you took.

I don't want to create a bunch of processes.  I do want everyone to be on 
the same page in regards to how we develop PyBlosxom.  The more consistent 
things are amongst all of us, the easier it is for other people to follow 
what's going on.  Blah blah blah.

So, given that, I think I'd rather Doug prototype on his own, write the 
spec, then we can discuss it from there.  I have no idea why Steven 
created his own branch for the minor WSGI fixes he's doing which I think 
should be in CVS HEAD....  Steven?

Going forward, we should figure out how we want to deal with things on a 
case by case basis.

/will


-------------------------------------------------------
This SF.net email is sponsored by Demarc:
A global provider of Threat Management Solutions.
Download our HomeAdmin security software for free today!
http://www.demarc.com/Info/Sentarus/hamr30