It might help in
-Keeping in touch with other projects
-Keeping developers and users up-to-date with what's happening, at the "overview" level
-Writing the Cocoon story for future generations. Partly joking, but being able to read the last month of news if you've been away for a while helps a lot.
Technically, this could either be:
-A weblog (at blogs.cocoondev.org?)
-A weblog.xml file in CVS, published at regular intervals. Monthly archives should be available then.
I think the weblog could be easier to setup if blogs.cocoondev.org is ok, and volunteer committers might get a password for publishing.
Thoughts? -Bertrand
