Earlier quoted context omitted.
Were the deadlines, feature freezes, and project reshuffling imposed on you from above, or were they your decisions? In a blog post two months ago you said, "I've taken the decision..." https://web.dev/blog/webdev-migration There was clearly someone in Google management who decided that RSS could be broken. Why is this important? Well, for example, it seems that the RSS feed was already broken when this important ann…
Not the GP but I think that blog post https://web.dev/blog/webdev-migration you linked explains it pretty clearly? • The people working on web.dev decided to migrate to a common Google site platform, so that they could focus on content rather than maintaining an ad-hoc infrastructure, • That platform happens not to support RSS (yet), so they've done the best they can in the meantime, filing a bug with the platform, c…
This is a false dichotomy. I wasn't questioning the decision to migrate platforms, I was questioning "the deadlines, feature freezes, and project reshuffling".
> there are always ongoing migrations between "the old system that is deprecated and the new system that is not ready yet" — but that is "just" a cultural problem rather than anyone consciously deciding that RSS could be broken.
I disagree, because whenever you migrate, some features are considered essential and others inessential. Someone consciously decided that RSS was among the inessential features in this specific case. The "culture" did not make that specific decision.
This is the developer relations team. How can you have relations with developers when they don't even see your announcements? The essential part is the communication with outside developers, not the internal CMS.
> they've done the best they can in the meantime, filing a bug with the platform, creating the https://developer.chrome.com/feeds info page acknowledging the issue, and even creating unofficial feeds.
How were developers supposed to know any of this? I had no idea until now.