From: Rene Herman <rene.herman@gmail.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, Adrian Bunk <bunk@stusta.de>,
Marcel Holtmann <marcel@holtmann.org>,
Christoph Hellwig <hch@infradead.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: MODULE_MAINTAINER
Date: Mon, 23 Apr 2007 11:33:40 +0200 [thread overview]
Message-ID: <462C7D74.60003@gmail.com> (raw)
In-Reply-To: <4613D492.2070404@gmail.com>
On 04/04/2007 06:38 PM, Rene Herman wrote:
Rusty?
> On 04/04/2007 06:00 PM, Alan Cox wrote:
>
>>> Given that people seem to agree that authorship information has no
>>> place in the binary, that might actually be best.
>>
>> Authorship information is very useful in the binary, especially when you
>> have to get lawyers involved in explaining things to people.
>
> Okay.
>
>>> So, MODULE_AUTHOR be gone?
>>
>> Not if I have anything to do with it. Putting maintainer in is not a
>> bad idea but that assumes it gets maintained, the beauty of _AUTHOR
>> is that it's generally right and stays that way or approximately so.
>
> Case in point; someone is working with me in private on a new "mitsumi"
> legacy CD-ROM driver. He's authoring the actual driver and upto now I've
> just been doing some peripheral module infrastructure work. Given that I
> have the hardware to test the thing, I'll be the maintainer though.
>
> Adding myself as a MODULE_AUTHOR would be largely incorrect and adding
> myself as the _only_ MODULE_AUTHOR would be so factually incorrect I
> wouldn't, even if only from a credits point of view. Yet I do want to
> make sure people contact me, and not the MODULE_AUTHOR (which will
> happen no matter the MAINTAINERS file).
>
> Other cases-in-point; I've lately been rummaging through sound/isa a
> bit. Nothing much copyrightable again but especially in those situations
> where (some of the) original authors are no longer active, I do again
> want people to contact me about them if needed. And all the "which one
> of the three people listed here is maintaining this" is yet another.
>
> MODULE_AUTHOR may be approximately right but especially with old drivers
> it also has little relation with who's maintaining the thing.
>
> If MODULE_AUTHOR stays, can I just have MODULE_MAINTAINER please? It
> doesn't need to be added to drivers directly, it can just grow (and
> being inside the code, I suppose it'll likely stay up to date better
> than the MAINTAINERS file).
Rene.
next prev parent reply other threads:[~2007-04-23 9:35 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-04 11:26 MODULE_MAINTAINER Rene Herman
2007-04-04 11:29 ` MODULE_MAINTAINER Rene Herman
2007-04-04 12:33 ` MODULE_MAINTAINER Christoph Hellwig
2007-04-04 13:02 ` MODULE_MAINTAINER Rene Herman
2007-04-04 14:57 ` MODULE_MAINTAINER Adrian Bunk
2007-04-04 16:33 ` MODULE_MAINTAINER Stefan Richter
2007-04-04 16:38 ` MODULE_MAINTAINER Adrian Bunk
2007-04-04 16:45 ` MODULE_MAINTAINER Stefan Richter
2007-04-04 14:48 ` MODULE_MAINTAINER Marcel Holtmann
2007-04-04 15:02 ` MODULE_MAINTAINER Adrian Bunk
2007-04-04 15:50 ` MODULE_MAINTAINER Rene Herman
2007-04-04 16:00 ` MODULE_MAINTAINER Alan Cox
2007-04-04 16:06 ` MODULE_MAINTAINER Marcel Holtmann
2007-04-04 16:38 ` MODULE_MAINTAINER Rene Herman
2007-04-04 17:00 ` MODULE_MAINTAINER Takashi Iwai
2007-04-04 17:48 ` MODULE_MAINTAINER Adrian Bunk
2007-04-04 18:01 ` MODULE_MAINTAINER Rene Herman
2007-04-04 19:12 ` MODULE_MAINTAINER Adrian Bunk
2007-04-05 0:08 ` MODULE_MAINTAINER Stefan Richter
2007-04-23 9:33 ` Rene Herman [this message]
2007-04-23 11:24 ` MODULE_MAINTAINER Rusty Russell
2007-04-23 11:52 ` MODULE_MAINTAINER Robert P. J. Day
2007-04-23 12:00 ` MODULE_MAINTAINER Robert P. J. Day
2007-04-23 12:32 ` MODULE_MAINTAINER Rene Herman
2007-04-26 1:18 ` MODULE_MAINTAINER Andrew Morton
2007-04-26 10:03 ` MODULE_MAINTAINER Rusty Russell
2007-04-26 10:41 ` MODULE_MAINTAINER Rene Herman
2007-04-26 13:54 ` MODULE_MAINTAINER Adrian Bunk
2007-04-26 14:55 ` MODULE_MAINTAINER Rene Herman
2007-04-26 16:00 ` MODULE_MAINTAINER Alan Cox
2007-04-26 16:45 ` MODULE_MAINTAINER Rene Herman
2007-04-26 15:41 ` MODULE_MAINTAINER Randy Dunlap
2007-04-26 15:52 ` MODULE_MAINTAINER Adrian Bunk
2007-04-26 16:44 ` MODULE_MAINTAINER Randy Dunlap
2007-04-26 17:12 ` MODULE_MAINTAINER Adrian Bunk
2007-04-26 19:37 ` MODULE_MAINTAINER Krzysztof Halasa
2007-04-26 19:43 ` MODULE_MAINTAINER Adrian Bunk
2007-04-26 20:02 ` MODULE_MAINTAINER Krzysztof Halasa
2007-04-26 20:24 ` MODULE_MAINTAINER Adrian Bunk
2007-04-26 21:51 ` MODULE_MAINTAINER Krzysztof Halasa
2007-04-26 22:01 ` MODULE_MAINTAINER Adrian Bunk
2007-04-26 22:07 ` MODULE_MAINTAINER Krzysztof Halasa
2007-04-26 22:28 ` MODULE_MAINTAINER Rene Herman
2007-04-26 20:11 ` MODULE_MAINTAINER Rene Herman
2007-04-26 22:24 ` MODULE_MAINTAINER Gene Heskett
2007-04-27 9:06 ` MODULE_MAINTAINER Stefan Richter
2007-04-26 22:03 ` MODULE_MAINTAINER Rene Herman
2007-04-27 21:06 ` MODULE_MAINTAINER Rene Herman
2007-04-28 21:03 ` MODULE_MAINTAINER Krzysztof Halasa
2007-04-23 23:46 ` MODULE_MAINTAINER Rusty Russell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=462C7D74.60003@gmail.com \
--to=rene.herman@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bunk@stusta.de \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=rusty@rustcorp.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox