During the last years OpenVswitch and OVN have become a major dependency for several projects and SIGs in the CentOS ecosystem, including OpenStack, oVirt and OpenShift. During this time each project has been following its own way with limited coordination (just some opportunistic cross-tagging between SIGs) and different approaches, rebuilding Fedora builds or FDP srpms from ftp.redhat.com from time to time in their own tags and repos.
This has led to multiple issues and suboptimal usage resources so I think a good step ahead would be to use existing NFV SIG  as a collaboration area for all the interested projects to build, test and ship OpenvSwitch and OVN using public SRPMs from Fast Datapath .
What I'm proposing is that the interested people in becoming maintainers for OVS/OVN in NFV Sig request membership to nfv-sig group . Then, we'll coordinate to request new tags/buildroots for OVS/OVN and start building and testing the required releases.
This proposal has been sent to ML  with no response, so I'd like to get feedback about the right way to move on with it.
As per https://lists.centos.org/pipermail/centos-devel/2020-July/037049.html Alfredo has indicated willingness to assume the Chair role.
Discussed in the July board meeting, and Alfredo's move to SIG Chair was unanimously approved.
What are the next steps?, I'm not sure if SIG chairs have any special permissions in CAS or if i need to register me as chair somewhere. I'd like to propose a meeting to discuss SIG new goals, roadmaps and members asap.
@rbowen amoralej is still not approved in https://accounts.centos.org/group/members/sig-nfv/
Could he as new SIG Chair get "sponsor" permission so we can get NFV SIG going?
@rbowen so @amoralej was approved but only with "user" Role, why do SIGs need to rely on CAS admins to approve new members?
This is completed now, right?
Yes it's completed and can be closed.
Metadata Update from @rbowen:
- Issue status updated to: Closed (was: Open)
to comment on this ticket.
SSH Hostkey/Fingerprint | Documentation