Hi,

> I personally deliberately avoided number of commits/PRs in the report
> as I saw Justin giving the same remark in his review to other reports
> that did that, and I believe he has a good argument.

I’s not just my point, the board frequently gives the same feedback on reports 
that just contain stats/number with no explanation.

Some examples:
"rb: Please drop the mailing list and Jira stats section of the
    report unless those numbers support a specific point you wish to
    make."
"idf: When including mailing list and jira stats it would be helpful
     if you could include a bit of explanation as to what they mean
     for your project.”
“ mt: The mailing list stats and the Jira stats should be not be
     included in the report unless there is something noteworthy
     about them”

Thanks,
Justin

Reply via email to