#onap-meeting: Amsterdam M1 Review #2
Meeting started by kennypaul at 13:50:38 UTC
(full logs).
Meeting summary
-
- Ranny Haiby, Nokia (RannyHaiby,
14:01:01)
- Jason Hunt, IBM (JasonHunt,
14:01:17)
- Xiaojun Xie, China Telecom (Xiaojun,
14:01:47)
- Huabing Zhao on behalf of Zhaoxing Meng,
ZTE (Huabing_Zhao,
14:02:22)
- stephen terrill, Ericsson (SteveT,
14:02:36)
- Alla Goldner, Amdocs (alla,
14:03:57)
- Lingli Deng, China Mobile (Lingli_Deng,
14:05:09)
- Chris Donley, Huawei (cdonley,
14:05:10)
- Xinhui Li, VMware (xinhuili,
14:05:59)
- simple voice vote (kennypaul,
14:07:44)
- approval considered to be granted if no
objections (kennypaul,
14:08:14)
- modeling (kennypaul, 14:08:28)
- Sonu covering for Rajesh from Intel
(Sonu,
14:09:30)
- concerns over the number of committers
(kennypaul,
14:11:34)
- if a committer is also a code contributor that
person's name should be in both locations (kennypaul,
14:13:22)
- a committer should not be committing their own
code. (kennypaul,
14:14:01)
- the code for this is already very mature
(kennypaul,
14:14:40)
- Deng recommends waiting until code freeze to
lock down committers (kennypaul,
14:17:33)
- discussion over "parser" definition
(kennypaul,
14:19:48)
- AGREED: w/
contingency of clarification of committers and resource allocation
updates (kennypaul,
14:22:58)
- Service Orchestrator (kennypaul, 14:23:23)
- (JasonHunt) "The risk with committers signing
up on their own is that they have the power to commit code.
Typically, you have to demonstrate your technical credentials and
contributions before being named a committer. If I were a project
lead, that would concern me." (kennypaul,
14:24:05)
- (Jamil) "Committer should deliver code"
(kennypaul,
14:24:40)
- (Seshu) TBDs in the checklist are pending a
meeting- not concerned with ability to complete (kennypaul,
14:28:23)
- (Helen) A committer should be a contributor,
plus a committer has right to review other's code. (helenychen,
14:28:46)
- same contingency on resource allocation
(kennypaul,
14:30:05)
- discussion of proposals w/ architecture
committee (kennypaul,
14:30:48)
- AGREED: review
approved w/ contingency (kennypaul,
14:31:16)
- Multi VIM/Cloud (kennypaul, 14:31:58)
- ACTION: in PTL
meeting need to follow up on API risks (kennypaul,
14:37:36)
- team has agreement w/ APPC but not with DCAE
yet (kennypaul,
14:38:04)
- potential misunderstandings can be made worse
with many committers (kennypaul,
14:40:36)
- ACTION: add risk
section to checklist (kennypaul,
14:42:13)
- in addition to weekly PTL meeting suggest
assigning roles for xfunc coordination (kennypaul,
14:44:11)
- AGREED: with
contingency on resource allocation and action of risk section
(kennypaul,
14:45:11)
- CLI (kennypaul, 14:46:01)
- need updates to inbound APIs (kennypaul,
14:46:22)
- ACTION: -gildas
review commit/code review best practices at the PTL meeting
(kennypaul,
14:51:40)
- AGREED: Review
approved (kennypaul,
14:51:52)
- Integration (kennypaul, 14:52:25)
- need to clarify what testing is covered in
Amsterdam (kennypaul,
14:54:42)
- testing for vCPE and VoLTE use cases but not
Demos (kennypaul,
14:56:29)
- discussion over responsibility for owning the
Demos. (kennypaul,
14:57:06)
- would like updates on progress of
automation (kennypaul,
15:00:40)
- Helen would like to see better defined
committer criteria from TSC (kennypaul,
15:03:27)
- ACTION: gildas take
issue of Demos to TSC (kennypaul,
15:03:49)
- AGREED: Review
Approved (kennypaul,
15:04:08)
- CCSKD (kennypaul, 15:04:40)
- docker can be removed from the list of API
dependenies (kennypaul,
15:06:16)
- AGREED: Review
Approved (kennypaul,
15:07:04)
- Documentation (kennypaul, 15:08:19)
- using 3 repos versus an umbrella project
approach (kennypaul,
15:15:48)
- (Lingli) need to formalize the self-committer
policy (kennypaul,
15:18:57)
- AGREED: Review
approved (kennypaul,
15:19:06)
- External API Framework (kennypaul, 15:19:48)
- https://wiki.onap.org/display/DW/Committer+Best+Practices
(kennypaul,
15:22:28)
- above related to committer best
practices (kennypaul,
15:22:51)
- AGREED: Review
approved (kennypaul,
15:23:06)
- ONAP Operations Manager (kennypaul, 15:24:18)
- Release Deliverables - defined, but not linked
to the page yet. (kennypaul,
15:25:42)
- need better understanding of roll back
capabilities (kennypaul,
15:27:48)
- ACTION: PTL fill in
check list. (kennypaul,
15:29:01)
- roll back will need joint testing (kennypaul,
15:30:51)
- AGREED: Review
Approved w/ contingency on resource allocation and checklist
(kennypaul,
15:31:58)
- follow up reviews from last review (kennypaul, 15:35:27)
- (Hui Deng) concerns over violations to charter
by paring down committer list. (kennypaul,
15:37:49)
- (Chris D) PTL should ask committers to
voluntarily step down (kennypaul,
15:38:30)
- (Helen C) if no one steps down, then
what? (kennypaul,
15:39:10)
- (Chris D) can take a vote among committers
once there is experience w/ the team (kennypaul,
15:40:38)
- Project Review of Network Function Change Management proposal (kennypaul, 15:43:53)
- this would be an end-to-end across all
projects- more logical as a Subcommittee (kennypaul,
15:44:40)
- OR as a usecase for Beijing release
(kennypaul,
15:45:33)
- project proposal will be withdrawn (kennypaul,
15:48:13)
Meeting ended at 15:48:44 UTC
(full logs).
Action items
- in PTL meeting need to follow up on API risks
- add risk section to checklist
- -gildas review commit/code review best practices at the PTL meeting
- gildas take issue of Demos to TSC
- PTL fill in check list.
People present (lines said)
- kennypaul (74)
- collabot` (9)
- Jamil (2)
- alla (2)
- JasonHunt (2)
- Sonu (2)
- Xiaojun (1)
- Huabing_Zhao (1)
- xinhuili (1)
- SteveT (1)
- cdonley (1)
- helenychen (1)
- RannyHaiby (1)
- Lingli_Deng (1)
- phrobb (0)
- gildaslanilis (0)
- CaseyODL (0)
Generated by MeetBot 0.1.4.