Today, the ASWF TAC voted to admit OIIO as an ASWF project. Over the coming weeks, there will be some minor gymnastics for everybody as we switch the repo and mail list to be under their organization, request that people sign a new CLA, and other such housekeeping. We'll keep you informed of any steps you need to take on your end.
One thing we need to do is assemble the technical steering committee. Robin Rowe has already stepped forward with an offer to participate and in particular to be the Windows and cross-platform build czar. Weta, Animal Logic, Autodesk, and NVIDIA have all made positive noises about participation with names penciled in or TBD. This is a good time to look into your organizations and ask yourself if you are a significant stakeholder (using it, dependent on it, caring about what gets implemented and future direction, at risk if the project is under-resourced), and if so, or if you would like to be, then this is the time to step up and put somebody forward as an ongoing participant and/or TSC member. The time commitment is not necessarily very large. The bare minimum would be attending an every-2-weeks Zoom TSC meeting, and trying to follow and participate (when you have the expertise) in mail list and issue discussions, comment on PRs, etc. Medium level would be an intent to spend a few hours a week to help with maintenance and implementation. High level would be to take primary ownership of a particular technical or code area or to work on a major feature (that is to say: there is something big YOU need or wish was in OIIO, and you're going to take a stab at doing it). Take the step up from being a user to being a contributor to being an owner. If you think you're up for it, just let me know and I'll make sure you're on all the right comms. -- Larry Gritz l...@larrygritz.com
_______________________________________________ Oiio-dev mailing list Oiio-dev@lists.openimageio.org http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
