Hi, On 09/07/2016 02:24 AM, Frank Brockners (fbrockne) wrote: > +1. > > Also note that when we defined the project lifecycle we used metrics > like the ones mentioned only as guidance rather than something to > compute a composite value – and even there, we did not constrain things > to metrics in OPNFV only. > > > > Frank > > > > *From:*SULLIVAN, BRYAN L [mailto:bs3...@att.com] > *Sent:* Dienstag, 6. September 2016 18:48 > *To:* Frank Brockners (fbrockne) <fbroc...@cisco.com>; Raymond Paik > <rp...@linuxfoundation.org>; opnfv-tech-discuss@lists.opnfv.org > *Subject:* RE: [opnfv-tech-discuss] Following up on Project Health > metrics discussion > > > > I’m unsure of the overall value of this exercise. Simply ask the PTLs > what the “health” of the project is. An honest PTL will tell you, and > that’s the only type we should elect.
I dispute that this is a question of honesty. When I was starting out my software engineering career, I had an experienced manager who would ask me for estimates on how projects I was working on were going. "Fine," I would answer, "I should be finished that feature next week." Next week rolled around, and I'd get the question again. "Almost done, just a few bugs to work out. By next week it'll be done." I wasn't lying the first week, I just had no idea how to estimate software development. Similarly, if you ask a PTL if their project is "healthy", I would fully expect all projects to say yes - after all, what does an unhealthy project mean? This is where metrics come in... if we can flag certain sets of behaviours as indicating an issue, that allows adjustment. It's not enough to say "30 messages per month with that tag to tech-discuss - that seems pretty good" - by looking at behaviours, we can see who is not engaging effectively upstream, who is developing a lot of code in an OPNFV repo, which projects seem stuck in wiki/email discussions, which projects are not using Jira so well, etc. I don't know what those sets of behaviours/metrics might be, I figure that is the point of the project health metrics initiative. That said, I agree with both Frank and Bryan that unadorned/contextless composite metrics can mask, rather than reveal, some of these issues, and as such are not useful. With context, and with a human eye to evaluate things, some form of composite can be a useful diagnostic tool. Thanks, Dave. > Publish metrics if you want (we already do), but I would avoid trying to > draw conclusions from them. We do not have the luxury (if you can even > call it that!) of creating and maintaining a project-introspection > framework ala what you might see in corporate development shops. Even > considering what metrics are “useful” for specific purposes (e.g. what > “useful”/reliable implications can you draw from them) takes too much > time away from the real work. > > > > Thanks, > > Bryan Sullivan | AT&T > > > > *From:*opnfv-tech-discuss-boun...@lists.opnfv.org > <mailto:opnfv-tech-discuss-boun...@lists.opnfv.org> > [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of *Frank > Brockners (fbrockne) > *Sent:* Tuesday, September 06, 2016 7:39 AM > *To:* Raymond Paik; opnfv-tech-discuss@lists.opnfv.org > <mailto:opnfv-tech-discuss@lists.opnfv.org> > *Subject:* Re: [opnfv-tech-discuss] Following up on Project Health > metrics discussion > > > > Hi Ray, > > > > thanks for posting the initial cut. IMHO a "composite score", as > proposed on the page, could be **very** misleading, especially for > projects which do most of the work upstream. So unless we track all > upstream repos and upstream Jiras (or similar), I would suggest to > **not** compute a composite score but evaluate things qualitatively only. > > > > Thanks, Frank > > > > *From:*opnfv-tech-discuss-boun...@lists.opnfv.org > <mailto:opnfv-tech-discuss-boun...@lists.opnfv.org> > [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of > *Raymond Paik > *Sent:* Montag, 29. August 2016 19:33 > *To:* opnfv-tech-discuss@lists.opnfv.org > <mailto:opnfv-tech-discuss@lists.opnfv.org> > *Subject:* [opnfv-tech-discuss] Following up on Project Health metrics > discussion > > > > All, > > > > I had an action item from last week to start a wiki page for the > "project health metrics". You can find a proposal page > at https://wiki.opnfv.org/display/PROJ/Project+Health+Metrics. > > > > Please add your comments/feedback via email or directly on the wiki > page. I listed four activity areas that was discussed on the TSC call, > but feel free to add other activities that the community should consider. > > > > Thanks, > > > > Ray > > > > _______________________________________________ > opnfv-tech-discuss mailing list > opnfv-tech-discuss@lists.opnfv.org > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss > -- Dave Neary - NFV/SDN Community Strategy Open Source and Standards, Red Hat - http://community.redhat.com Ph: +1-978-399-2182 / Cell: +1-978-799-3338 _______________________________________________ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
