RE: [ck] Re: Linus 2.6.23-rc1

Did Ingo have the obligation to improve Con's work? Definitely not.
Did Con have a right to get Ingo's improvements or
suggestions? Definitely not.

Yes, and that's where the inequality is.

Unless the maintainer does a really bad job or pisses off Linus,
anyone who wants to merge his code into mainline pretty much
has to get the blessing of the maintainer. On the other hand,
as you just said, the maintainer has no such obligation.

There are no such rights in this open source
development framework (TM).

What Ingo did, I think, was what he wanted and he has the right to do
that.

I think it's the maintainer's privilege, not right.

in the open source world, that which is superior (i.e. code, function,
not person) has the right to exist and the inferior to die away.

I don't think it's the code superiority that decided the fate of the two
schedulers. When CFS came out, the fate of SD was pretty much already
decided. The fact is that Linus trusts Ingo, and as such he wants to merge
Ingo's code. Of course I cannot say it's wrong, and Ingo's earned this
it through years of hard work, but let's not kid ourselves and deny the
obvious fact.

I think Con was simply too frustrated after years of rejection. He could
have been more diplomatic this time round. But no matter how he'd have
done, once Ingo decided to write a new scheduler, the outcome was pretty
much already decided.

SD (and years of Con's work) inspired CFS. This is a fact. No matter how
smart and capable Ingo is, he needs inspiration to keep the good work going.
So I wish Ingo could work more closely with others and let them share a bit
more credit which would just produce even better work.

Hua


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: [ck] Re: Linus 2.6.23-rc1
    ... Compare that to Ingo, who saw that what Con's scheduler did was good, ... Con concentrated on Desktop performance thats right, ... Or the one where the maintainer argues against people who ... If I requested from Ingo to make a scheduler exception that contradicts ...
    (Linux-Kernel)
  • Re: [Announce] [patch] Modular Scheduler Core and Completely Fair Scheduler [CFS]
    ... my perception is that Ingo is simply trying to ... stated that the "problems" are in fact by design and won't be fixed. ... try to improve some areas of the kernel. ... Con worked ...
    (Linux-Kernel)
  • Re: [ck] Re: Linus 2.6.23-rc1
    ... The kernel has become a community project pretty ... I tried speaking to Con and Ingo whether they could settle their issue ... and brought in good scheduler concepts and ideas to the Linux world. ...
    (Linux-Kernel)
  • Re: [ck] Re: Linus 2.6.23-rc1
    ... I have no doubt that Ingo can quickly transform an idea into working code and I would've been very surprised if he wouldn't be able to turn it into something technically superior. ... He decided instead to work against Con and started his own rewrite, this is of course his right to do, but then he should also accept the responsibility that Con felt his years of work ripped apart and in vain and we have now lost a developer who tried to address things from a different perspective. ... 1101 Quezon City, Philippines ...
    (Linux-Kernel)
  • Re: [patch] CFS scheduler, -v9
    ... Are you worried that Con ... after the scheduler sat and rotted for several years. ... Maybe I'm naive and/or missing something but Ingo doesn't seem to be ... Linux and brings his unique abilities to bear on very complex Linux ...
    (Linux-Kernel)