[oe] [RFC] Removing MAINTAINER field from recipes

[Graeme Gregory]

I shall start by saying that I do not like this proposal.

>  * A lot of the MAINTAINER fields are stale
Not a reason to nuke fields of files where they are not stale.

>  * Not all people listed in the MAINTAINER fields (want to) have commit access
Then there should be a policy of only having a MAINTAINER field with
your email address if you are an oe developer.

>  * People have blindly copied recipes without contacting the respective MAINTAINER
This is due to the above staleness and peoples lack of commit status.

>  * Certain MAINTAINER only care about supporting their $DISTRO
Then they should no claim MAINTAINER of generic packages.

>  * The SCM (monotone) holds all the information about who added the recipes and who edited
> them.
> 
Not normally in a nice easy to read manner.

All the packages that I am listed as maintainer on I actively try and
maintain and improve the quality of. I would like people to feel they
can contact me to moan and complain about their lack of workingness on
their machine or distro of choice. I can then try and work with the
distro maintainers to get a fix into the generic .dev and then pushed
out into the distro that needs it.

I feel rather than nuking the MAINTAINER field which I feel is a useful
peice of information. That it would be more productive to come up with a
set of policies governing peoples MAINTAINERSHIP. I cant see debian for
example dropping all package maintainers overnight.

Maybe for example for people who dont want OE access but want to fix up
software we start some form of sponsorship where an OE dev with an
interest in that package can list as MAINTAINER but pass out bugs etc to
the actual MAINTAINER.

Thanks

Graeme

List of packages as like original proposers.

kismet, links. dillo, mplayer, sulpheed, sylpheed-claws, gqview, fbpanel
tightvnc, epdfview, xmms-tremor, xmms-mad