A few notes: Noone is expected to continously review even the "closed" CVS repository commits (if one such is created).. I agree that this would be a huge task. I thought that we restrict who may have write access here and also review the project starts. Another issue is the _current_ state. First, those modules that neither work with 4.5 nor with the forthcoming 4.6 surely does not worth a second look. Second, we check correct SQL usage and coding style. If this is OK, and there are two or more modules with colliding functionality we contact the authors asking them to merge. This raises the question that some nice functionality does not get moved to the closed contribs 'cos of some lacking whitespace. Well, we can send a note to the maintainer that his (I was thinking on a PC "her" here, but how many female drupal developers we have? never mind.) module failed the code style check. This is urgent. Please note that Drupal is spreading fast, and next weekend we are going to FOSDEM with IMHO the very intent to make it spread even more. Imagine inviting guests to your house where the actual house is hip, nice and clean but the back yard is ... you get the picture. Of course, we won't be able to clean up that back yard in a week and, after all, we are telling guests that the back yard is not maintained :) Regards Karoly Negyesi