Have questions? Stuck? Please check our FAQ for some common questions and answers.

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

Compare with Current View Page History

Version 1 Next »

 This section describes the steps needed for submitting a new feature or project proposal.

Types of proposals

Proposals are classified into the following types:

  • The proposal is related to Core ONOS modules
  • The proposal is for an external module or application or product unrelated to ONOS core.

Steps

1. Create a feature request in JIRA. Please select the type as "New feature".

 

2. Add "proposal" in the Labels field in JIRA and add the time estimate in the "Original Estimate" field.

In the Description field in JIRA (see above), add the following details:

  1. Problem statement
    1. Use case or requirements
    2. The problem it is trying to solve
    3. Other alternatives that exist and why they are not adequate
  2. Implementation design
    1. Pointers to documentation containing design and component changes
  3. Testing needs of the proposal
    1. End user impact
      1. API changes
      2. Configuration changes
      3. Debugging changes
      4. Other changes
    2. Work items:
      1. High level list of tasks along with approximate time estimates.
  4. Dependencies
    1. Assignees:
      1. Proposal Point of contact: Name/email
      2. Will this project be driven externally by a single or group of organizations? If yes, provide details.


You can view all the submitted open feature requests and project proposals through the quick filter "New Features" at the top of the ONOS Project in JIRA.

3. The ONOS releases steering team and the ONOS product owner will review the feature requests/project proposals and determine next steps. Every new feature request should be reviewed and the next steps for it should be determined in, at a maximum, 1 month from the date of submission.

  • No labels