Le 26/3/16 15:50, Cyril Ferlicot D. a écrit :
Le 26/03/2016 09:19, stepharo a écrit :
But you see you are becoming the most aware for athens and what we should do is document document. Now I got ****EXHAUSTED**** to document things that I did not build or use daily. This effort for me is gigantic and I cannot do it each time. In my opinion Pharo should refuse to include any class without at least a one line documentation for the small classes. And when someone review a bug correction and see that an important class have a really small documentation it should be a stop for the integration.
I never saw a Java class without documentation on oracle site. :) at least you made my day comparing pharo with oracle I felt proud :)
This will slow down the integration of some project, but since everyone agree that pharo included too many project, this should not be a problem. At least we would integrate only projects understandable by the others.