...
Antitrust Policy Statement: Meetings of the ONAP Project involve participation by industry competitors, and it is the intention of the Project to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of and not
participate in any activities that are prohibited under applicable U.S. state, federal or foreign antitrust and competition laws. Examples of types of actions that are prohibited at ONAP Project meetings and in connection with ONAP Project activities are described in the The Linux Foundation Antitrust Policy. If you have questions about these matters, please contact your company counsel or Andrew Updegrove, of the firm of Gesmer Updegrove LLP, which provides legal counsel to The Linux Foundation.
Linux Foundation Antitrust Policy: https://www.linuxfoundation.org/antitrust-policy
- Assemble/Welcome (5 min)
# | Objective | How Achieved | Participant Preparation required | Action items out |
|---|---|---|---|---|
| 2 | Review JIRA Backlog. Participants should be comfortable that they understand the backlog of tasks for our project ( 15 min) | Walk through the JIRA backlog to check for completeness | review: I (Neal) just create a bug on VNF requirement in JIRA for I just notice that there are 2 requirement items are not in line with VNF guideline document. Sorry for so late. 2 weeks ago, in weekly meeting, VNF guideline document was modified.VNF is not mandatory requested to only use the NCSP’s standard set of OS images now. R-46960 and R-23475 of VNF requirement should keep changes synchronized R-46960 The VNF MUST utilize only the Guest OS versions that are supported by the NCSP’s Network Cloud. [1] R-23475 The VNF SHOULD utilize only NCSP provided Guest OS images. [1] I suggest that maybe we can copy the relevant text from guideline document directly. | |
| 3 | Develop Beijing definition. Participants should be comfortable with an achievable development sprint scope ( 30 min) | VNF Use cases ? VNF Test Case Descriptions? | propose a minimal "getting started" sprint scope. ensure that suitable JIRA tasks are already in place to support this scope. review: | Create / edit Intention to participate in Beijing (due by 11/30) |
4. Any other Business? (5 min)
Lessons learned from Amsterdam release?
- meeting once a week seems like not enough time for some topics
- haven't seen much email discussion on the discuss list
- may need to do something else - e.g. create a tiger team/ task to resolve a particular topic?
- find a way to encourage broad active participation
- better time spot to avoid conflicts/ prioritization of the work?
- email request / reminder
- use F-F meetings better?
- work process for the group - getting creation/ discussion in JIRA before implementation
- distinctions between bugs e.g. formatting vs more meaningful changes to requirements
- closer collaboration with other projects - especially VVP, docs, VNFSDK
- test case descriptions as handoffs?
- earlier requirement content freeze date (e.g. at Mx milestone) to avoid last minute changes
F-F meeting in Santa Clara Dec 11-13