I think it is pretty clear:
We call our code repository Bitcoin Classic. It is a one-feature patch to bitcoin-core that increases the blocksize limit to 2 MB. We will have ports for master, 0.11.2, and -86, so that miners and businesses can upgrade to 2 MB blocks from any recent bitcoin software version they run.
In the future we will continue to release updates that are in line with Satoshis whitepaper & vision, and are agreed upon by the community.
The BitPay adaptive blocks are under investigation. If it proves to be best option in future, 2 MB will be replaced with adaptive blocks, otherwise 2-4-8 MB deployed when blocks become almost full. Pretty reasonable, not like the unrealistic Bitcoin Core so called "scalling plan"
Sounds to me like you are suggesting BIP102 hard fork now and than perhaps future hardforks?
As you can see here they appear to be voting democratically on the technical specifications at the moment -
https://bitcoinclassic.consider.it/With this pull request being merged -
https://bitcoinclassic.consider.it/merge-3-v0112-2mb-4mb?results=trueMainnet parameters are:
2 MB cap
... doubling every two years
... for two years
... earliest possible chain fork: 1 Mar 2016
... after miner supermajority (750/1000 blocks)
... and 4 week grace period once supermajority achieved
This appears to contradict your claim, that it is simply BIP 102, and looks more like a 2- 4 plan but realistically an effective 3.5MB - 7MB plan because it looks as if they are going to copy over segwit as well