Open-O Project Proposal Template Version 0.4 Reviewed Draft Chris Donley

Best Practices for successful proposal In order to ensure openness, new project proposals should include at least 3-4 organizations, including an operator Circulate draft proposals among the community to obtain feedback before submitting a proposal to the TSC The TSC will give preference to project proposals that are based on the existing functionality (vs. replacing such functionality with a new proposal) All code contributions must be scanned by the appropriate <TBD> open source audit tools to ensure the code is truly open source

Overview Project Name Repository name Project Description What is this project trying to address? Project Scope Describe problem being solved APIs/interfaces Testing and integration plans Features and functionality

Architecture Alignment How does this project fit with the Open-O architecture? Include architecture diagram How does this fit with external standards/specifications? APIs/interfaces Information/data models Are there dependencies with other open source networking projects? Integration testing Etc

Developers committed to the project Initial Committers Resources Contact person Developers committed to the project List developers, company, and contact info Initial Committers List Project roles (RACI chart?)

Describe plan for current release Release Plan Describe plan for current release Is this a Release 1 project, or are you targeting a later release? Minimum viable product Stretch goals Milestones Identified gaps Describe your longer-term roadmap

Link to seed code (if applicable) Vendor Neutral Other information Link to seed code (if applicable) Vendor Neutral If this proposal is coming from an existing proprietary codebase, have you ensured that all proprietary trademarks, logos, product names, etc. have been removed? Meets Board policy (including IPR)

Key Facts Project name: Repo name: Lifecycle state: Primary contact: Jira project name: Jira project prefix: Repo name: Lifecycle state: Primary contact: Project lead: Mailing list tag: Committers: foo@bar.com baz@qux.com

Appendix

Type/Degree of Participation Can Be Defined Responsible “Doer” Accountable “Buck Stops Here” Consulted “In the Loop” Informed “FYI” Individual(s) (Many) who perform an activity or take part in a decision—responsible for action/implementation. Individual (One!!) who has ultimate decision making and approval authority. Typically the owner of the budget. Individual(s) (Many) who need to have input into a decision or action before it occurs. Individual(s) (Many) who must be informed that a decision or action has taken place.

RACI Charting Maps Roles with Activities Functional Role: A position assigned or assumed to accomplish an activity or sub-activity A C I R C I C Activity: An action or decision that is one of several sequential steps in the completion of a business process. It should always result in a clear output I R A R A I A C A I R C A C R I

Region Employee Expense Statement Processing (Example) Participant Role Region Accounting General Accounting Activities Employee Secretary Supervisor 1. Document expenses AR 2. Complete expense account form AR R C 3. Forward to supervisor A R 4. Review C AR 5. Approve I AR 6. Forward to region accounting R A 7. Classify expenses C AR 8. Audit AR 9. Determine payment type C AR

Open-O Project Proposal Template Thanks Open-O Project Proposal Template