Hi Stef, To me class comments are not *that* useful. Most of the time I search explanations for contexts of use, which usually involves many classes and methods everywhere. I would remove packages which doesn't include at least some brief or general comments of the main classes or methods, this is less effort for a developer to remember and to document. Or it could be a start. Hernán 2010/12/5 Stéphane Ducasse <stephane.ducasse@inria.fr>:
Hi guys
I decided that I will not integrate any code that is not documented in Pharo.
I strongly suggest to remove from Pharo-dev packages whose classes are not commented. I'm not sure that I will look at code or answer question to code that is not commented. We should change our mindset and it seems that we do not care, so we should take radical decisions: Â Â Â Â less changes, less progress, more comments.
And for once I will not bash the past. Smalltalk was always with methods fully documented. We are just plain lazy and this is a shame.
Stef
-- Hernán Morales Information Technology Manager, Institute of Veterinary Genetics. National Scientific and Technical Research Council (CONICET). La Plata (1900), Buenos Aires, Argentina. Telephone: +54 (0221) 421-1799. Internal: 422 Fax: 425-7980 or 421-1799.