[TSC-47] SFC joining Managed Release for Fluorine

Thu, 5 Apr 2018 17:35:52 +0000

Summary

This is a request for the ODL Service Function Chaining (SFC) project
to join as a Managed project for the first time in the Fluorine release.

Healthy Community

The ODL SFC community has been healthy since its inception in the
Helium release. The SFC project can be contacted and tracked using
the following means:

Project Wiki: https://wiki.opendaylight.org/view/Service_Function_Chaining:Main
Email list: sfc-dev@lists.opendaylight.org
IRC channel: Freenode: #opendaylight-sfc
Regular meetings: https://wiki.opendaylight.org/view/Meetings (look for Service Function Chaining)
JIRA: https://jira.opendaylight.org/projects/SFC

Further evidence of the project's health is detailed in the following sections.

Responsiveness

The SFC project has been responsive to all manner of requests since
its beginning. One of the project's committers always replies to emails
and the project has always been timely completing milestones and
release deadlines. The weekly project meetings are open to anyone
and are held every week and are only cancelled for holidays or travel.

Active Committers

The SFC project has always had a healthy list of active committers
that are constantly reviewing and merging incoming patches, supporting
potential contributors, keeping CSIT healthy, and generally keep
SFC up-to-date and relevant. The project has individual committers
as Primary contact, Testing contact, and Documentation contact.
We are constantly pruning inactive commiters to keep the committer
list up-to-date.

TSC Attendance

The SFC project currently has a committer on the TSC, and generally
tries to have a representative active in the TSC and its meetings.

Checkpoints Submitted On-Time

The SFC project acknowledges the requirements for managed project
checkpoints and we confirm that we will be timely in submitting checkpoints
as is required for managed projects. The SFC project has a demonstrable
history of being on time submitting release milestone reports and completing
end-of-release requirements.

Jobs Required for Managed Projects Running

The SFC project maintains the following jobs that are required for Managed projects:

Distribution check job (voting)
- https://jenkins.opendaylight.org/releng/view/sfc/job/sfc-distribution-check-fluorine/
Validate autorelease job (voting)
- https://jenkins.opendaylight.org/releng/view/sfc/job/sfc-validate-autorelease-oxygen/
Merge job (non-voting)
- https://jenkins.opendaylight.org/releng/view/sfc/job/sfc-merge-fluorine/
Sonar job (non-voting)
- https://jenkins.opendaylight.org/releng/view/sfc/job/sfc-sonar/
CLM job (non-voting)
- https://jenkins.opendaylight.org/releng/view/sfc/job/sfc-maven-clm-oxygen/

Depend only on Managed Projects

The SFC project depends on the following projects:

controller
mdsal
yangtools
odlparent
openflowplugin (flow programming and extensions)
ovsdb (ovsdb southbound)
genius (ifmgr, idmanager, mdsalutils)
lispflowmapping

Documentation

The SFC project acknowledges that it will continue to maintain and
produce a user guide, developer guide, and release notes for each
release. Links to these documents for all of the past releases can
be found on the SFC project Wiki. The SFC project has a Documentation
contact who organizes the documentation responsibilities for each
release.

CLM

The SFC project acknowledges that it is required to handle Component
Lifecycle Violations in a timely manner. The project has always handled
the violations in a timely manner in the past.

OpenDaylight JIRA