Summary
This is a request for OVSDB project to join as Managed for Flourine release.
Healthy Community
OVSDB Project has been a part of ODL community since inception and has active community adding features and fixes in every release.
Responsiveness
All active committers are active on IRC, mailing list and Jira. OVSDB meeting is clubbed with the Netvirt meeting as Netvirt was spun off from OVSDB as separate project.
Mailing List: https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev
IRC Channel: #opendaylight-ovsdb
Active Committers
List of committers can be found at:
https://wiki.opendaylight.org/view/OVSDB_Integration:Main
All committers listed as Active Commiters are still active and highly responsive in community.
TSC Attendance
OVSDB has always had at least one committer present in TSC meetings and will continue to do so going forward.
Checkpoints Submitted On-Time
OVSDB project acknowledges that we'll be required to submit checkpoints on time. OVSDB project has a history of submitting checkpoints on time and will continue to do so.
History of checpoints during Oxygen is available at http://docs.opendaylight.org/en/latest/release-process/milestone-readouts.html
Jobs Required for Managed Projects Running
All required jobs are in place and can be seen at:
https://jenkins.opendaylight.org/releng/view/ovsdb/
Depend only on Managed Projects
OVSDB project depends on core projects only.
Documentation
OVSDB Project acknowledges that it is required to produce a user guide, developer guide and release notes for each release. The request may also highlight a history of providing quality documentation. Existing documentation links:
Developer Guide: http://docs.opendaylight.org/en/latest/developer-guide/ovsdb-developer-guide.html
User Guide: http://docs.opendaylight.org/en/latest/user-guide/ovsdb-user-guide.html
Release Notes: http://docs.opendaylight.org/en/latest/release-notes/projects/ovsdb.html
CLM
OVSDB Project acknowledges that is required to handle Component Lifecycle Violations in a timely manner.