Re: pybloxsom (fwd)

Doug wants to prototype the testing stuff he's working on in our 
repository.  Additionally, Steven seems to be using more "advanced" 
features of CVS.

My problems with this are three-fold:

  1. I don't know enough CVS administration to really follow what's
     going on, or fix it if it goes bad.  I don't know if anyone
     on our team knows enough CVS administration to fix things if
     they go bad.

  2. It is causing a lot of checkin email that I'm not really
     following.  I use the checkin email to keep track of things and
     as a poor-man's peer review queue.

  3. It seems people are communicating less and prototyping more.  I'd
     really like to discuss things before they start getting checked
     in and moved around.  Additionally, we have a small code-base and
     communicating with eachother will help a lot when people are
     making changes to the same pieces of code.


Here's why I keep talking about me.  I have no idea how dedicated you guys 
are to this project.  We've had developers come, do some stuff, and then 
disappear off the face of the earth.  That's fine and is 
expected--peoples' lives change and this is an open source project. 
However, the remaining people can't be left with a bunch of stuff they 
don't know how to deal with.  Additionally, I don't plan to work on this 
project for the rest of my life either.  I want to leave the project in a 
state where it has a lot of momentum and new people can come in, 
familiarize themselves with things, and help out.

Anyhow, so that's where I'm coming from.  I don't really have time to go 
become a master of CVS right now, so that's not really an option for me. 
If someone in the group is very proficient with CVS administration and can 
promise that they're going to be around, then I'm fine with depending on 
that person to deal with CVS.

Additionally, we do have some standards and I'd like to add to them as the 
team gets bigger so that we're all on the same page and the process of 
what we're doing is documented.  Currently that documentation resides at:

    http://pyblosxom.sourceforge.net/blog/static/development

Incidentally, it includes information on how to format your doc-strings so 
that they get picked up by EpyDoc for the API documentation.


Right...  so going back to Doug's issues, I'm not sure what to do.  I'd 
prefer he prototyped in his own repository, but if you guys can work out a 
way for him to do what he needs to do and it's better that he does it in a 
central place available to all of us, I'm ok with changing my stance.

Additionally, if communicating by mailing list doesn't work for you guys, 
what better ways can we make sure we're all in the loop?  Email works best 
for me because it's asynchronous.

Thoughts?

/will


---------- Forwarded message ----------
Date: Thu, 31 Mar 2005 07:28:13 -0800
From: Doug Ransom <doug.ransom-cmaem7PIVQRoiclzN/[email protected]>
To: will guaraldi <[email protected]>
Subject: Re: pybloxsom

Ok, I'll check nothing in on the prototypes.  The system we use at work, 
perforce, is pretty amazing for supporting this type of activity, but I am 
guesssing CVS is pretty bare bones.  I'll have to learn it.

Doug

will guaraldi wrote:
> 
> Uhh...  I thought the plan was that you were going to prototype bits of 
> it on your own and then write up a specification of what the issues 
> involved are and what architectural changes would need to be made.
> 
> I don't know enough about CVS and I'm not sure anyone else does either 
> to deal with forking and such.  I have no idea if it's trivial or not.
> 
> /will
> 
> 
> On Wed, 30 Mar 2005, Doug Ransom wrote:
> 
>> 
>> Thanks.
>> 
>> Is it ok to create a "fork" or "sandbox" in CVS for a prototype?  We use 
>> perforce at work, which makes this trivial.
>> 
>> Doug


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