Re: CVS for Cfengine (Was: Re: Bugzille for cfengine)

[John Sechrest]

Thanks for the note. I certainly agree that CVS access is a vital
step forward. 

I certainly can aim for that.

The key question is CVS vs subversion. Which you have already 
seen the beginning of that discussion.

I am still waiting on the approval from sourceforge for the 
site.

I will then work on the next step. 

If the subversion discussion moves forward, it will translate to 
a non-sourceforge service on a machine in norway. And I assume
mark will tell me what he wants me to do with that.

In the mean time, I will work to get CVS and other sourceforge
material up to allow us to delete/depopulate the cfengine
pages on savannah.

I will be out of reach of the next work for the last two weeks 
of the month, so I may not get CVS up until early january,
depending on the approval date.




Eric Sorenson <address@hidden> writes:

 % On Tue, 14 Dec 2004, John Sechrest wrote:
 % 
 % > It would be good to have a stronger idea of who wants to
 % > engage in coding. And what the process for getting
 % > things into the archive should be.
 % >
 % > My expectation is that a small number of people will take on the
 % > developer role and that others will decide to take on a supporting
 % > role for submitting patches. But I could be way off. My current
 % > plan is to move slowly to set up the system. My intent was to
 % > set up CVS, because it was supported by Sourceforge.
 % 
 % John -- there are many points worthy of discussion in this and
 % subsequent emails, but I wanted to focus on this comment. I would
 % argue that, rather than move slowly to get everything planned and
 % set up before going "live" on sourceforge, we ought to move quickly
 % to get one critical piece working, and let the rest of it fall into
 % place "as slowly as possible; as fast as necessary".
 % 
 % Specifically, I would very much like to see the cfengine project
 % CVS tree on sourceforge populated and *written to by Mark* as quickly
 % as is reasonable, perhaps before the end of the year. Everything
 % else -- mailing lists, bug tracking, developer access, *everything*
 % is secondary to this. If that is the only change that happens to
 % the cfengine development process, and nobody else ever ends up 
 % getting write access, that would be fine with me. But I plead to
 % both you and Mark, please work to make this happen ASAP.
 % 
 % Over-dramatic? Maybe. But I broke 1200 production machines for several days
 % last week (due to the 'cfagent -Q' splaytime behavior), and I really think it
 % would not have happened if we had a systematic way of comparing code changes
 % and commit logs between cfengine releases. You setting up the CVS and
 % Mark writing to it is a very small, incremental step that nets huge wins
 % for everyone out in the trenches relying on cfengine every day.
 % 
 % -- 
 % 
 %   - Eric Sorenson - Explosive Networking - http://eric.explosive.net -

-----
John Sechrest          .         Helping people use
                        .           computers and the Internet
                          .            more effectively
                             .                      
                                 .       Internet: address@hidden
                                      .   
                                              . http://www.peak.org/~sechrest