On 24 Jul 2019, at 15:11, Ted Hardie wrote:
As the RSOC is responsible to the IAB, I would very much like to hear a similar statement from the IAB, the chair or the IAB’s RSOC program lead, regarding what mistakes were made so the community can consider whether the current arrangements require change before moving forward with finding an interim RSE.
The two comments sent by the IAB already express our regret and discuss one aspect of what we think might need to change.
(I’m mindful of conserving my minute at the plenary mic so I’m trying to hash this out here...)
Are you saying the the IAB has not erred in this?
Hi Aaron,
The base error here was not realizing that Heather was still unhappy with issues that occurred significantly before this straw fell on the camel's back. You note that the her view from the RSE cited the rfcplusplus BoF, for example, which the IAB recognized as a mistake and acknowledged as such a year ago:
Speaking personally, I never saw her behavior to IAB members change at all during the period after this point, and I obviously mistook her professionalism on this point as her being satisfied that we were leaving the matter in her hands. Hindsight can be clear on this, but we obviously missed any signs there were that these issues were not resolved.
We're sorry about that, but there's no way to undo that now. The best we can do is work out whether some of the causes are structural (e.g. if you have 3 bosses, will you always get 3 times the employment-related agita?) and try and fix those for the future. That's why our aim in this exercise is to work out how we can changes things so they work better in the future; it's very unlikely that the IAB will be the same the next time a similar issue occurs, and we need more than lore to guide us.
regards,
Ted Hardie
The note you point to below discusses the IAB’s regret (not an apology to the community) nor any admission of error. Is there nothing the IAB should have done differently? It’s a long thread so maybe I missed it. That is different as to whether the RFC6635 should change.
--aaron
