Ondřej Samohel

If I may add to the discussion - this is probably similar thing (in concept) as the one we already have for Maya/Nuke and that is scriptsmenu support. I agree...

or not. :) can you resolve the conflicts please? It should be just using what's in develop and adding back the shelves

Thanks, this looks great! Can't wait to test it. One note about the AOV/input links - I was thinking hard about the uses in different DCCs and I think that...

> Could you elaborate? it's actually difficult question. If you publish model and with it workfile, should that published workfile have outgoing link to the model? That's what happened to...

Yes, I think the easiest way would be to drop namespaces on path, treat the root as wildcard (or drop it off completely) and then try to match the path...

There is validator for this but seems that it doesn't work for all cases [validate_look_single_shader.py](https://github.com/pypeclub/OpenPype/blob/develop/openpype/hosts/maya/plugins/publish/validate_look_single_shader.py) We need to test it more

So, could this be tweaked a little bit to provide PySide2 and OTIO for Resolve? Just asking how much is it bound to Fusion logic.

you have there md5 implemented instead of sha256 but I guess that's just placeholder. I was wondering about the metadata that is coming from it. Actually if there is a...

> Would this be a Validator that adds in the extra nodes in *Repair*? Or when would this occur? Yeah, I think *Repair* action si the right place for it....

I agree that we need to specify format, but we'll need to add in the future validators to deal with unsupported features enabled on existing render instance - for example...