Improve first contributing experience

[molant]

Setting up the project on a developer machine can take quite some time:

• Fork the project
• Clone it
• yarn
• build

Just the last 2 steps can take a lot of minutes (in my machine yarn is 10 min and build allows me almost to take a nap).

There are a few things we could do to improve this:

• [ ] Docker images
• [ ] From CI upload the dist folders and automatically download them as a git hook (co from master? clone the repo for the first time?)
• [ ] Something else?

In preparation for the Hackathon in October I think we should look into this (and also because it's driving me nuts in my machine).

I'm creating it as an epic because I expect multiple steps for whatever we decide (scripts, update pipelines, etc.)

[molant]

I've done a bit more testing and the numbers on my machine for builds (yarn build) are:

Device	Environment	Build time
Surface Book (i7 16GB 512GB SSD)	WSL2	513s
Surface Book (i7 16GB 512GB SSD)	Windows	982s
MacBook Pro 2016 (i5 8GB 256GB SSD)	macOS Mojave	694s
Surface Book 2 (i7 16GB 512GB SSD)	WSL	925s
Surface Book 2 (i7 16GB 512GB SSD)	Windows	749s
Surface Laptop (i7 16GB 512GB SSD)	Windows	640s

@antross, @sarvaje can you please post your times in your machines? I'll try to get the times for the macBook tomorrow

Nevertheless, we are looking at 10-15 min build time on a machine that's supposed to be pretty decent. If we can decrease the initial build time (or checkout from master) to 1min or less it would be awesome.

Thoughts?

[sarvaje]

Device	Environment	Build time
Surface Book 2 (i7 16GB 512GB SSD)	WSL	925s
Surface Book 2 (i7 16GB 512GB SSD)	Windows	749s

[antross]

Device	Environment	Build time
Surface Laptop (i7 16GB 512GB SSD)	Windows	640s