November 28, 2022

Host: Carol Payne

Secretary: Carol Payne

Attendees:

  • Rémi Achard (TSC) - DNEG

  • Mark Boorer (TSC) - Industrial Light & Magic

  • Mei Chu (TSC) - Sony Pictures Imageworks

  • Sean Cooper (TSC ACES TAC Rep) - ARRI

  • Michael Dolan (TSC) - Epic Games

  • Patrick Hodoul (TSC) - Autodesk

  • John Mertic - Academy Software Foundation / Linux Foundation

  • Carol Payne (TSC Chair) - Netflix

  • Mark Titchener (TSC) - Foundry

  • Carl Rand (TSC) - Weta Digital

  • Doug Walker (TSC Chief Architect) - Autodesk

  • Kevin Wheatley (TSC) - Framestore

  • Name - Organization

Apologies:

  • Name

OCIO TSC Meeting Notes

  • Committer privileges for Cedric Fuoco
    • Instrumental in 2.2, will also be for 2.3!
    • No objections from the TSC, Doug will open the GH issue
  • Install instructions
    • Doug has been working on documentation for 2.2 / out of date info
    • install instructions page is very out of date at this point
    • Wondering if we can clean up some of the cmake instructions/options
    • Might be hard to standardize, as cmake itself is not really standardized in default options
    • Simplest thing would be if we stopped pulling dependencies for people, but not sure how that would be received
    • USD uses a python script for building, instead of trying to put all the smarts in cmake itself
    • Mark votes to leave it as is and use resources elsewhere - leave any major updates for a new cmake version upgrade, etc
    • Doug - keep an eye out for the PR for updated documentation, please take a look and make sure it's not missing anything
  • VFX Industry build matrix
    • Mark - hard to make these overall version lists, as every project is different and it's own island
    • Kevin: we should approach it from "what does OCIO want to support" and then use the list to see what everyone is needing, and figure out what we need to do to get there
    • Also, what do we mean by support - does that mean it must be in our CI build matrix? As we have only limited amounts of builds - think it's 20?
    • What's supported in CI is not what we actually support - CI is for developer workflows to make sure they're not breaking 
    • What we support is the core workflows and what we as OCIO depend on 
    • We haven't technically stopped supporting old versions of OCIO, we could make patches if we need to
    • More about what we continue to support in new versions of OCIO - i.e. do we need to continue to support old C++ versions, etc
    • We are limited on CI builds, but we can always add more for nightly builds and wheels
    • We should likely test ninja in CI
  • Should we move VFX RP 2019 out of our CI builds to make room for 2023?
    • Michael: yes, 4 years of support seems adequate 
    • There's an issue open for GH actions to support apple ARM - no ETA yet (https://github.com/actions/runner-images/issues/2187)
    • We should put together a spreadsheet of our current CI build matrix (Doug will create a sheet)
    • Find out the status of the 2023 docker container (Carol will ask at TAC meeting)
    • At some point we should remove the java bindings
    • Also the Nuke node examples etc
  • TSC Member update:
    • Do a round of new member proposals Jan 2023
    • Talked about current list, and making sure members are still willing to participate and up to date
  • 2.2.1 update - still would like to do, whether it happens EOY or early next is up for debate
    • Build fixes and bug fixes, nothing major but good to do regardless
  • Items for next meeting agenda:
    • Info
  • No labels