Mazin and TSC members, Nice job on the"rubrick" for evaluating the proposed projects. It will make sure that the contributions with the most interest, support and relevance with the least risk make the first release.
Chris Sent via the Samsung Galaxy S8+, an AT&T 4G LTE smartphone -------- Original message -------- From: "GILBERT, MAZIN E" <[email protected]> Date: 5/18/17 8:15 PM (GMT-06:00) To: onap-tsc <[email protected]>, [email protected] Subject: [onap-tsc] Framework for proposed projects feedback ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. ONAP Team, I want to thank you again for working so hard in proposing projects. Per our TSC meeting today, I am enclosing the framework that the TSC committee developed for scoring and providing feedback on each project. I expect you will get feedback from the TSC committee starting next week. Thanks Mazin Framework for TSC Project Feedback 1. Clarity a. Reasonable and well defined scope b. Identification of software modules and APIs being developed and delivered to ONAP and other components. c. Following project and LF guidelines for contributors/committers d. Identification of dependencies and assumptions on other components and open source. 2. Overlap a. Intentional and unintentional overlap b. Overlap with external open source efforts 3. Risk management a. Sufficient development resources allocated to deliver on time b. At least 3-4 companies involved to provide diversity c. Availability of seed code and its maturity 4. Relevance and prioritization a. Alignment with merger release b. Alignment with use cases c. Sound technical solution for solving a real need
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
