1. Messages
  2. OCIO 1.0.10

Re: OCIO 1.0.10

Larry Gritz <l...@...>
 

I'm not really a part of the OCIO dev community, so take my opinion with a grain of salt, but,

I agree that any discussion about design or big issues of implementation really should happen on the archived, fully public mail list. The asynchronous, think and compose before you write, nature of email actually is an important feature.

Slack or other chat seems good for ephemeral, realtime collaboration, "how do I fix this, I need it in an hour", or a quick question/answer that need not be archived. Slack history may be searchable, but it seems to me that it's mainly geared toward conversations that are ok to be missed by people who happen not to be logged in at the time that they happen. It strikes me as the equivalent of an office hallway conversation -- very important to the daily life of a project, but not where any big decisions should be made.



On Apr 28, 2017, at 3:36 AM, DBR - Ben <dbr....@...> wrote:

I would be interested in joining the Slack channel (although I'd rather discussions happened "in the open" - only so discussion/decisions can be easily referenced in future. However as long as people are diligent in transcribing relevant discussions into this mailing list, or ticket comments etc, that would also be perfectly fine)

In terms of bugs I'd like fixed for a future patch version, these are the major problems we've encountered with 1.0.9, or have patched around in our internal builds:

Problems mainly in Nuke:
1. https://github.com/imageworks/OpenColorIO/issues/397 EnvExpand infinite recursion (querying an unset env-var in a OCIO Nuke node "context" value causes Nuke to freeze forever)
2. https://github.com/imageworks/OpenColorIO/issues/383 HDL baking broken when a look is specified
3. https://github.com/imageworks/OpenColorIO/issues/385 OCIODisplay channel selection dropdown order changed in Nuke 9+

Build problems:
(we also apply pull request #321 as it as it not part of any released version, but it is already merged in master)

Additionally, this seems pretty bad, although is not something I have personally encountered (but only because the en_AU locale we use happens to be compatible enough):
5. https://github.com/imageworks/OpenColorIO/issues/297 parsers should explicitly set LOCALE

On 28 April 2017 at 01:56, Michael Root <mi...@...> wrote:

I'd really like to see https://github.com/imageworks/OpenColorIO/pull/381 or some equivalent in the next official release.

I personally don't like closed-door development of open-source projects, and I don't find Slack at all appealing.  That said, I'm not really a major contributor, so whatever helps keep the OCIO project moving is great.

-miker




On 04/26/2017 10:31 AM, Sean Cooper wrote:
Hello all,

With a little bit of movement on the OCIO repo working towards addressing the most egregious image-quality-effecting bugs, we need to look to locking off to a 1.0.10 to help our users, and product partners.

If you haven't been watching, I invite you to take a look at the OCIO repo, and point out other image quality *bugs* that you deem a requirement for the next minor version. Prior to my involvement there have been a number of commits to master since 1.0.9, and I think it's beneficial to put a stake in the ground as a firm mark of rejuvenation. We can proceed from there.

If you haven't joined in the side Slack conversation where more day-to-day conversation has been centered, please reply below or message me personally I am more than happy to invite you. Or if you have a strong opinion against the "closed-door" conversation, I am open ears.

Thoughts, and opinions welcomed, thanks!
Sean
--
You received this message because you are subscribed to the Google Groups "OpenColorIO Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ocio-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups "OpenColorIO Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ocio-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups "OpenColorIO Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ocio-dev+u...@....
For more options, visit https://groups.google.com/d/optout.

--
Larry Gritz
l...@...
Join ocio-dev@lists.aswf.io to automatically receive all group messages.