On my own account as I don't have the Dogecoin password on me - it's a way of allowing users to create their own hard forks, and as with any hard fork whether it's adopted or not depends on consensus. Essentially a lot of proposed changes we don't try, because we're fairly certain that we can't get consensus on them (and/or they're just a bad idea), but we shouldn't be the gatekeepers for changes, the community should. So if someone can get consensus on a new hard fork, and get enough people to adopt their suggested configuration, it should become the new main fork.
It does! Leave it to the DOGE to extend the boundaries of decentralization...
Specifically, what I mean is it shouldn't require coding and compiling your own client to do this. We actually have the arbitrary hard-fork code in 1.10 already, in an attempt to mitigate the nest of if-else conditions from the hard forks to date, so mostly this involves deciding a configuration format (likely JSON), safety measures (i.e. make it clear to the user if they're running a non-standard fork, and which fork they're running), and code it all up.