[oe] Package Maintenance

[Holger Schurig]

> * Who maintains file X (be it a class/recipe/conf/sitefile
> etc)? * Who last changed file X?
> * Who are the contributors to file X?
> * Can we easily create a subset of the metadata which is
> "maintained"?

I don't really think that -- in the general case -- maintaining 
maintainers on a per-file or per-recipe basis works for the 
recipes. There are just too many.

But maybe maintainership based on categories make sense.

* all cross-compilation and build tools
* all Java stuff
* all Python stuff
* all matchbox stuff
* all KDE stuff
* all OPIE stuff
* (more categories that are easily identifiable and make sense)
* the "pool" :-)

The point is: a package that is in the python category could 
easily be in Mickey scope of interest anyway. Similar for other 
categories. There's no exact match, but still a high degree of 
correlation.

Now it's easy to say "John Doe is our Java guy". And John could 
of course have sub-maintainers.