Video Conference Link

Attendance

  • Cory Omand - WG Chair, Pixar/TWDS
  • Alan Blevins, Dreamworks
  • Alex Schwank, Apple
  • Aloys Baillet, Animal Logic
  • Andy Biar,  Warner Bros.
  • Ben Chung-Hoon, Google
  • Bill Spitzak, Dreamworks Animation
  • Brian Green, Dreamworks
  • Carson Brownlee, Intel
  • Charles Fleche, Rodeo FX
  • Chris Rydalch, Blue Sky Studios
  • Daniel Heckenberg, Animal Logic
  • Dhruv Govil, Apple
  • Eoin Murphy, Animal Logic
  • Eric Enderton, NVidia
  • Francois Lord, Rodeo FX
  • Gary Jones, Foundry
  • Gordon Bradley, Autodesk
  • Henry Vera, DNEG
  • James Pedlingham, Foundry
  • Jeff Bradley, Dreamworks
  • John Hood, SPI
  • John Mertic, Linux Foundation
  • Jordan Soles, Rodeo FX
  • JT Nelson, Pasadena Open Source Consortium/SoCal Blender group
  • Kimball Thurston, Weta
  • Larry Gritz, SPI
  • Lee Kerley, SPI
  • Mark Elendt, SideFX
  • Mark Final, Foundry
  • Mark Tucker, SideFX
  • Matthew Levine, WDAS
  • Michael B. Johnson, Apple
  • Michael Kass, NVidia
  • Michael Min, Netflix
  • Niall Redmond, Foundry
  • Nick Porcino, Pixar
  • Pilar Molina Lopez, Blue Sky Studios
  • Pier Paolo Ciarravano, MPC
  • Robin Rowe, CinePaint
  • Roman Zulak, SPI
  • Rory Woodford, Foundry
  • Sean Looper, AWS
  • Sean McDuffee, Intel
  • Serguei Kalentchouk, Apple
  • Shawn Dunn, Epic Games
  • Sue Sauer, Sunrise Productions
  • Richard Lei, Weta
  • Toby Jones, Walt Disney Animation Studios

Minutes

  • Cory: Note about meeting recordings. Group is happy with current approach: meetings are recorded for reference but recordings not published or broadcast.
  • Action item follow-up [0:00-0:10]
    • Contribution guidelines for knowledge base
    • CoryO: current github repo requires DCO signoff for commits. Is this too restrictive?
    • JohnM: Best practice in other groups is to treat documentation as software via markdown etc. with contribution licences etc. This is particularly important for materials that may need to be shared.
    • MichaelK: This will create friction for small and frequent contributions. Has USD team given a position on whether it would be acceptable to have a more broadly edited (and possibly occasionally inaccurate) wiki?
    • CoryO: USD team intends to expand documentation with versioning against USD releases, including FAQ. They are happy to have a companion, public FAQ / knowledge base.
    • CoryO: Is Creative Commons a suitable licence?
    • JohnM: Have to ensure the IP model is compatible with ASWF.
  • Platform for contribution (github wiki, something else?)
    • JohnM: Has now switched github wiki permissions to allow public edits
  • Knowledge Base Category Brainstorming (Alan) [0:10-0:40]
  • Closing/Action Items [0:40-0:50]

Action Items

  • IPython/Jupyter notebook integration (JT)
  • Take a stab at github wiki categories (Cory)
  • Contribution license (CC) on front page of wg-usd (Cory/John)
  • Samples/notebooks area in the repo (Cory)
  • Integrate build club and other resources into wg-usd KB wiki (Nick)
  • No labels