Clarifications...

1) Bitcoin classic is not simply changing maxBlockSize, doing so , even to 2MB would introduce dangerous attack vectors -CVE-2013-2292  The Classic devs are aware of this and thankfully making many more changes for sigop protections.

2) Development has already been decentralized with multiple implementations. We do need to support other implemenentations like libbitcoin and bitcore. There is a distinction to be made between having multiple implemenatations that break consensus rules and ones that do not . There can be multiple implementations that have different developers, written in different code/languages, and with different unique features all working cooperatively (This is recommended), but some would argue that always having implementations that are attempting to usurp consensus rules decreases user and investor confidence as ultimately there can only be one set of consensus rules that is considered bitcoin.

3) Segwit provides an effective 2MB increase in capacity , is already in testnet, has wide support - https://bitcoincore.org/en/segwit_adoption/ and will go live in april, IMHO before Classic can get deployed

4) In other news a planned hard fork increasing to an effective 4MB capacity is already being organized-

https://botbot.me/freenode/bitcoin-core-dev/

wangchun from F2Pool is planning with some core devs yesterday for a planned 2MB hard fork and adding extra nonce space in feb/march 2017 to increase effective capacity up to ~4MB.