Project Proposal Process Overview
A shout-out to @Chris Donley for much of the content found here
What is a project?
IS / HAS | IS NOT / DOES NOT |
---|---|
|
|
The basic steps for submitting a proposal
Talk to community members first about the problem you think needs to be addressed.
Fill in the template by clicking the create button in the "Draft Project Proposals" section of the wiki
Meet with the Architecture subcommittee for an initial review
Address any concerns raised by the Architecture subcommittee scheduling a follow-up review if necessary
A MINIMUM OF 2 WEEKS PRIOR TO MAKING YOUR PRESENTATION TO THE TSC your submission should be considered to be locked. Nothing else should be added or changed from that point on.
Add your proposal presentation to an upcoming TSC agenda at least two weeks in the future (you can do that yourself)
Move your proposal from Draft Project Proposals to New Project Proposals
Send email to tsc@lists.onap.org notifying the community that it has been posted and include a link to the proposal
The TSC considers many things when they look at approving a new project
Technology for the sake of technology won't cut it, neither will solutions in search of problems.
Is your project addressing a real problem in the industry?
How does this affect other projects?
Does this advance our architecture?
How does this fit with the next release? How about R+1 or 2?
Does it increase our risk of delivering on time?
Does it support multiple use case scenarios?
Do you have enough resources?
Are those resources new, or are you drawing resources away from other projects?
Will this project make ONAP more attractive to service providers?
Would this simplify or complicate end user adoption?