...
For ease of tracking input, please put any comments/questions/etc., in by prepending feedback/comment/suggested change by <Your initials or name> or by using the Wiki comment function
Mission Statement: Empowering Empower the global communications community to create by creating and developing reference cloud infrastructure models, architectures, conformance programs and tools , and programs to deliver network services faster, more reliably, and securely.
(PG) Typically mission statements do not get into the weeds about how. So suggest as in the comments: "Empower the global communications community to deliver reliable and secure network services faster."
Scope:
Anuket supports the development of reference infrastructure architectures, tools, and programs using open source license and documentation, requirements, and specifications under <creative commons>. To support the development, deployment, operation, or adoption of the open source project, will require release documentation, architecture and requirements documents, testing, integration, and the creation of other artifacts. Scope includes but is not limited to
...
: missing the foundation, viz., Reference Model) (Walter K: I agree with PG, it is extremely important to remember that CNTT proposes ONE Reference Model from which different technology architectures are derived. This is our strength. I propose: "developing reference cloud infrastructure model, architectures, tools, ...". I would prefer "developing" rather than "creating"; we have already created a lot of good stuff, which has been acknowledged in the telco industry; let us not forget it)
SK; I would add conformance as well to say "developing reference cloud infrastructure model, architectures, conformance program, tools,.......
BFC: Got all of the comments in.
Scope:
Anuket develops open reference infrastructure models, architectures, tools, and programs. Open source software developed within the project will leverage OSI-approved licenses, while documentation, including specifications, will leverage open licenses. The scope of the project includes but is not limited to:
(a) Enabling member communities to align on reference model, architecture and implementation requirements and specifications for cloud-based communications infrastructure and workloads (Walter K: again our unique model seems to be lost; I propose , "...to align on the reference model, reference architectures and reference implementations..." (BFC: Added reference to the statement.)
(b
...
) Supporting open source and open standards communities in the ecosystem,
(c) Developing an integrated, tested, and validated open
...
software reference infrastructure (including interfaces to hardware), with tools of its own design and from upstream testing projects,
(
...
d)
...
Helping design a conformance framework and validation programs,
(
...
e)
...
Contributing to and influencing upstream projects leveraging the reference infrastructure,
(
...
f)
...
Creating new open
...
source components within the reference infrastructure where needed,
(
...
g) Supporting ongoing strategic activities and
...
evaluating emerging technologies to foster continued deployment success.
Older Drafts/Notes:,
(g)PG) Typically mission statements do not get into the weeds about how. So suggest as in the comments: "Empower the global communications community to deliver reliable and secure network services faster."
Scope BulletsBeth Cohen Proposed reorder:
(a) Enable member communities to align on architecture and implementation requirements and specifications for cloud-based communications infrastructure and workloads(e Drive open standards and open-source-based ecosystems,
(b) Develop an integrated, tested, and validated open software reference software reference infrastructure (including interfaces to hardware), with tools of its own design and from upstream testing projects,
(c) Help design a conformance framework and validation programs,
(c) Contribute to and influence upstream projects leveraging the reference infrastructure,
(d) Create new open source components source components within the reference infrastructure where needed,
(c) Help design a conformance framework and validation programse) Drive open standards and open-source-based ecosystems,
(f) Support Support ongoing strategic activities and evaluate emerging technologies to foster continued deployment success,
(g)
Mission Statement
Characteristics of a good mission statement (according to the internet) 
...
Empowering the global telecommunications community to create new cloud infrastructure reference architectures, tools and programs to deliver network services faster, more reliably and securely.
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.
Proposed new scope:
Anuket supports the development of reference infrastructure architectures using open source license and reference documentation, requirements, and specifications under <creative commons>. 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. Scope includes but is not limited to
(a) Foster close collaboration of member of the global telecommunications community to align on architecture and implementation requirements and specifications, integrate and build tests, tools, and components for NFV infrastructure, VNFs and CNFs which realize the stated outcomes. (HRK – May not need the last bit of this sentence – seems competitive to vendors and a-e restate more cleanly) (PG: IMHO, Scope statement relate to work but not the intent – "Foster close collaboration ..." is more like a Mission or Purpose)
(b) Develop an integrated, tested, and certified open software reference software reference infrastructure (including interfaces to hardware), with tools of its own design and from upstream testing projects,
(c) Contribute to and influence upstream and influence upstream projects leveraging the reference infrastructure,
(d) Create new open source components source components within the reference infrastructure where needed,
(e e Drive open standards and open-source-based ecosystems,
(f) Support Support for the strategic framework through the technologies made available by the organization to make the Reference the Reference Infrastructure testing, certification, and deployment a success. (HRK – Make this more clear – currently up for multiple interpretations)
Possible deeper dive statements to drive the formulation of the full value prop
Also possible to add these to the scope statement
When we define value prop, should consider the types of work we do that isn't release artifact-based.
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 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 and influencing upstream projects leveraging the reference infrastructure,
(d) building new open source components source components within the reference infrastructure where needed,
(e) leveraging open implementations open implementations to drive an open standards and open-source-based ecosystem for NFV for NFV solutions,
(f) supporting supporting and maintaining the strategic framework of the Project the Project through the technologies made available by the organization to make the Reference the Reference Infrastructure testing, certification, and deployment a success.