Updated 2016-04-14 13:04:32 by jannijtmans

The Tcl Core Team, or TCT, is the august body elected to direct the development of the Tcl Core in the summer of 2000.

See Also  edit

Tcl/Tk Core Development
The Tcl Core
the C reference implementation of Tcl
source code repositories
Tcl Improvement Proposal
describes the process by which changes to Tcl and Tk are introduced, accepted, and documented.

Documentation  edit

TIP 0, Tcl Core Team Basic Rules
mailing list archive, or TCLCORE

Projects  edit


Members  edit

Jos Decoster mailto:[email protected]
Mo Dejong mailto:[email protected]
Joe English mailto:[email protected]
Donal Fellows mailto:[email protected]
Alexandre Ferrieux mailto:[email protected]
Brian Griffin mailto:[email protected]
Jeffrey Hobbs mailto:[email protected]
Kevin Kenny mailto:[email protected]
Andreas Kupries mailto:[email protected]
Steve Landers mailto:[email protected]
Jan Nijtmans mailto:[email protected]
Donald Porter mailto:[email protected]
Miguel Sofer mailto:[email protected]
François Vogel mailto:[email protected]

There are some respected former members who resigned due to lack of personal time.
Mark Harrison mailto:[email protected]
D. Richard Hipp mailto:[email protected]
George Howlett mailto:[email protected]
Jim Ingham mailto:[email protected]
Karl Lehenbauer mailto:[email protected]
Michael McLennan mailto:[email protected]
John Ousterhout mailto:[email protected]
Daniel Steffen mailto:[email protected]
Brent Welch mailto:[email protected]

Description  edit

In accordance with TIP 0, Tcl Core Team Basic Rules, the TCT invites new members based on an assesment of an individual's code and leadership contributions to Tcl. The TCT relies heavily on community resources to maintain the other components of the Tcl ecosystem that are vital to keeping the entire project healthy and vibrant. If you appreciate Tcl and want to get involved, you are welcome! Apart from the Core Team, there are numerous opportunities for others to maintain important Tcl resources and nurture the community, and to have a strong influence over the future direction of Tcl.

The TCT has a long-standing policy of wanting to enable people to do cool stuff and not getting unduly in the way of those who do the work. We're particularly keen on enabling people to do cool stuff without having to change Tcl. The very very high engineering standards that are applied to the core, especially for stability, robustness and documentation, do slow the pace of change a bit, but for good reason, and ultimately with the goal of enabling people people to build things on top easily. A modular, layered design is ultimately in the best interests of everyone, and hopefully provides a solid foundation upon which other developments can happen rapidly and in a distributed, scalable way.