Mission Statement
Characteristics of a good mission statement (according to the internet) 
- Succinct
- Memorable
- Distinctive
- Has Longevity
- Motivating
Possible Drafts (feel free to edit, comment, or add your own)
"Potato" empowers the global communications industry to deploy applications and infrastructure quickly, reliably, and securely.
"Potato" exists to serve the infrastructure needs of the global communications industry through architecture alignment, integration, automated testing, and conformance programs. We power the telco cloud.
"Potato" defines, integrates, deploys, and tests the infrastructure and applications necessary for next-generation communication services.
"Potato" improves the quality and agility for on-boarding network services through architecture alignment, integration and deployment, test automation, and conformance.
Scope
Current OPNFV Scope statement; The scope of the Project includes software development under an OSI-approved open source license supporting the mission, including documentation, testing, integration and the creation of other artifacts that aid the development, deployment, operation or adoption of the open source software project.
Possible new one: The scope of the Project includes both software development under an OSI-approved open source license and reference documentation, requirements, and specifications under <creative commons> in order to support the mission. These include release documentation, architecture and requirements documents, testing, integration, and the creation of other artifacts that aid in the development, deployment, operation, or adoption of the open source project.
Possible deeper dive statements to drive the formulation of the full value prop
Note that this is taken from the OPNFV 2.0 work; need to integration anything missing from CNTT
(a) Fostering close collaboration of Communication Service Providers (CSPs) and their supply chain to integrate and build tests, tools, and components for NFV infrastructure, VNFs and CNFs which realize the stated outcomes of this mission,
(b) iterating on developing an integrated, tested, and certified open software reference infrastructure (including interfaces to hardware), with tools of its own design and from upstream testing projects,
(c) contributing changes to and influencing upstream projects leveraging the reference infrastructure,
(d) building new open source components within the reference infrastructure where needed,
(e) leveraging open implementations to drive an open standards and open-source-based ecosystem for NFV solutions,
(f) supporting and maintaining the strategic framework of the Project through the technologies made available by the organization to make the Reference Infrastructure testing, certification, and deployment a success.