Re: Re: pybloxsom (fwd)

> 4. Here's a strawman process for big changes (small ones can probably
> go into head)
> 
>      a. discuss proposed changes in e-mail
>      b. work on changes (in a branch?)
>      c. when changes are done, ask people to review (the branch or a
> patch)
>      d. have a vote on whether the changes should be checked in or not
> (specify a time frame when the checkin will occur)
> 
> The open question is whether we have enough CVS-fu to make working on
> branches practical or whether we want to investigate some other
> solution.
> 

That is a fairly complete summary, in a few lines, of what I took a
whole huge email to write confusingly. Thanks a lot for that - and
obviously I agree.

As to whether we want to investigate another solution, I'm currently
paying for subversion hosting. I would be glad to set up a pyblosxom
repository, but I'm not sure how to properly handle backups and other
admin tasks. Maybe we could just keep experimental branches on my
server?

Peace
Bill Mill
bill.mill at gmail.com


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