twingle/doc/teps README.txt,NONE,1.1
[email protected] Thu, 6 Mar 2003 03:54:12 -0700 (MST)
| Newsgroups | gmane.comp.cms.oscom.twingle.cvs |
|---|---|
| Message-ID | <[email protected]> |
Update of /cvs/root/twingle/doc/teps
In directory alpha.oscom.org:/tmp/cvs-serv11543
Added Files:
README.txt
Log Message:
First checkin
--- NEW FILE: README.txt ---
Twingle Enhancement Proposals
As we work on Twingle, we need to make proposals for important
changes. These proposals need to be communicated to others in an
organized way, both during the discussion process and later when new
people join to project.
The TEP process is a very lightweight system for managing and
recording discussions. It has the following goals:
o Lightweight. The only rules are the ones absolutely necessary.
o Discussing. Write down for others what you intend to do.
o Tracking. Did we agree to something? Each TEP has a field to
say so.
o Archiving. Later, we can look up the syntax or format that was
proposed.
o Documentation. Similarly, new project developers can look at
some docs about what has been decided.
The audience for TEPs is *fellow Twingle developers*.
Description of Process
I propose that we pattern TEP completely on the Python Enhancement
Process:
http://www.python.org/peps/