You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We will keep the current builds of the adapters alive in PyPI so users may still explicitly install them - they just won't be in the "batteries included" release. Should security issues emerge, we may however decide to remove them from PyPI.
Reasoning
The HLS playlist adapter was something I’d built for a previous use case that’s heavily dependent on including some custom metadata fields and only generates one specific (and probably less-common) flavor of HLS playlist. I'm not aware of its active use anywhere.
The FCP X XML adapter does not have an active maintainer and is in need of some serious attention to be usable in a lot of cases. I’ve had reports of people trying it and thinking OpenTimelineIO is broken because timelines aren't correctly translated. In its current form, I think it may be causing more confusion than utility.
The Java bindings were something we at Netflix advocated for. Since then, our need for them has diminished and we’re having great success using the python bindings. These bindings are pretty far behind the OTIO core implementation and without someone with clear interest in maintaining them, it’s probably most responsible to mark them as archived until someone wants to take up support.
For any of these repositories, if a community maintainer wants to step-up and get them into shape we could consider unarchiving and accepting a PR that brings them up to standards.
These decisions are not final and I'd very much like to hear community feedback.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all - I’d like to propose a few changes related to adapters and bindings and would like to hear thoughts from the community on them.
Remove the following adapters from inclusion in the opentimelineio-plugins package:
Mark the following repositories as archived in github:
We will keep the current builds of the adapters alive in PyPI so users may still explicitly install them - they just won't be in the "batteries included" release. Should security issues emerge, we may however decide to remove them from PyPI.
Reasoning
The HLS playlist adapter was something I’d built for a previous use case that’s heavily dependent on including some custom metadata fields and only generates one specific (and probably less-common) flavor of HLS playlist. I'm not aware of its active use anywhere.
The FCP X XML adapter does not have an active maintainer and is in need of some serious attention to be usable in a lot of cases. I’ve had reports of people trying it and thinking OpenTimelineIO is broken because timelines aren't correctly translated. In its current form, I think it may be causing more confusion than utility.
The Java bindings were something we at Netflix advocated for. Since then, our need for them has diminished and we’re having great success using the python bindings. These bindings are pretty far behind the OTIO core implementation and without someone with clear interest in maintaining them, it’s probably most responsible to mark them as archived until someone wants to take up support.
For any of these repositories, if a community maintainer wants to step-up and get them into shape we could consider unarchiving and accepting a PR that brings them up to standards.
These decisions are not final and I'd very much like to hear community feedback.
Beta Was this translation helpful? Give feedback.
All reactions