TSC Meeting Minutes 2026-02-03

OpenFX TSC — Meeting Minutes

Date: Tue, Feb 3, 2026 (monthly)

Duration: ~1:00

Attendees:

Regrets / Unknown: Resolve/Blackmagic team

Topics & Notes

Gary reported solid progress on “property metadata” work:
- Vendor-specific/custom properties supported via vendor-shipped YAML.
- YAML-driven approach enables auto-generated documentation and language bindings (e.g., Rust/Go/Python) and reduces hand-maintained “dock”/metadata code.
- Type-safe property accessors improve correctness (type + dimension enforcement vs. runtime failures).
Discussion: where docs should live/how they should be generated if headers are built from YAML; and how suite docs relate to property docs (suites/functions documented explicitly; properties often implicitly documented via suite docs).

Main goal: define a minimal mechanism to identify the color space associated with a color parameter / picked color, without opening the “full color management can of worms.”
Consensus direction:
- Add a property indicating the color space of the color value (e.g., “is this scene-linear wide gamut vs Rec.709/sRGB-ish?”).
- For backwards compatibility, default behavior should be specified (team discussion leaned toward treating unspecified defaults as sRGB as the “historical assumption”).
- Define clear responsibility: host and/or plugin may set the property, but it must be consistent with the value being stored.
Implementation coordination:
- Paul to update headers / implementation.
- Gary volunteered to update a sample plugin once the header/property is in place.
Phil raised a concern about picked colors coming from host-defined spaces that may not map neatly onto the standard list; discussion stayed focused on keeping the initial mechanism simple (with “basic/core spaces” as a pragmatic option).

Gary noted he plans to push his clip/image metadata work soon; intended to unblock Paul’s work that depends on it.

Discussed as essentially “done/shipping,” but uncertainty about whether a PR exists / whether it has been formally merged.
Paul agreed to ensure the PR/status is moved forward promptly.

JP has not progressed since last discussion; he has notes to incorporate into the PR.
JP reported difficulty getting feedback from Blackmagic; after updating the PR, he plans to chase again.

Discussion touched on plugin placement and practical build ecosystem constraints (Classic ARM generally feasible; EC much harder).
Gary indicated he would update writeup/docs and circulate for review.

Noted an open PR (unique identifier) lacking reviews; Greg Cotton previously offered to test but no reviews have landed.
Reminder to the group to review low/no-review PRs to keep progress moving.

Gary Oberbrunner
- Break up and merge the completed portion of his property-metadata PR; continue work on the remaining suite work.
- Push clip & image metadata changes “soon” to unblock dependent work.
- Update ARM64-related documentation/writeup and send out for review.
- Update sample plugin(s) once the new color-space property/header change is in place.
Paul Miller
- Implement/land the agreed color-space property behavior for the color parameter / color picker (target mentioned: “tomorrow / within ~2 weeks” in discussion).
- Confirm the “base parameter interpolation type” work has an active PR and move it forward (create/refresh PR if missing).
- Push forward the “unique identifier” PR (solicit reviews / progress it toward merge).
John-Paul Smith
- Update the conformance-related PR with collected notes and re-engage Blackmagic for feedback after the update.
All
- Review open PRs regularly, especially those with no reviews, to help get changes merged.

Date: Tue, Mar 3, 2026 (monthly)