[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <200707261222.50487.bzolnier@gmail.com>
Date: Thu, 26 Jul 2007 12:22:50 +0200
From: Bartlomiej Zolnierkiewicz <bzolnier@...il.com>
To: Jeff Garzik <jeff@...zik.org>
Cc: Ingo Molnar <mingo@...e.hu>,
Satyam Sharma <satyam.sharma@...il.com>,
Rene Herman <rene.herman@...il.com>,
Jos Poortvliet <jos@...nkamer.nl>, david@...g.hm,
Nick Piggin <nickpiggin@...oo.com.au>, Valdis.Kletnieks@...edu,
Ray Lee <ray-lk@...rabbit.org>,
Jesper Juhl <jesper.juhl@...il.com>,
linux-kernel@...r.kernel.org, ck list <ck@....kolivas.org>,
linux-mm@...ck.org, Paul Jackson <pj@....com>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [ck] Re: -mm merge plans for 2.6.23
On Thursday 26 July 2007, Jeff Garzik wrote:
> Bartlomiej Zolnierkiewicz wrote:
> > On Wednesday 25 July 2007, Ingo Molnar wrote:
> >> you dont _have to_ cooperative with the maintainer, but it's certainly
> >> useful to work with good maintainers, if your goal is to improve Linux.
> >> Or if for some reason communication is not working out fine then grow
> >> into the job and replace the maintainer by doing a better job.
> >
> > The idea of growing into the job and replacing the maintainer by proving
> > the you are doing better job was viable few years ago but may not be
> > feasible today.
>
> IMO... Tejun is an excellent counter-example. He showed up as an
IMO this doesn't qualify as a counter-example here et all unless
you are trying to say that Tejun does your job much better and that
we should just replace you. ;)
> independent developer, put a bunch of his own spare time and energy into
> the codebase, and is probably libata's main engineer (in terms of code
> output) today. If I get hit by a bus tomorrow, I think the Linux
> community would be quite happy with him as the libata maintainer.
Fully agreed on this part.
> > The another problem is that sometimes it seems that independent developers
> > has to go through more hops than entreprise ones and it is really frustrating
> > experience for them. There is no conspiracy here - it is only the natural
> > mechanism of trusting more in the code of people who you are working with more.
>
> I think Tejun is a counter-example here too :) Everyone's experience is
> different, but from my perspective, Tejun "appeared out of nowhere"
> producing good code, and so, it got merged rapidly.
Tejun (like any of other developers) spent some time in-the-making
and this time was in large part spent in the IDE-land, and yes I'm also
very glad of the effects. :)
Thanks,
Bart
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists