Re: Re: pybloxsom (fwd)

>
> 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?

this sounds ok - I can start with a prototype that can potentially be 
tossed just to prove the idea out. 

At work, we create "sandboxes" all the time, do any risky work, then 
integrate back if we want.  But we have a great tool, perforce, for this.  

It doesn't sound like anyone is comfortable doing this in CVS yet, and I 
don't want to be the guinea pig as I haven't used CVS.

Doug

>
> 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
> _______________________________________________
> Pyblosxom-devel mailing list
> Pyblosxom-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel
>
>



-------------------------------------------------------
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