Improve project organization

Proposed improvements to project organization.

This organization change has 3 goals:

1) Make the project more open and accessible
2) Make the project more scalable
3) Do this in an incremental way, without unnecessary refactoring

The actual organization change is covered in 6a99b8dea935be9228a47c84bcbfb7491e6e5584. Cosmetic changes are discussed in #9177 and #9178 
+1. I didn’t realize this was a format (new to toml) but I’m glad we’re not building a parser for this.

> On Nov 14, 2014, at 3:31 PM, Solomon Hykes <notifications@github.com> wrote:
> 
> In MAINTAINERS:
> 
> > +			"docker/project/make"
> > +		]
> > +
> > +	[Subsystem.remote api]
> > +
> > +		people = [
> > +			"vieux"
> > +		]
> > +
> > +[people]
> > +
> > +	[people.shykes]
> > +
> > +	Name = "Solomon Hykes"
> > +	Email = "solomon@docker.com"
> > +	Github = "shykes"
> Also note that with a unique top-level file, readable by an out-of-the-box parser (here toml), complexy is vastly reduced compared to our current cascading system. The parser/scanner we have in gordon is pretty hairy and from personal experience, modifying it is non-trivial.
> 
> —
> Reply to this email directly or view it on GitHub <https://github.com/docker/docker/pull/9137/files#r20394374>.
>