Proposed governance and maintenance policy

Below are the proposed governance and maintenance policy for Chef. :)
It's a bit of a tricky one here - I share @jaymzh concern that a single LT position for core would limit it to somebody able to make it essentially a full time job, but then splitting it up also removes the ability to see the whole of core client.

A middle ground might be potentially having sub-Lts for components, and then either another Lt for client core as a whole who would coordinate roadmaps with the sub-Lts. Or potentially making the roadmap etc a shared responsibility between component Lts.

Either way, it seems like core as a whole is too big for just one Lt.