[TCLCORE] Re: Fwd: [TCT] Welcome...

[Jim I. <ji...@ap...>]

Jeffrey,

Here is a copy of this message that I sent to the TCT mailing list.  It is better in this forum, I think.

I really think that having a staged checkin process like the one I describe for gdb & gcc is a good idea, mostly because it makes it much easier for everybody in the community to know what is going on - CVS mail is a pain, since you then have to go dig out the changes, and it is too easy to let stuff just fly past unnoticed.  We have done this for gcc & gdb for a while, and it does not seem an onerous burden.

Jim

Begin forwarded message:

> From: Jim Ingham <ji...@ap...> 
> Date: Mon, 28 Aug 2000 15:14:50 -0700 
> To: "D. Richard Hipp" <dr...@hw...> 
> Cc: TCT Mailing List <tc...@aj...> 
> Subject: Re: [TCT] Re: Welcome... 
> X-Mailer: Apple Mail (2.333) 
>  
>  
> Hi, Richard... 
>  
> I think that patches should in general be staged, and posted publically before they are 
> committed.  I also think that we need to set up some light-weight peer review scheme as 
> well. 
>  
> Here is the way that it works for gdb & gcc, and I think this is a pretty good method 
>  
> 1)  ALL patches should first be sent to some patches address (either 
> comp.lang.tcl.patches, or c.l.t with some special tag for patches, or to the bug 
> database - we have to decide which is easiest).  This provides easy archiving, and raises 
> visibility for all changes.  It also puts patches from the Core team and external 
> contributors on an equal footing, which is a salutary thing. 
>  
> 2) The sources are broken up into functional areas, and each functional area has a 
> maintainer & a backup maintainer(s).   These are listed in a MAINTAINERS file in the 
> sources.   
>  
> 3) The maintainer can check in changes to his or her area at the same time as posting the 
> patches notice. 
>  
> 4) Other people can be granted "checkin after approval" privileges - presumably all the 
> TCT will all have this privilege, but it can be extended to people who have expertise in 
> more limited areas, for their area.  These people can check in the code once they have been 
> given the OK.   
>  
> It is the duty of the maintainers to be timely in their replies, and that is also why it is a 
> good idea to have a backup. 
>  
> 5) It is also the responsibility of the maintainer to check in the patches from other 
> people (without checkin after approval privileges). 
>  
> 6) As to mechanics, it is probably easiest to use SSH to obtain write access.  CVS works 
> pretty well with SSH, and it is easy to mail the CVS maintainer your SSH key.  Kerboros 
> would be another alternative, but I think that it is harder to set up.  Anyway, we use SSH at 
> Cygnus for the sourceware repositories, and it was quite easy to setup and administer. 
>  
> Jim 
>  
>  
> On Monday, August 28, 2000, at 01:40 PM, D. Richard Hipp wrote: 
>  
> > I am deeply honored to be a part of the Tcl Core team  
> > and I look forward to contributing to this effort in   
> > the weeks and months ahead.  
> >   
> > For now:  
> >   
> > I have in hand a patch to Tk8.4 that fixes a X11  
> > "BadMatch" error.  It used to be that I would send  
> > such patches to Jeff and they would get into the   
> > next release.  But I'm thinking it sure would be   
> > a lot easier (for me and Jeff both) to just do a  
> > "cvs commit"....  
> >   
> > What are the procedures for writing to the CVS  
> > repository?  How are updates coordinated to prevent  
> > someone from committing an unstable change right   
> > before an important release, for example?  Is there  
> > any kind of peer review of changes?  How to we get  
> > turned on for write access to the CVS repository?  
> >   
> > Are these reasonable questions, or am I way ahead of  
> > myself?  
> > --   
> > D. Richard Hipp -- dr...@hw... -- http://www.hwaci.com/drh/  
> >   
> > --  
> > This is the Tcl Core Team (TCT) mailing list.  
> > To subscribe:    send mail to tct...@aj... with the   
> >                  word SUBSCRIBE as the subject.  
> > To unsubscribe:  send mail to tct...@aj... with the   
> >                  word UNSUBSCRIBE as the subject.  
> > To send to the list, send email to 'tc...@aj...'.   
> > Currently there is no publically viewable list archive.  
> >   
> > Note: an @scriptics.com email will work also, and we plan to move  
> > this to @tcltk.org as quickly as possible.  
> >   
> >   
>  
> -- 
> Jim Ingham                                   ji...@ap... 
> Developer Tools - gdb 
> Apple Computer 

--
Jim Ingham                                   ji...@ap...
Developer Tools - gdb
Apple Computer

--
The TclCore mailing list is sponsored by Ajuba Solutions
To unsubscribe:  email tcl...@aj... with the 
                 word UNSUBSCRIBE as the subject.