What to do with this code base?

[TimDaub]

Considering that we have now two separate code bases: What to do?

Options that I was able to recognize:

• leave them separated and continue develop one of them further
• merge ethberlin into artonomous-mvp (and vice versa even though that wouldn't make much sense)
• (more?)

I'm eager to develop this project to main net :)

[iainnash]

I'd wonder if it'd be worth it to publish a separate repository for smart contracts, another for the subgraph stuff and then one for the frontend. One issue with this is then things can become quickly out of sync as opposed to a more monorepo approach and it makes tracking issues and syncing concerns harder.

Would it be best to rename the hackathon repository to be the main repository and clean up and merge in code from the other repository as a starting point?

[tarrencev]

I think splitting the codebase up makes sense, perhaps as a monorepo. I think it would also be good create small PR's as we move code over to another repo, so it can be properly code reviewed. I think there is quite a bit of tech debt + security considerations that we overlooked during the hackathon :)