toggle quoted messageShow quoted text
The Sony configs are heavily referenced in the present documentation (the only place where real OCIO usage is described) so until a new user-story is put forth they should remain accessible.
I'd wait to hear from The Foundry reps on whether the nuke-default should exist there or not. If it's still useful I don't think it's causing harm.
The onus is certainly on OCIO v2 Docs to learn from OCIO v1 and provide clear and obvious modern use cases and implementation references.
I don't think the tags/releases would pollute the ecosystem too much and provided a very simple link-able way for end-users to avoid ever touching git, which was my intent.
Doing this also drops the download size quite a bit because you aren't pulling down all of time when you download the zip, or even git clone from master.
To be fair, at this stage, I don't think it hurts to leave them as they are.
To some extent, the SPI Gospel is what tipped the balance on my end to improve the shaper, if people did not do comparisons with it recently, maybe I would not have done it :]
I had the same quibble about the version number on the folder. I said to myself that while not super elegant, it was no big deal and would actually help non-techie users to know exactly which config they get. I must admit it is itching a bit :)
Comments on II #3
- Why even include the nuke-default? Those are the configs from Nuke 6.3 when OCIO was first implemented in Nuke 7-8 years ago, wildly out of date compared to what ships with the software.
- Same with both Sony examples, also wildly out of date compared to what is used internally at Sony (unless they contribute new ones as examples).
- I have seen many people use the Sony configs as gospel when they should perhaps be looking at the ACES config instead as an example.
- minor quibble: Why include the ACES version number in the folder name, this should be representative of the tag, not the folder name.
Crossing fingers for things to move forward! I cannot say we have not tried :)
A few comments:
I.1: As mentioned in https://github.com/imageworks/OpenColorIO-Configs/pull/17
, I'm fine with whatever license is chosen, and HP said that his work was done under the Academy Umbrella thus the Academy license should apply, so there should not be a problem fixing that.
I.3: Are you referring to the 2.2, 1.8 and Venice recent discussions?
II.3: Sounds good! Although we should drop some tags/releases, it is excessively confusing currently and because Github cannot render the diffs it makes the experience a bit traumatic.
III.1: Sounds good too, I'm assuming that the AMPAS drives it?
I would need to think about the minute details but seems like a good plan to me, I like it :)
On Tue, 1 Oct 2019 at 14:21, Sean Cooper <sean@...
I know this is coming from a long and storied past but we (the OCIO TSC), high on the spirits of migrating our repo to the ASWF, would like to once and for all come to a resolution on the OCIO + ACES dilemma.
There are a number of issues that are rolled under this banner and by no means can they be (or should they be) resolved in this email thread, but I will do my best to lay them out as they are...
As the world exists today:
- Due to HP's and Thomas's contributions to the OpenColorIO-Configs repo not being licensed, they are unable to be carried over to the ASWF as-is
- The ACES 1.1 OCIO configs, due to various factors, have yet to be merged into the SPI OpenColorIO-Configs repo and yet, are already seeing active use
- There will likely be multiple versions of the ACES 1.1 OCIO config in existence due to continued discussion about what should be included and the names they are given
- Ownership of the ACES OCIO configs presently sits outside of both ACES and OCIO (though the contributors are closely involved with both projects)
- The OpenColorIO-Configs repo size has become a burden to work with
A step towards tomorrow:
- The ACES OCIO Configs should be assigned a license
- The ACES 1.1 config should be merged to Master as-is
- Updates pushed and versioned as-per the next bullet
- I propose a repository structure such as can be found in my fork (https://github.com/scoopxyz/OpenColorIO-Configs)
- All old ACES configs are removed from master
- Dedicated ACES configs branches and tags will be created
- The dedicated ACES config tags will have a secondary version number
- All users of the configs should be pointed to the Release zips
A path to the future:
- An ACES virtual working group should be formed to outline the clear path of the ACES OCIO configs
- A new-breed config repository should be crafted to move under the ASWF
- Clear license inherited from ASWF
- All Configs and LUTs must be generated by CI as artefacts
- Repo structure and artefacts must account for:
- External Versioning (e.g. ACES)
- Internal Versioning (e.g. naming changes)
- OCIO Versioning (e.g. utilising v2.x features)
As a general summary I personally don't think the OpenColorIO-Configs repo, as it exists today, should be merged to the ASWF at all. Instead, we really do need to build a fresh slate and a new way of thinking about creating and distributing OCIO Configs (both ACES and non-ACES). This should happen as a new wave of development.
I think its quite clear the present Imageworks Configs repo and its configs should (and will) continue to be supported while future development happens.
Please let me know your thoughts, and please start a new thread if your topic of discussion warrants in-depth conversation (such as the ACES Working Group). Or please continue the conversation on the relevant GitHub PR: