Mono-repo for Mandel

[chillsauce]

• There is a lot of development activity happening in different GitHub repos within EOS that is not being recognized by those outside of EOS.
• The main EOSIO codebase repo is the common point of reference for the level of development activity happening on EOS, but this does not paint an accurate picture of all the development happening in EOS.
• How might we showcase all the development activity happening in EOS to those outside of EOS?

Possible low-hanging fruit:

• Make the main branch the development branch
• and make a release branch when you do releases
• consider having all blue paper work done in the Mandel repo

Larger effort:

mono-repo:

we can consider merging the following back into the main Mandel repo:

• [submodule "eosio-wasm-spec-tests"]
• [submodule "libraries/abieos"]
• [submodule "libraries/appbase"]
• [submodule "libraries/chainbase"]
• [submodule "libraries/eos-vm"]
• [submodule "libraries/fc"]

We should not merge the following into the main repo:

• softfloat
• yubihsm

Community Proposals Requested

2000 EOS is available to those who submit a proposal that's accepted through the Blue Paper feedback process

[chillsauce]

The current consensus is to merge the following back into the main Mandel repo:

• [submodule "eosio-wasm-spec-tests"]
• [submodule "libraries/abieos"]
• [submodule "libraries/appbase"]
• [submodule "libraries/chainbase"]
• [submodule "libraries/eos-vm"]
• [submodule "libraries/fc"]

We should not merge the following into the main repo:

• softfloat
• yubihsm

We will seek feedback from new ENF engineers when they join.

This should occur before 3.1 is officially cut.