Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

March 20, 2023

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

  • Zach Lewis - Method Studios
  •  

Apologies:

  • Mark Titchener

OCIO TSC Meeting Notes

  • Config merging feature
    • Slides for reference:
    • Reference issue: #1359
    • This is a frequently requested issue, and Doug & Cedric from Autodesk are considering starting work on this feature next in their dev roadmap.
    • Kevin - cases 1 and 3 are user requirements, but 2 is application-based (allow applications to include required colorspaces)
      • Would NOT want applications to merge configs automatically based on start up
      • Config author should have control over config merging
      • Mark - agree. This is a large amount of complexity for not a lot of gain - these things are already possible by using current OCIO features, just need to learn
        • Doug - agree on complexity, we need to make sure we treat this carefully - most things would be added to appHelpers or a command-line tool
      • Micheal - could see this being useful to avoid duplication in applications for sure
      • Doug - applications can publish a default config, with their required spaces, and then the facility/author could have control over what gets merged when
    • Mark - adding a colorspace etc is one thing, but the rest - roles, search paths, etc is quite another
    • Doug - don't really think it's as complex as it sounds - but understand the hesitation.
    • Carol - maybe let's table this for now, give folks a chance to peruse the slides and think some more, and bring it back at the next meeting. Please post concrete thoughts on the issue or on the slides, not on slack, just to make it easier for tracking.
  • Google Season of Docs Application Proposal:
    • Please provide feedback on our proposal, here:
    • Deadline is friday, feedback by wednesday please!
    • Carol following up with John Mertic re: budget estimates
  • Dedicate some TSC time to review open issues?
    • Sure, sounds good.
    • First step - do an overall github issue prune
    • Then build a curated list of issues at the top of the agenda
    • Build time into the agenda to discuss open issues each TSC
    • Remi - could use the discussion feature on github, some orgs ask folks to open a discussion first, and then promote worthy things to issues
  • No labels