Uploaded image for project: 'tsc'
  1. tsc
  2. TSC-50

OpenFlow Plugin joining to Managed Release for Fluorine

XMLWordPrintable

    • Icon: Project Plan Project Plan
    • Resolution: Done
    • Icon: Medium Medium
    • None
    • None
    • None
    • None
    • NOT_Integrated (UnManaged)
    • Initial
    • SNAPSHOT_Integrated (Managed)

      Summary
      This is a request for OpenFlow plugin project to move from Unmanaged to Managed. This project is joining as a Managed project for the first time and has all intent to adhere to all the requirements of a Managed Project. 

      Project level facts can be found here:

       https://wiki.opendaylight.org/view/OpenDaylight_OpenFlow_Plugin:Main

      Healthy Community

      OpenFlow plugin project is one of the project from initial set of the project. From last 8 releases it's been an active project and we received contribution from various organization and individual contributors. Currently we have around 3 active contributors to the project. As a project PTL, i already started the process of cleaning up the committer list. In next one or two weeks time, we will cleanup the existing committer list and will invite more contributors to step up as a committer  to the project. 

      This project is been consumed by many downstream project and always maintained a active project status from the inception of this project.

      Responsiveness
      All the committers and active project contributors are currently subscribed to the mailing list, IRC, Jira and participate in the weekly meetings. Given that we have limited active contributor, responsiveness on all these channels is bit challenging, but we are currently working on improving it.

       

      Active Committers

      Currently we have 6 active committer who agreed to contribute to any 3 of the following work items

       Regularly attending OpenFlowpluing meeting ( Must for all committer)

       Participate in the technical discussion for the new features.

       Review the patches pushed to the  project.

       Contribute code (new feature, bug fixing).

       Respond to the mailing list  questions, bug request etc.

      Apart from that we are planning to groom some of the  existing active contributors to take committer role.

      TSC Attendance
      OpenFlow plugin project acknowledge that it will send a committer to represent the project to at least 50% of TSC meetings. Anil Vishnoi & Abhijit Kumbhare are the active committer to the project and they are active member of the TSC as well. 

      Checkpoints Submitted On-Time
      OpenFlow plugin project acknowledge that it will submit all the required checkpoints on time. They have a good history of  on-time milestone submission during the previous format of the release process and it's recorded in the docs project.

      Jobs Required for Managed Projects Running

      OpenFlow plugin project has an extensive set of CSIT test that cover the most of the user facing features of the openflowplugin project. List  of CSIT project can be referred at following URL:

      https://jenkins.opendaylight.org/releng/view/openflowplugin/

      Depend only on Managed Projects
      OpenFlow plugin project  currently depends on the following projects:

       AAA

       Controller

       MD-SAL

       Yangtools

       Netconf

      All the above mentioned projects are core managed project.

      Documentation

      OpenFlow plugin project already provide following user documentation :

      Developer Guide : 

      http://docs.opendaylight.org/en/stable-nitrogen/developer-guide/openflow-plugin-project-developer-guide.html

      http://docs.opendaylight.org/en/stable-nitrogen/developer-guide/openflow-protocol-library-developer-guide.html

       

      User Guide: 

      http://docs.opendaylight.org/en/stable-nitrogen/user-guide/openflow-plugin-project-user-guide.html

       

      OpenFlow plugin hosted documentation:

      http://docs.opendaylight.org/en/stable-nitrogen/submodules/openflowplugin/docs/index.html

       

      In Fluorine release, we are planning to improve the document in following aspect

       High level coverage of all the features provided by openflowplugin

       High level design document for the developers to understand the internal of the openflowplugin project.

       

      CLM
      OpenFlow plugin acknowledges that it will respond/act in timely manner to Component Lifecycle Violations issues reported related to the project. As per the last report from Linux Foundation, there was no critical CLM violation was reported. 

      https://jenkins.opendaylight.org/releng/view/CLM/job/openflowplugin-maven-clm-fluorine/

       

            dfarrell07 Daniel Farrell
            Avishnoi Anil Vishnoi
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: