Idea: Crossbreed a source code control system and a wiki

[mjd-perl-pm@plover.com]

What if the source code for a software package such as Perl or Apache
HTTPD were derived from a wiki?  Each wiki page would be a function.

Function calls would be hotlinked to their corresponding pages in the
wiki.  Documenation would be more wiki pages; comments in the source
code might link to other wiki pages.

Anyone who wanted to make a change would do it.  After each change,
the code would be automatically extracted from the wiki and rebuilt
and the automated tests (other wiki pages) would be run.  If a change
resulted in new test failures, the test failures report would be
automatically added to the wiki, as an annotation to the change that
caused them.

Periodically, a snapshot of working code would be taken and packaged
and a new version would be released.

If you don't like that anyone can change the source code, replace
'anyone' with 'anyone on the development team'; wikis don't have to be
public.  

-
**Majordomo list services provided by PANIX <URL:http://www.panix.com>**
**To Unsubscribe, send "unsubscribe phl" to majordomo@lists.pm.org**