Rather than establish a project for individual projects, the OPNFV community has agreed to work on establishing focus community groups where we will describe community engagement practices, identify community leaders, manage our contributions toward those communities and generally get ourselves organised well enough to be a benefit, rather than a burden, to our source communities.
In general, we would like to have a consistent process for feature requests across OPNFV projects. Since the bar in terms of structure and information seems to be highest for OpenStack, we will align feature request documentation on the OpenStack blueprint process. The process is defined for requirements projects.
However, in the case of Open vSwitch specifically, because there were a number of features which were eagerly requested by members, feature improvements for Open vSwitch are being tracked in the ovs-nfv project.
To facilitate the work of developers submitting features to Open vSwitch, we have instituted a process for requirements projects which consists of the following:
repository/requirements/reference_document.rst- this document should describe the goal at a high level for OPNFV consumers
All collaboration with the Open vSwitch community takes place via Open vSwitch mailing lists and the Open vSwitch IRC channel:
IRC: #openvswitch on irc.freenode.net
branch-X.Ye.g. branch-2.3 at https://github.com/openvswitch/ovs/tree/branch-2.3. The Open vSwitch maintainers backport bugfixes to these branches.
Open vSwitch is primarily licensed under the Apache 2 license.
[PATCH]and should also indicate the area of the code being modified and a brief description of the change.
Open vSwitch has a lightweight governance process for proposing and accepting new features.