Each project should have its own page with all of the associated project pages / attachments under it.

For consistency, use the same <project Name> as recoded in the list of Resources and Repositories

Approved Project Proposal

Release Planning

Weekly project meetings are held on Tuesdays from 10AM-11AM EST. .

ONAP Meeting 2 is inviting you to a scheduled Zoom meeting.

Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/252520698

Or iPhone one-tap (US Toll): +14086380968,,252520698# or +16465588656,,252520698#

Or Telephone:
Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll)
+1 855 880 1246 (US Toll Free)
+1 877 369 0926 (US Toll Free)
Meeting ID: 252 520 698
International numbers available: https://zoom.us/zoomconference?m=qn560WOM7jr2THShO6xPhN76NtUtxewq

Tasks

Topic	Notes	Follow-Up
M1 Deliverables definition	All - [vnfrqts ] email discussion on number and structure of deliverables so we can have a decision on next week's call	see also the daughter page: M1 Release Planning link Steven Wright entered the project epics based on the RACI chart LHS column. Herb Patten and Scott Blandford to add user stories into JIRA corresponding to the epics.
Tool Chain	proposal for a workflow using confluence tools - (Alex Vul) see also documentation project's toolchain comparison and recommendation.	JIRA vnfrqts project established 2017-7-11 The documentation project seems to be planning to use ReadtheDocs to extract and assemble documentation from development projects. vnfrqts would expect to follow the same toolchain.
deliverable format	from discussion on 2017-7-11, assume the immediate output is to confluence wiki pages and use confluence tooling to then generate pdf, spreadsheets etc.
JIRA followup	2017-7-11: Steve Wright to follow up with Gildas on the JIRA platform to see if the Boards etc. there are applicable to tracking individual VNF requirements.