1) a detailed plan, further talk on the details of how to proceed with the agreement reached at the other Roundtable, would be one thing, but i really hope poeple come into that talk with the idea that the pro/cons have been weighted and this IS the way forward, now its more a matter of how Exactly it will be rolled out.
2) incentives, can we somehow increase the incentives to run a full node?
3) Make peace, it's obvious we need a competing impl. , but how do we go about making sure Classic stays relevant? and howdo we get Core and Classic teams not only coexisting but also work together on some things. there will be many BIP most will be MUCH less controversial than BlockSize, these BIP need a lot of man hours put into them, why not have Core work on BIP123 while Classic works on BIP124, when they are done, both teams review each other's work, and at the end of the day BIP123 and BIP124 both get done, and we know they've been peer reviewed and securitized.
the overall goal should be to get everyone on the same page.
bips should not be a core controlled thing.. for instance gavin recently made a bip that ANYONE core/xt/bu/bitcoinj could all implement .. by having individual bips for individual companies will just cause more debates and make bip 100001 something we would see soon..
bips should be something ANYONE can implement and not be branded/copywrited/limited to a company.
bips should be in draftform and tweaked and improved on and then finalised.. rather then making 100000 different bips until one of them sticks
fully agree,
i'm just saying, there's alot of work to be done, split up the work, and review each other's work when done.
maybe the work isn't related to a BIP, say we need to research how effective the gossip network is. one team can be looking at that area running test, coming up with good numbers, while the other team works on somthing else.
both teams would agree to share all data they collect.