Dirk-Willem van Gulik wrote:
Our project is getting value out of the Wiki, in part because we have non-Committers feeling empowered and able to contribute directly.
People can do the same with patches on mailing list; and seem less likely to abuse that. Perhaps the simple validation (and display) of
a valid email address may do the trick.
The combination of a Wiki (JSPWiki, which offers an XMLRPC interface for integration purposes), and hourly mailing list notifications _with_ diffs on a designated list is working incredibly well for Cocoon.
Some _users_ have even started a complete overhaul of introductory Cocoon documentation, something which would be hard to handle using CVS and patches.
I agree with the idea that this is partly because of the Wiki being
owned and operated by the Cocoon community (users & committers),
and eventualy might be moved under the oversight of the Cocoon PMC, rather than an centralized ASF resource (= multi-project and/or in-crowd-only).
</Steven> -- Steven Noels http://outerthought.org/ Outerthought - Open Source, Java & XML Competence Support Center Read my weblog at http://blogs.cocoondev.org/stevenn/ stevenn at outerthought.org stevenn at apache.org
