On Tue, 2009-07-21 at 10:04 +0200, Hans Dockter wrote: [ . . . ] > There are some islands in the code where the documentation is not > good. Other parts of the API have excellent docs. This has also > historical reasons as the Groovydoc tool was initially pretty useless. > This has changed but not the groovydoc. [ . . . ]
I wonder if, perhaps, everyone can make it a policy that, whenever they
make a commit, they slip in a few comments about classes and methods
that currently don't have any.
It really needs the people who know the code to do this, there isn't
much point in people volunteering to help who don't already know the
code.
Not a particularly helpful comment on my part, I know, I just wanted to
encourage anyone who has knowledge associated with a currently
undocumented bit of the code base to take the time to add some
documentation comment in.
--
Russel.
=============================================================================
Dr Russel Winder Partner
xmpp: [email protected]
Concertant LLP t: +44 20 7585 2200, +44 20 7193 9203
41 Buckmaster Road, f: +44 8700 516 084 voip: sip:[email protected]
London SW11 1EN, UK m: +44 7770 465 077 skype: russel_winder
signature.asc
Description: This is a digitally signed message part
