Purpose

The OpenAssetIO working group steers the technical development of the project as it works towards its initial release. The aim is to ensure that its architecture and implementation choices facilitate easy and broad adoption within Media and Entertainment and beyond.

Membership

The working group is open to anyone who wishes to join, all meetings will be recorded and posted publicly after the event.

Meeting details

Zoom link: https://thefoundry.zoom.us/j/97582912679 Frequency: Every 4 weeks on Thursday Add to Calendar: Calendar Invite

---

February 11th 2022

Date/Time: 11th February 2022 @ 17:00 GMT

Agenda:

---

January 10th 2022

Meeting Slides

Date/Time: 13th January 2022 @ 17:00 GMT

Discussion Points

• Quick overview for new faces
• Progress update
• Upcoming Milestones
• CY22 or later?
• C++/Python bindings and memory management
• Considerations when binding to other languages

Notes

Overview of where we are with project (see slides)

Q: Does it contain a resolver?

• No - just specifies how information should be shared

Discussion: Where should communication take place?

• Slack & Discord not open, the more open the better,
• Conclusion: Discussion on the repo is probably best but it also depends on the type of thing that people need/want to post.

Q: Is there a plan to move to ASWF?

• Plan to move officially to ASWF at some point, currently just with Foundry

CMake Discussion

• Recommend always working default variables rather than custom otherwise huge overheads supporting customers

CY2022/Python Discussion

• Happy with CY2022 only
• Please not Python 2 - that is going backwards
• 3.9 is the only python version that reliably works on Windows

Nick presentation on OTIO difficulties with languages

• Raymond: Are we trying to optimise the experience of the developers or integrators as that will have a bearing on the route we should take

Which languages feel best for people?

• MovieLabs, PoC in a mix of Python and Javascript in Node. Member studios are all over the map but Python is at the top.
• Pixar: C++ and Python. C is a good shimming system, great lowest common denominator between the languages.
• Blender is pretty much Python-only when it comes to add-ons / 3rd-party tools. Blender itself is made in C and C++, and uses various libraries in those languages. They precompile those libraries for the major platforms with GCC, it's usually not much of an issue to integrate a new library.