RFC: Moving the srt plugin to -good
Hello!
We (the good people at Spiideo) are using the SRT plugin in our stack, both as a sender and receiver, to ingest audio/video to our processing nodes, and we also use it as a means to send data out from our processing to consumers. The state of the plugin matters to us.
Getting the plugin from gst-plugins-bad
to gst-plugins good
is something we are willing to spend some time on.
Why?
- Finding out if there are any known issues out there that people are anxious about
- Getting some eyes on what might be missing in the plugin
- Making sure documentation is up-to-date
- Getting some critical eyes on the test needed to feel good about the plugin
- Not having to explain to management types why we are using bad stuff
From subprojects/gstreamer/docs/random/moving-plugins:
PROCESS
-------
- Issue in gitlab gets filed by someone requesting a move from bad
to good/ugly
This is "requesting" the move.
- a second person reviews the request and code, and verifies that the
plugin meets the checklist items below, by commenting on the bug
and giving a rundown of what still needs to be done
This is "sponsoring" the move.
- when the checklist is met, a third person can approve the move.
This is "approving" the move.
- an admin performs the move.
This is "performing" the move. (Are you laughing yet ?)
We are willing to put in work to raise the quality of the plugin to where it needs to be for a move to make sense. Is there anyone out there with some bandwidth to "sponsor" this by helping us getting the rundown of what needs to be done?
Reading the checklist from subprojects/gstreamer/docs/random/moving-plugins I see there are some more work to be done on unit-test and manual tests, but there are probably more things to be done.
The srt library used seems to be MPL 2.0: https://github.com/Haivision/srt
Is this worthwhile? Is this wanted? Is this madness?
All the best