Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

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
  • 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 use case
  • Something that can exist without having a dedicated repo
  • A fully self-contained internal development team
  • Require Committers with different expertise 

Pro Tip

The TSC will always give preference to project proposals that address gaps in existing ONAP functionality vs. replacing existing  functionality with a new proposal.  


A project proposal should answer six fundamental questions:

  1. WHO will be doing the work?
  2. WHAT do you propose doing?
  3. WHEN do you plan to deliver it?
  4. WHERE will you put your deliverables? 
  5. WHY should we consider doing this?
  6. HOW does this fit into our architecture?

Best Practices for successful proposal

  • Always remember this is an open source community, not contract labor. 
  • Participation of at least 3-4 organizations, including at least one operator (preferably more)
  • Circulate draft proposals among the community to obtain feedback before presenting to the Architecture subcommittee
  • Address any concerns raised by the Architecture subcommittee before getting on the TSC agenda
  • Post your proposal draft on the wiki under “Proposed Projects” section at least two weeks in advance of your TSC presentation date
  • Send email to tsc@lists.onap.org notifying the community that it has been posted


Pro Tip

Being open to feedback gives you credibility. There will of course be disagreements on solutions or approaches, but anyone that feels you are ignoring their input is unlikely to consider working with you on anything either now or in the future . If you hear an objection or concern that cannot be addressed by your proposed solution it is in your best long-term interest to respectfully highlight it publically and then provide the technical reasoning or logic that went in to your decisions.    


Filling out the proposal template

As you go through the template here are the things to keep in mind. These are typical of the questions that you get asked over and over.

The Overview section

  • What is the problem?

    Why can’t it be solved in existing projects?

    How do you propose we solve it?

  • No labels