Martin Dougiamas

The smiley cakes will be gone in 2.0. See MDL-14361.

Well, there is some stuff relevant here:

You can set the site name which sets the title of the site.

You can set the site description which (on most themes) is set to be the metadata description for the site (whether or not you choose to show it on the front page in a block).

You can make sure there are course links on the front page for non-logged-in users so that course descriptions get indexed by crawler.

As for mod_rewrite to remove parameters from the paths, is this really an issue anymore? It sounds like old information ... Google for example has no issues indexing all of Moodle.org currently.

A standard sitemap generator would be a nice idea (I guess it would just present search engines with public course descriptions etc, which is easy, and public forums/announcements). What else could/should it do?

We really need to update the default icons in Moodle 2.0.

One good idea is to move to using something based on the Tango Icon Library (which is GPL and widely used).

There is also the Silk set: http://www.famfamfam.com/lab/icons/silk/ and the Nuvola set: http://www.moodlezengarden.com/

They all require quite a bit of work and I would really appreciate your help in helping us to choose and finish one beautiful new set of icons to put in core.

See MDL-14361 for details.

I think the vote currently just shows that people who don't need keywords don't want them.

Binary files were already being treated as -kb (we explicitly specify a long list by file extension)

I'm not sure about setting everything to -kb all the time. It makes sense to me but are there any gotchas? Any other opinions?

OK, so we've been discussing this in the dev chat.

Positives to expanded keywords are:
a) You get a quick idea of who edited this last.
b) Users downstream can easily tell you what version they are using.

Negatives are:
a) git doesn't support them
b) IDEs have trouble with them
c) some developers hate metadata embedded in code

There seems to be four solutions:

1) Add a GPL boilerplate to every file in one huge commit so that the keywords never get caught up in future diffs. This is something we should do anyway.

2) Switch the main CVS server to use -kk by default (unexpanded), but switch the read-only CVS mirrors to use -kkv. This means developers won't be bothered and users still have the infoon their sites. All developers would need to check their settings.

3) Remove keywords from HEAD, but add them back to the packages using an evil script on download.moodle.org.

4) Just abandon keywords entirely. This is an easy search-replace.

Make your choice!