I don't know the exact content of the proposition, but I thought it was a single package ?  In other words, a hard fork that includes 2 MB and segwit the way it is right now ? 

Am I wrong in thinking that on the software side, that's quite easy to do with core 0.14.1:

1) change the hard limit on the block size (that's just one hard parameter to change)

2) change the activation threshold for segwit from something like 95% to something like 20% to be sure it gets activated automatically if ever this software is run by more than 20% of miners.

3) change the bit on which the checking is tagged in 2)

4) allow to signal the bit in 3) with an option.

5) by hand, from the moment that 80% of the miners signal this bit, produce a first single 2 MB block, which signals the hard fork.  Now, the two chains exist because old core 14.1 will not accept this block and build on its predecessor, and this modified core will accept it (see 1) ) and make its own chain that is not considered valid by the other nodes/miners.

That's about it, or am I missing something ?

Because this code is itself a hard fork, SW becomes automatically a hard fork even though its implementation as a soft fork can remain.

These modifications don't seem like difficult to do in 4 months, right ?