public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Donald G Porter <dgp@email.nist.gov>
To: tcl-announce@mitchell.org, tcl-core@lists.sourceforge.net,
	tcl-pubs@lists.sourcerforge.net, tcl-win@lists.sourceforge.net,
	tcl-mac@lists.sourceforge.net, wintcl@scriptics.com,
	mactcl@scriptics.com, tclprojects@scriptics.com,
	itcl@scriptics.com, incrtcl-users@lists.sourceforge.net,
	tkcvs-discuss@sourcegear.com, tcl-i18n@yahoogroups.com,
	sourcenav@sourceware.cygnus.com, tkgs-devel@sourceforge.net,
	tkgs@ajubasolutions.com, tkgs-list@yahoogroups.com,
	tclpro-dev@lists.sourceforge.net, tkhtml@yahoogroups.com,
	ptk@lists.stanford.edu
Cc: claird@starbase.neosoft.com, lvirden@cas.org
Subject: Tcl Core Team: Call for Tk maintainers
Date: Fri, 06 Apr 2001 11:47:00 -0000	[thread overview]
Message-ID: <200104061846.OAA27985@email.nist.gov> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2377 bytes --]

	*	*	*	*	*	*	*
	
In February, the Tcl Core Team (TCT) called on members of the community
to volunteer as maintainers of the Tcl source code.  We are pleased to
note that many prominent members of the Tcl community have answered that
call, including Daniel Steffen, Kevin Kenny, Miguel Sofer, Rolf
Schroedter, and Vincent Darley.  Several TCT members are also performing
maintainer duty.  Thanks to all these people [*] who keep high quality
in the Tcl source code!

In recent days, the TCT has quietly been collecting volunteers to serve
as maintainers of the Tk toolkit source code.  Already on board are
Allen Flick, Frédéric Bonnet, and Miguel Bañón in addition to TCT
members [+].  Now the TCT would like to issue a more public invitation
to others who may be interested in working on the Tk source code.

We have divided Tk into 86 parts, each covering one functional area [#].
We are looking for people who are willing to maintain / take
responsibility for (at least) one of these functional areas.  Each area
can have many maintainers, so feel free to join forces with others.  
Prior knowledge of the Tk source code in the chosen area is useful but
not required.  A willingness to acquire such knowledge is required, as
is enough volunteer time, i.e. at least a few hours per week.

The basic tasks a maintainer performs are the review and integration of
patches to his or her functional area of Tk.  For a more detailed
description of how maintainers work on Tcl/Tk, see TIP 28 [$].

People who are interested in becoming a Tk maintainer (or a Tcl
maintainer -- there's still room for more!) should send an email to the
TCLCORE mailing list <tcl-core@lists.sourceforge.net>.  Let us know your
SourceForge [@] account name, so we can empower you as a Tcl/Tk
Developer.

~~~
[*] -- http://dev.scriptics.com:8080/cgi-bin/tct/tip/24.html --
[+] -- http://dev.scriptics.com:8080/cgi-bin/tct/tip/30.html --
[#] -- http://dev.scriptics.com:8080/cgi-bin/tct/tip/23.html --
[$] -- http://dev.scriptics.com:8080/cgi-bin/tct/tip/28.html --
[@] -- http://sourceforge.net/ --

| Don Porter          Mathematical and Computational Sciences Division |
| donald.porter@nist.gov             Information Technology Laboratory |
| http://math.nist.gov/~DPorter/                                  NIST |
|______________________________________________________________________|

                 reply	other threads:[~2001-04-06 11:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200104061846.OAA27985@email.nist.gov \
    --to=dgp@email.nist.gov \
    --cc=claird@starbase.neosoft.com \
    --cc=incrtcl-users@lists.sourceforge.net \
    --cc=itcl@scriptics.com \
    --cc=lvirden@cas.org \
    --cc=mactcl@scriptics.com \
    --cc=ptk@lists.stanford.edu \
    --cc=sourcenav@sourceware.cygnus.com \
    --cc=tcl-announce@mitchell.org \
    --cc=tcl-core@lists.sourceforge.net \
    --cc=tcl-i18n@yahoogroups.com \
    --cc=tcl-mac@lists.sourceforge.net \
    --cc=tcl-pubs@lists.sourcerforge.net \
    --cc=tcl-win@lists.sourceforge.net \
    --cc=tclpro-dev@lists.sourceforge.net \
    --cc=tclprojects@scriptics.com \
    --cc=tkcvs-discuss@sourcegear.com \
    --cc=tkgs-devel@sourceforge.net \
    --cc=tkgs-list@yahoogroups.com \
    --cc=tkgs@ajubasolutions.com \
    --cc=tkhtml@yahoogroups.com \
    --cc=wintcl@scriptics.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).