User: Password:
Subscribe / Log in / New account

News from the staging tree

News from the staging tree

Posted Sep 11, 2009 14:21 UTC (Fri) by zander76 (guest, #6889)
Parent article: News from the staging tree

A wonderful example of a company throwing code over the wall, watching it get rejected, and then running away as fast as possible, all the while yelling over their shoulder, "it's required on all new systems, you will love it!" We don't, it sucks, either fix it up, or I am removing it.

This is one example of linux kernel development being full of themselves. Yeah, sure thats one way to look at it. Another way would be "throw code over wall after spending time getting your boss to let you release the code and move on to what you are suppost to be working on before you get fired!!"

It take a lot of time and effort to convince your boss that releasing code to the linux community is a good thing but they don't want to pay you to work on a linux project when you have other stuff to do. If people like it or can use any of it then great if not ohh well.

To put it briefly, some of us don't work in the open source community or even use open source software at work so there is absolutely NO incentive for our boss to allow us to release anything let alone do continual work on it. Would be nicer if people would accept what it is and that is "hey, thanks for the example code, if someone is interested in working on that they can have a look at what you released"

(Log in to post comments)

News from the staging tree

Posted Sep 11, 2009 17:21 UTC (Fri) by martinfick (subscriber, #4455) [Link]

While your perspective is a good one, it does not really apply to the quote above. Sure, it is a great thing when a company releases source code, no matter what!

But if you pay attention to the 2nd half of the quote, it implies an expectation on the part of the releaser, that's the complaint. In other words, no one is complaining that a company released code, they are complaining that certain companies release code and expect it to make it into mainline so that this same company can later benefit from this code being in mainline for future projects (note the: "it's required on all new systems").

This requires a two way interactive model; as others have pointed out, that seems to be the point of the staging tree. The kernel devs do NOT expect the companies to do all the work on their own (that's why it goes in the staging tree, to get kernel devs involved). But this also means that the kernel devs have not yet taken up maintainership of the code since it is not yet in mainline. They expect the company to be involved working with the devs to bring it up to par. Once it is up to par, I suspect that it is more acceptable to rely on the kernel devs to keep it up to date with the changing mainline kernel, but not before.

News from the staging tree

Posted Sep 12, 2009 4:03 UTC (Sat) by zander76 (guest, #6889) [Link]

After reading the quote a few times I see your point. I guess it depended on how you read "Its required on all new systems". I read it more alone the lines of the hardware has changed so if you want to support the new hardware you can make it work. After re-reading it I can see that it can be taken as "We need it on all our new systems so merge this".

News from the staging tree

Posted Sep 13, 2009 2:53 UTC (Sun) by gregkh (subscriber, #8) [Link]

My word, I feel like this is 8th grade poetry class, where everyone
is trying to interpret the phrase and meaning of every single line.

That was a summary of over 40 drivers, and was a very long message. If anyone wants any specific clarification, did anyone think to actually
ask me?

Oh, and as for this driver, Intel told me to drop it, they don't want
it in the kernel anymore as the team has been disbanded, and they no longer
care about the code.

News from the staging tree

Posted Sep 13, 2009 13:25 UTC (Sun) by nix (subscriber, #2304) [Link]

Would the code have done anything useful were it fixed up, I wonder?

News from the staging tree

Posted Sep 13, 2009 15:48 UTC (Sun) by gregkh (subscriber, #8) [Link]

Perhaps, try it out, it's not like it is hidden anywhere...

Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds