According to this presentation regarding the Apache Way http://events.linuxfoundation.org/sites/events/files/slides/TheApacheWay15.pdf (slides 30-31) all contributions are considered equal. That means the big, the small, those of minor and major importance.
Nevertheless, collaborating early and often will ensure that both noise and reverts are minimised. It can't be avoided that, with all contributors being volunteers with limited time available , a change is committed (accepted by lazy consensus) whereby over a period of time increase in insights will lead to reverts of old code and to replacement by better code. Creating the JIRA issue(s) early - not just after the commit, as a notification for release notes - will help increasing the awareness of all and opens the door to share insights before the commit and not after. Give the issue its obligatory waiting period (72 hrs) before the commit and due process is ensured. Best regards, Pierre Smits *ORRTIZ.COM <http://www.orrtiz.com>* Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http://www.orrtiz.com On Sat, Apr 25, 2015 at 9:52 AM, Jacopo Cappellato < jacopo.cappell...@hotwaxsystems.com> wrote: > > On Apr 25, 2015, at 1:14 AM, Adam Heath <doo...@brainfood.com> wrote: > > > On 04/23/2015 06:00 PM, David E. Jones wrote: > >> An FYI for all committers: create an account on GitHub (if you don't > already have one) and add your @apache.org email address to it, and > within a few hours you'll show up in the contributor graphs. I tried this > and am now showing up there: > >> > >> https://github.com/apache/ofbiz/graphs/contributors > >> > >> If nothing else it's entertaining, I had no idea that I had this volume > of commits since OFBiz joined the ASF (750k lines added, 135k lines > removed; note that changes to lines show up in both counts). > > > > Come on, everyone. It's a competition! See if you can beat Jacopo! > > :-) > Frankly speaking... I hates these and similar metrics (e.g. number of > posts in the mailing list per author, number of commits per author etc...) > because they don't say anything about the quality of the contribution but > just on the amount of noise produced; and I am worried that they may induce > some to post more and more, commit more and more to stay up in the ranking > and this may be detrimental to the quality of the contribution. > > > > > Useless metrics are fun sometimes. Number of commits, number of lines > added/removed, don't really mean anything. I've seen stupid code that had > the same 30 lines cut and pasted 20 times, instead of making a helper > method, and of course a single line per commit can also inflate numbers. > > Right, or several commits then reverted :-) > > Jacopo
