What core is doing isn't a fork. It is backwards compatible.

Someone who runs Core 29 or 29.1 for example has to do 'nothing' and everything is forwards/backwards compatible.

Knots on the other hand by activating an anti-spam hard fork, is changing consensus rules and creating their own fork. That is the point of the write-up and what I was trying to address. Core is not proposing a fork