[Mesh] hackathon

[deekoo_3291a at deekoo.net]

On Sun, Jun 29, 2014 at 06:28:34PM -0700, Max B wrote:
> documentation to make sure they can get up to speed as quickly as
> possible. I can start brainstorming the key pieces of the mesh info that
> we'd need to get someone onboarded as quickly as possible.

IMO, the most important thing we need is to start a historical archive of
prebuilt binary images so people can just flash a node and dive in.  (And
this will also be useful later on, so we can easily install older versions
when the latest build is broken for whatever reason)

> Also - I can
> think about which of our projects are most urgently in need of work and
> the best ways to make sure people can plug into them. I would LOVE to
> have a docker (/the new hotness in server management) skeleton/framework
> and actually be able to walk someone through setting up their own dev
> mesh in under an hour (I think it's possible...). That way we could
> really let people work on any part of the whole without worrying about
> people stepping on eachother's toes, etc.

Getting private dev meshes set up quickly should be doable (and it's
something I'd like to make a stab at sometime - but I have a strong
suspicion I won't have it ready by the hackathon).

Also, if anyone wants to set up virtualized nodes that people can run on
their laptops/desktops, that might also be useful (especially for people
hacking on the web interface or testing updates to large packages).  I
don't know where to recommend people start on that, though.