Hi @noonedeadpunk, we can help you with any details you need.
The collection, as mentioned in this thread, is deprecated and is planned to be archived after December 2025.
I’ll follow up with more details regarding ownership transfers.
Regards.
2 Likes
+1 to Sagar’s note.
We’re currently reviewing the ownership requests and will share more information here as things progress.
1 Like
@KB-perByte so pretty much we want to ensure that collection is working and compatible with relevant ansible, python and openvswitch versions, to keep it basically in maintained state.
Alternatively we were considering forking it and publishing to a different namespace, however our projects and governance are all licensed with Apache 2.0, so having GNU GPL licensed code withing is not great, so we’d rather avoid it.
We are ready to start working on it, if there is somebody around to review patches and/or onboard. So I guess main question would be - if we should try getting current collection maintained, or rather you would suggest going through forking right away?
If people that are interested in helping with the openvswitch Collection reply with their GitHub account I can grant you write on the repo.
Feel free to start a new Forum Post with ideas for next steps. If we get that added to The Bullhorn and mentioned in the Collection’s readme we can attract new contributors
Yes, sure:
We’re working on different orgs, but agreed to collaborate on maintenance of the collection, so diversity concern is also being addressed here 