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

[D. R. H. <dr...@hw...>]

Jim Ingham wrote:
>
> 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 
>
> [...]

This all sounds good to me.  This is similar to
things I've done in the past that worked, and it
appears also to work for gcc/gdb.

Are there any counter-proposals?

To implement Jim's scheme, somebody with the right
privileges needs to take the following actions:

  1.  Create a c.l.t.patches newgroup OR a tclpatches
      mailing list OR a tcl patches database

  2.  Break the source tree into functional areas
      and assign a maintainer to each area.

  3.  Set up CVS so that maintainers can checkin
      at any time and that others can checkin
      with an appropriate approval cookie from the
      maintainer.

  4.  Figure out how to run CVS over SSH without
      also given people a login and set up the
      CVS server accordingly.

  5.  Collect SSH keys from the maintainers, etc.

  6.  Document the above so that people can use
      the system.

Clearly, it would be much easier for me to just
send the patches to Jeff than to worry through all
of the above.  But perhaps it is worth the trouble
to walk through the above, just to get things moving.

Assuming we move forward with this (a big
assumption, I know) who will do all of the above
for us?  My guess is that the set of people with
the right privileges is limited to Jeff and Brent.
Unless we move the source tree out to SourceForge
or something.

Thoughts?  Volunteers?

If we decide to do something like this, I'll help
help with the documentation in item (6).
-- 
D. Richard Hipp -- dr...@hw... -- http://www.hwaci.com/drh/

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