PROPOSAL - following feedback from the ONAP TSC 2019-02-07 the POC definition for Dublin

...

Proof of concept

Proof of concept (PoC) is a realization of a certain method or idea in order to demonstrate its feasibility,^[1] or a demonstration in principle with the aim of verifying that some concept or theory has practical potential.^{[citation needed]} A proof of concept is usually small and may or may not be complete.

The following are guidelines for a POC:

1. Every POC has a named sponsor for the feature whom acts as spokesperson at all checkpoints/meetings
2. POC (only) related defects cannot block the release
3. POC development that includes entry points in the release version must comply with license scans and vulnerability fixes
   1. A POC should not introduce a back-door to the stable features so it must comply with security, code coverage, and license scans requirements
4. POC features that are visible/accessible in the final product should be documented with limitations and POC status stated
5. A use case POC using common code, does not change the treatment of the common code with regards to completeness, S3P, documentation and other common code expectations
   1. Otherwise, POC should be kept in separate repo branch

==-=-=-=-=-=-=-=-=-=-=-CUT LINE, Previous content preserved for continuity... Delete after TSC review-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

POC is equivalent to "Tech Preview" or "Experimental"

...