kbuild - Linux Kernel Build (Archive)

>What happens now when somebody takes over responsibility for a file
>or subsystem and the MAINTAINERS file doesn't get patched, either because
>that person forgets to send a MAINTAINERS update or Linus doesn't 
>happen to take the MAINTAINERS patch for a while?

>What happens when I look at a file and it's not obvious which
>subsystem it belongs to?  Sure, I can grovel through MAINTAINERS.  But
>how do I know which verbal description matches the function of the
>cryptically-commented or uncommented code I have in front of me?

>Distributed-information problems need distributed-information
>solutions.  Locality is your friend.  This crowd should know that
>if anybody should.

I'll throw this back out again, and if you all are not interested, drop it
if you want.  I am looking for places and points to help out where I see
issues come up several times, and this is one I have seen occasionally. I am
not advocating Eric's proposal for sweeping maintainer's changes, though I
respect Eric, and all the developers work.  How about starting with a simple
MAINTAINERS file maintainer?  Someone to actively follow project developers
and contact info?  Not a small or simple project, I understand, but maybe a
central point to send patches to Linus for the Maintainers file?  Just my
two cents, on a Tuesday  :o)

B.

On Tue, 26 Jun 2001, Holzrichter, Bruce wrote:

> respect Eric, and all the developers work.  How about starting
> with a simple MAINTAINERS file maintainer?  Someone to actively
> follow project developers and contact info?

That's the best idea I've read so far.

Any takers?

regards,

Rik
--
Executive summary of a recent Microsoft press release:
   "we are concerned about the GNU General Public License (GPL)"


		http://www.surriel.com/
http://www.conectiva.com/	http://distro.conectiva.com/

On 26 Jun 2001 16:03:05 -0300, Rik van Riel wrote:
> On Tue, 26 Jun 2001, Holzrichter, Bruce wrote:
> 
> > respect Eric, and all the developers work.  How about starting
> > with a simple MAINTAINERS file maintainer?  Someone to actively
> > follow project developers and contact info?
> 
> That's the best idea I've read so far.
> 
> Any takers?

me.  I took issue with the MAINTAINERS file when Eric brought it up
originally.  However, I don't think drastic measures need to be taken.
I have seen a lot of ideas, including Meta-data in the kernel source.

What I think we need is the simple solution: find a maintainer for the
file, cleanup the current cruft and misinformation, and then actively
work to keep the file current.  I am willing to be this maintainer.

I am not a major "maintainer" in the kernel, but I have and do
contribute.  Thus I think this is a good task for me.  I am willing and
wanting to do this.  Comments?

-- 
Robert M. Love
rml at ufl.edu
rml at tech9.net

>>>>> "Robert" == Robert Love <rml@...> writes:

Robert> me.  I took issue with the MAINTAINERS file when Eric brought
Robert> it up originally.  However, I don't think drastic measures
Robert> need to be taken.  I have seen a lot of ideas, including
Robert> Meta-data in the kernel source.

Robert> What I think we need is the simple solution: find a maintainer
Robert> for the file, cleanup the current cruft and misinformation,
Robert> and then actively work to keep the file current.  I am willing
Robert> to be this maintainer.

A good place to start would be to write a script that checks the email
addresses listed in there for bounces say every 6 months (not too
often or people will get grumphy). Oh and maybe include the data about
the person so he/she can verify it's ok, maybe this way we can get
forget this meta-data sillyness.

Robert> I am not a major "maintainer" in the kernel, but I have and do
Robert> contribute.  Thus I think this is a good task for me.  I am
Robert> willing and wanting to do this.  Comments?

Well, you'd become the maintainer maintainer. Thats worth a slot in
the MAINTAINERS file ;-)

Jes

>On Tue, 26 Jun 2001, Holzrichter, Bruce wrote:

>> respect Eric, and all the developers work.  How about starting
>> with a simple MAINTAINERS file maintainer?  Someone to actively
>> follow project developers and contact info?

>That's the best idea I've read so far.

>Any takers?

Along with some other people that have replied, I would be happy to help out
any way I can.

Bruce H.

I too think I would like to help with this.  I am not a big coder so that
limits my involvement in the kernel, but I think I could help out here.

> Along with some other people that have replied, I would be happy to help out
> any way I can.
>
> Bruce H.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@...
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

Brent Norris

Executive Advisor -- WKU-Linux

W: 270-745-8864
H: 270-563-9226