Approvals for Critical Changes

[Gregory Nutt]

In the past, we talked about not all changes being equal and that 
changes within some directories are more sensitive than changes to 
others.  We discussed the notion of an "owner" of each top level 
directory that needed to approve any changes to those directories.  
Nathan was the primary advocate for the concept.  I think that it is 
time that we re-consider this idea.

Is there any github way to automate this so that the cognizant person's 
approval is required before any change to a directory?  I suspect not 
since that is a pretty specific requirement.

As the number of committers increases, I think there is a real changes 
of ill-informed, ill-conceived, under-reviewed changes to make into 
critical parts of the OS.  How do we protect against that?  We need to 
assure that the proper reviews and approvals are in place for changes to 
those critical parts.

Greg