Crossing namespaces

[Daniel van Vugt]

Looking through our class hierarchies, particularly in the server, it 
occurs to me that we cross namespaces a few times. This is particularly 
apparent trying to trace server logic through multiple subdirectories, 
which it crosses a lot. I'm referring mainly to:
mir::graphics::
mir::compositor::
mir::surfaces::
mir::frontend::

These namespaces are often so related and interdependent that I can't 
see the justification in them being separate. It just makes things more 
complicated. And if they should be separate then they're not quite 
separated in an optimal way yet.

Does anyone have a good reason why server classes shouldn't live under 
mir::server:: ? I don't imagine many of the sub-namespaces are really 
required or even logical any deeper than that.