I have some suggestions for the [Azimuth Code Project main page](http://code.google.com/p/azimuthproject/) on Google. (I don't seem able to edit it myself.)
1) I think it's good for us to have clear names for different pieces of the overall Azimuth Project. It's already a bit confusing with
1. Azimuth (the blog),
2. the Azimuth Project (wiki), and
3. the Azimuth Forum (this forum).
These names are not optimally clear: perhaps someday we should change them! It would make more sense to use Azimuth Project for the whole project, and
1. Azimuth Blog,
2. Azimuth Wiki, and
3. Azimuth Forum
for these three pieces.
Now Tim has introduced a fourth piece: the Azimuth Code Project. I like that name! But on what I'm calling the "[Azimuth Code Project main page](http://code.google.com/p/azimuthproject/)", we _don't see_ the phrase "Azimuth Code Project". We instead see "azimuth project" (on the page) and "azimuthproject" (in the URL). I suggest that at least on the page itself, there's a nice clear header saying "Azimuth Code Project".
2) I suggest changing
> The azimuth project tries to provide clean, well documented implementations of basic numerical algorithms, using up-to-date tools and paradigms from software engineering. It is associated to the Azimuth project of John Baez.
> The Azimuth Code Project tries to provide clean, well documented implementations of basic numerical algorithms, using up-to-date tools and paradigms from software engineering. It is associated to the [Azimuth Project](http://www.azimuthproject.org/azimuth/show/HomePage), which is a plan to create a focal point for scientists and engineers interested in saving the planet, and make clearly presented, accurate information on the relevant issues easy to find.
3) Since we're trying to do things well, let's make it easier for people to see what code is available on the Azimuth Code Project. I'm no expert on Google Project Hosting, but I had to go to [code](http://code.google.com/p/azimuthproject/source/checkout), read the stuff there, then go to [http://azimuthproject.googlecode.com/svn/trunk/](http://azimuthproject.googlecode.com/svn/trunk/), and then climb down a tree (a trunk?) to find various interesting pieces of code.
Shouldn't we have something more user-friendly and fun? How about a list of projects (perhaps so far just the Hopf bifurcation and stochastic resonance), with links to the relevant code? There must be some way you software guys do this.
4) Graham has written some code in R, making the source available on various Azimuth Project pages. Could this perhaps be better integrated into the Azimuth Code Project? It may conflict with Tim's strategy of using Java - but do we need a different Azimuth Code Project for each software strategy?