upvote
I'm not really involved in OpenSSL, aside from a few tiny changes and commenting on a few things that affected GNU coreutils. However, I have seen Bob, whom I assume you are referring to based on the profile picture, participate in many discussions. I wouldn't infer too much from it.
reply
Bob is a member of the Engineering & Standards team at the OpenSSL Corporation.

https://openssl-corporation.org/leadership.html

reply
deleted
reply
Do the projects collaborate closely since the split? My history is admittedly fuzzy.

Sometimes the fix can be worse than the bug. Like patching a hole in the wall.

reply
Yes, they collaborate. BoringSSL and libressl especially, which IIRC share some of the same developers. But OpenSSL has it's own priorities and vision, which sometimes (often?) clashes with the sensibilities of the BoringSSL and libressl developers. Because OpenSSL is still the de facto standard bearer and developer target, it can get frustrating for the libressl and BoringSSL developers, especially when they zig and OpenSSL decides to zag.
reply
I think the second, LibreSSL was forked before OpenSSL v3 and this only impacts OpenSSLv4.
reply
Describing the comments on this PR as "shitting all over the proposed fixes" seems wildly out of proportion? This is direct, productive feedback on a PR that led to a consensus and approval on an appropriate fix in ~a week, we don't need to make the OS process sound worse than it is.
reply
To me it looked like entirely reasonable discussion. Return one value or return an other value. And which one should be chosen based on what is in general expected. And then also consider what parts of code can this sort of change impact.

I really find sad how far we have gone. Purely technical merits of a fix should always be an open conversation.

reply
Nobody is shitting over anything in that PR thread, please stop catastrophizing.
reply
Isnit a cultural, maybe: i found bob to be constructive and to the point.
reply