[TCLCORE] Re: [TCLCORE] Re: [TCLCORE] Words to consider...

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

Also sprach Scott Stanton:

> 
> Jim Ingham said:
>> Gcc,
>> (starting with the egcs fork) put a lot of effort into setting up a
> steering
>> committee that contained both developers and users, and was not
> dominated by
>> any one interest.  Then they maintain a parallel, technical review
> structure
>> that maintains code quality through a system of area maintainers and
> careful
>> submission & review practices to assure that (a) submitted code is in
> line
>> both with the gcc design principles, and future goals and (b) the
> knowledge
>> of same are transmitted from one generation of gcc hackers to the next.
>> They have also documented these practices clearly, with Hack rules and
> well
>> defined maintainers lists, and supported them with a nice CVS
> repository,
>> and mailing lists for patches and general discussion...
> 
> Are these documents readily available somewhere?  It seems like they'd
> make for interesting reading as we try to set up similar structures for
> Tcl development.
> 

First off, you should have a look at gcc.gnu.org, which is the official
version of the old cygnus egcs site.  They have some nice stuff there.  The
Maintainers list and the hack rules are in the gcc sources.

Also, it might be good to contact the egcs folks - maybe Jeff Law would be a
good person to try, or Jim Wilson.  They are pretty dedicated to open source
development, and also have had a lot of experience both with the more closed
development of the old gcc, and with setting up a more open community in the
face of this other development model.  If you had some idea of what you
wanted to do, they would probably be willing to give you some good feedback
on it.  I know in particular that Jeff is not shy of expressing his
opinions, and he is a good guy to talk with.

Jim
-- 
Jim Ingham                                 ji...@ap...
Apple Computer

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