It might be helpful to use SqueakMap for this, too.  Create a
release-specific, class/framework-specific Project and/or or set of
SUnit tests, that demonstrates the cruft you're interested in getting
rid of, and register it on SqueakMap. 

-----Original Message-----

[SNIP]
> What I would like from the guides is a list of "classes to clean".
> We need guides to say:
> 	the two next months we want to clean that class:
> 	we need examples, we need tests, we need comments

Sounds like a good idea. Would you care to help out with a gross list of
such classes to attack? To get the ball rolling I would perhaps focus on
some simpler tasks to begin with.