Resolved (06.__), the ICANN Board acknowledges the fact that the
approving and publishing of minutes of meetings were in arrears and the
Board acknowledges the difficulty that causes members of the community
in keeping up with the Board's activity. Accordingly, the Board notes
that it had directed action and the staff has complied with steps for
ensuring extra resources are being applied to this problem, so the
Board is now confident that minutes will be dealt with, in a timely
fashion. The Board noted the ICANN Staff’s work in bringing the minutes
up-to-date. Lastly, the Board noted that both the Board and the Staff
have indicated strong intentions to maintain a timely reporting of the
Board’s activity.
Too bad it took ICANN less than 48 hours to put the lie to its "strong intention[] to maintain a timely reporting of the Board’s activity," by missing the five business day reporting deadline for the meeting it held on Friday, June 9th.
In other comments below, Veni Markovski spends more of his credibility defending ICANN's late reporting, arguing that posting the report after the end of the fifth business day (a Friday) but before the beginning of the sixth business day (a Monday), constitutes technical compliance with the bylaws. He also suggests that my post characterizing ICANN's late reporting as a bylaws violation is "yellow" journalism.
First the facts and then a comment. Fortunately readers of this weblog and followers of ICANN's activities don't have to take my word, or Veni's, for the proper calculation of time for issuing preliminary reports. The Bylaws are crystal clear: "No later than five (5) business days after each meeting (as calculated by local time at the location of ICANN's principal office), any actions taken by the Board shall be made publicly available in a preliminary report on the Website." It doesn't say "before the beginning of the sixth business day," but "no later than" five business days after each meeting. For the meeting ICANN held on Friday, June 9th, the time clearly passed at the close of business on Friday, June 16th, the fifth full business day after June 9th.
What baffles me is why an ICANN Director would turn his anger on the person reporting the bylaw violation rather than focusing on the person(s) responsible for the late reporting. How much more ridiculous can Staff make the Board look than by flouting one of its resolutions just two days after it was passed? If I were a Board member, I'd direct my substantial concerns at the person(s) responsible, not at the ICANN community member who pointed out the problem.

