[OT] Maintainers master list: new idea

[OT] Maintainers master list: new idea

[Marc Brekoo]

Hi there,

Sorry to bother you with this, but I have some new ideas to keep the
MAINTAINERS-file up-to-date. Currently, data in the file aren't up-to-date.
I had the following idea:

What if we create a website, where maintainers can verify and update their
records. Records could also be added, in case a new driver appears, or
removed if the code was obsoleted. The nice thing about this is that we can
send a mail to the maintainer when he hasn't updated his record for say, 6
months (as suggested in previous mails).

This way, patches to the original file could be sent to Linus on a regular
basis. MAINTAINERS would be UP TO DATE!!


Please give me some suggestions, or mail me for more details.

Regards,
Marc Brekoo.

Re: [OT] Maintainers master list: new idea

[Xavier Bestel]

I have another suggestion for the MAINTAINER list:

Put the filenames/directories the maintainer is responsible of, perhaps
in a hierarchical tree (X maintains usb drivers, Y maintains usb
keyboards, Z maintains usb keyboard from such vendor).
This should be coherent and easily parsable.

This way, someone which has to send several patches can make a little
script which finds the correct maintainers to send its stuff to.
I've already been in that situation, currently it's a pain.

Xav

Re: [OT] Maintainers master list: new idea

[Marc Brekoo]

Xavier Bestel said:

> I have another suggestion for the MAINTAINER list:
>
> Put the filenames/directories the maintainer is responsible of, perhaps
> in a hierarchical tree (X maintains usb drivers, Y maintains usb
> keyboards, Z maintains usb keyboard from such vendor).
> This should be coherent and easily parsable.
>
> This way, someone which has to send several patches can make a little
> script which finds the correct maintainers to send its stuff to.
> I've already been in that situation, currently it's a pain.

Wouldn't that be the same as including metadata in the files itself? The
only thing that's different in this approach is that the metadata isn't
included into the code itself, but in a seperate database.

But, maybe this isn't such a bad idea, because it is a _damn_ pain.... :)

I'm currently working on some code to make this website I was talking about,
and I'll include this as soon as it works well enough.

Regards,
Marc Brekoo.