Nobody repealed it. There was no meeting about ending it and no announcement. It was simply true in week two, mostly true in week five, and by week nine the people who were there when it was announced had stopped mentioning it, because mentioning it made them the difficult one. ...
Before you write a core hours policy, do the arithmetic. A team spread across four time zones from Central Europe to the US west coast has, on a standard nine-to-five, no overlap at all — not a narrow window, none — and the policy you are able to write is decided entirely by that number rather than by what you would prefer. Teams skip the arithmetic, announce core hours of 10:00 to 15:00 in a time zone nobody names, and find out in week two that it means 06:00 for one person and 22:00 for another. ...
A meeting policy that is still working in month three has three properties the ones that die do not. It is written down somewhere a new person finds it without asking. It has an exception process that existed before the first exception. And somebody senior has been visibly inconvenienced by it, in public, at least once. ...