14:05:09 <rpaik> #startmeeting OPNFV Projects
14:05:09 <collabot> Meeting started Wed Aug  3 14:05:09 2016 UTC.  The chair is rpaik. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:05:09 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
14:05:09 <collabot> The meeting name has been set to 'opnfv_projects'
14:05:20 <rpaik> #info Ray Paik
14:05:25 <bjskerry> #info Brian Skerry
14:05:42 <dmcbride> #info David McBride
14:06:05 <bjskerry> #info from TSC minutes June 28th: "Project structure, scope and coordination discussion: There are a number of projects that have not been active or staffed by a single company and has not been able to attract new contributors.  There was a good discussion on different metrics to determine the health/status of projects.  Brian Skerry and Tapio agreed to meet after their vacations to continue evaluating this topic.  "
14:07:44 <bjskerry> #info Some projects are still alive, even though they appeared dormant for a while.
14:09:00 <bjskerry> #info Examples of projects that had no activity for a while but had presentations at the last summit
14:10:58 <bjskerry> #info There are really two types of dormant projects; those that have indicated they plan to participate in a given release and those that don't
14:12:44 <bjskerry> #info If there is nothing happening for multiple release cycles that indicates a problem
14:13:35 <rpaik> #info in addition if there is nothing happening in the OPNFV tools (e.g. Jira, git/gerritt, etc.)
14:16:21 <bjskerry> #info For some projects there are activities, but nothing is being recorded.  Having a well-defined process might give projects the incentive to keep status up to date.
14:16:41 <bjskerry> #info Need a way for projects to withdraw intent to participate in a release
14:17:23 <rpaik> #info another criteria is when the project team members are not responsive
14:18:50 <ChrisPriceAB> IRC only meeting?
14:18:59 <bjskerry> #info Meeting minutes are another criteria
14:19:17 <rpaik> ChrisPriceAB let me send you the GTM info
14:19:39 <rpaik> https://www.gotomeeting.com/join/991112053
14:25:24 <bjskerry> #info Can we use Bitergia as an first level indicator of a potential problem?
14:29:31 <rpaik> #info discussion on quarterly report out to the TSC on dormant projects
14:29:37 <ChrisPriceAB> #info I wonder what are the basic metrics we might want to try out.
14:30:59 <rpaik> #info suggested metrics: no activities on the repo's, Jira (per Bitergia), no updates on the wiki, and project team members not responsive
14:32:18 <ChrisPriceAB> #info activity in the repository:  Can this be measured in a metric indicative of both contributions to the repo and the level of activity of the projects committers?
14:33:03 <bjskerry> #info For Colorado: of all the projects that planned to participate, 6 to 8 didn't make it.
14:42:29 <rpaik> #info an example of activity metric could be 1-10 for repo activities; 1-10 for closed Jira tickets; etc.
14:43:36 <rpaik> #info a better option could be "top 10" gets a score of 10
14:43:43 <rpaik> #undo
14:43:43 <collabot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x2c69ad0>
14:47:28 <bjskerry> #info There are really two issues: 1. Objective criteria for health of each project; 2. For little to no activity for a project what should we do about it
14:47:50 <ChrisPriceAB> +1 ^^
14:48:55 <bjskerry> #link https://wiki.opnfv.org/display/SWREL/Releases+Colorado+Projects
14:53:16 <rpaik> #info discussion on doing a quarterly report of project health
14:56:44 <bjskerry> #info Need to have a discussion in the TSC for projects that are not ready for colorado
14:57:59 <tallgren> We also need to set the criteria for new projects, like the number of participating companies
15:00:58 <dmcbride> #info projects previously removed from Colorado:  Escalator, RS, Policy Test
15:01:49 <rpaik> #endmeeting