Date and Time: 6:00am PDT / UTC 13:00, Thursday September 03, 2015
Convener: Bin Hu (AT&T)
Bin introduced the information of electing a committer into the Board. Chris Price indicated that it is usually self-nomination, because of resource commitment such as travel.
Uli asked if there is a consistent list of committers. Chris indicated that it should be retrievable in Gerrit. Bin tried to browse Gerrit and shared screen, but couldn't find such list. Perhaps there are other tricks to retrieve the list from Gerrit but we just don't know how to do it.
Uli and others will figure out more about the logistics of this election offline.
Adi (Huawei) gave an update that he contacted Ryota and attended the weekly meeting of Doctor project. He also had follow-up discussion with Doctor and Copper projects through mailing list. Some simple use cases are within the scope of Doctor project, but some more complicated use cases of fault correlation will not be addressed by Doctor project. So there is a clear gap. And those more complicated use cases of fault correlation will be addressed by Pinpoint project. On the other hand, Doctor certainly will serve as a source of information to Pinpoint's fault root cause analysis.
Adi committed to fully synchronizing with both Doctor and Copper projects, and further analysis of where to address those use cases.
Bryan (AT&T) indicated that we want project to complement each other, and avoid overlap. And he sees clear separation of the scope of those projects. And clearly there are gaps not addressable by either Doctor or Copper projects. And Pinpoint's focus is the correlation engine.
Group achieved consensus to recommend Pinpoint for TSC Creation Review with the understanding that it will focus on correlation engine.
Dave Neary (RedHat) raised question about community awareness of Blueprints that some projects have worked out. The discussion then went on how to look forward to some critical work of C Release (e.g. Blueprints for OpenStack M Release) while stay focused on B Release.
Bin will ask projects for community awareness and community review of Blueprints. Some Blueprints may be reviewed at next week's technical community meeting.