Re: Re: pybloxsom (fwd)

On 03/31/05 18:08, will guaraldi wrote:
> 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.
> 

I'm currently writing a short how-to for the "advanced" CVS features I
think we should use, namely versioning and branching. I'll post it
within a hour or so.

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

I've created a branch 'kaidon' (which is my sourceforge username) to
test some stuff which I didn't want to commit to HEAD. I also wanted to
see if the branching stuff I use in my own repo works the same for
sourceforge. The emails you've seen where commits to that branch.

Please accept my apologies for just doing this without comunicating it
first. Didn't think that it's a problem as it doesn't affect the main
source branch or hurt the project in some way. I do understand your
concerns of the CVS becomming a mess though, so I'll be more thoughtfull
in the future.

If we decide to use the branching features it might be a good idea to
only generate checkin-emails for CVS head and the branches that are used
to fix bugs in releases if that's possible.
Do you have any control how and when checkin-emails are generated?

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

I don't think the versioning and branching stuff is that complicated. I
also think that knowlegde in this sector is always a + and generally
makes a developers life easier in the long term. This offcourse is just
my point of view.

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

I think it'ld be better to have Doug's work in the main repo. Like this
others can have a peak at it or help solve problems. If he does this in
CVS HEAD or his own development branch has to be discussed. Not sure
what would be better. I do think that CVS HEAD should always be in a
working state though.

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

ditto


cheers
Steven


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