Versions Compared

Old Version 3

changes.mady.by.user Kenny Paul

Saved on

compared with

New Version Current

changes.mady.by.user Kenny Paul

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

A shout-out to Chris Donley for much of the content found here (smile)

WIP  Kenny Paul

What is a project?

IS / HASIS NOT / DOES NOT
  • A long term endeavor to deliver features across multiple releases
  • Rationalized based upon clear technical and industry benefits
  • Has a clearly defined scope that can be leveraged across many use cases
  • Requires a dedicated content repository
  • A community which acts collectively as a single development entity 

  • Has Committers with expertise in the relevant areas

  • Intended for a single ONAP release 
  • Rationalized based upon convenience for an individual entity
  • Scoped broadly or a collection of unrelated items to satisfy a single use case
  • Something that can exist without having a dedicated repo
  • A fully self-contained internal development team
  • Require Committers with different expertise 

...

titlePro Tip

...


The basic steps for submitting a proposal

...

  • 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?


Info
titlePro Tip

The TSC will always look more favorably on project proposals that address gaps in existing ONAP functionality vs. replacing existing  functionality with a new proposal.  

Best Practices for successful proposal

...