Is there any agreement on how such a PoW change would be implemented and what code of conduct would be followed? For example how a new PoW scheme would be selected. I presume some thoughts has already been put into it, beyond merely considering the option.
How about start by prepare guide/reference client in-case hard-fork is needed? Reflecting from Bitcoin-Qt 0.8.0 accident (which is accidental hard-fork due to different DB version), that would help community/developer where to start solve the problem.
It's not good to have an exact algorithm planned out, since then someone could make an ASIC for it in advance.
Smart move, though I don't believe in hypes regarding magical power of ASIC designers to crack every algorithm. A well designed memory hard algo won't be an easy piece of cake to bite, imo.
It'd be nice if there was a defined procedure for selecting one quickly. The exact algorithm isn't that important as long as nobody knows it in advance and it keeps the necessary properties for a PoW, but you don't want to waste time arguing about it. ..
Preparedness could be a lot better. I especially advocate for the creation of a clear set of criteria which indicate miner abuse so that they don't get away with something very incremental like freezing "obviously stolen" coins.
Well said.