Proposed governance and maintenance policy

Below are the proposed governance and maintenance policy for Chef. :)
@ranjib That will basically mean no one except a Chef employee can be an LT for anything other than very small subsystems. That seems sad.

@sersut If the goal is to split up core until it's all bite-size pieces, I think you'll lose having a person who can look at the overall use-case of the client, which brings us back to @juliandunn 's comment on line 69 about having a meta-subsystem for "overall changes", which is actually what I'm interested in, but core was @adamhjk 's suggestion for such a thing. So I think we should *either* make core that *or* make a new meta subsystem for people who are interested in governance of the client as a larger picture.