Generate package code statistics on submission

[noamross]

It would be useful to get package code statistics via cloc on submission. A bonus would be if cloc could distinguish between raw comments (often indicators of "ghost code") and roxygen comments (which may indicate well-developed documentation).

[maelle]

• Using previous submissions/CRAN pkgs as comparison
• Also look at frequency of raw comments vs code (would show unreadable bc unexplained code?)
• Also generate statistics about no of exported classes&functions

[maelle]

We'd also need to decide what to do with the info. If a pkg is gigantic, suggest splitting +warn potential reviewers?

Oh and looking for code duplication cf ropensci-review-tools/goodpractice#78

[maelle]

Does launchboat handle this @noamross ?

[noamross]

Yes, it has a cloc report, though launchboat needs some work. Also I had discussed another idea for a package with Bob at the unconf, cranstats, that would hold pre-generated cloc and other data for all packages on CRAN, and then when run on a local package would show where it falls in the distribution.

[maelle]

Handled via pkgreport cc @mpadge