Hi all. I’ve used node compositors for years in a color and aerial
cinematography workflow, and I write C++/Qt for a living. I’d like to put
real hours into Natron, starting with the least interesting part of it.
My read from the outside is that the build is the bottleneck. CONTRIBUTING
rates building locally as harder than fixing a bug, Travis sits disabled in
the tree, and the README badges point at CI that hasn’t run in years.
Nothing else moves until that’s sorted.
What I’m proposing, in order. Build RB-2.6 on Windows and Linux and correct
the INSTALL docs wherever they’re wrong. Stand up GitHub Actions with a
build matrix covering Linux, Windows, and macOS. Then, if the maintainers
want it, cut a tag from the fixes that have accumulated on RB-2.6 since
2.5.0.
I’m not promising a Qt6 port. I want to understand the Shiboken situation
before anyone says that word out loud. My hours are evenings and weekends,
so I’d rather commit to a narrow scope and finish it than announce
something large and stall.
One thing I can’t answer from the repo: is CMakeLists.txt meant to replace
Project.pro, or was it an experiment that stalled? That changes the order
of everything above.
Who’s still reviewing pull requests, and which branch do you want them
targeted at?