The Myth of the Isolated Kernel Hacker 282
Ant writes "The Linux Foundation's report (PDF) on who writes Linux — "... Linux isn't written by lonely nerds hiding out in their parents' basements. It's written by people working for major companies — many of them businesses that you probably don't associate with Linux.
To be exact, while 18.2% of Linux is written by people who aren't working for a company, and 7.6% is created by programmers who don't give a company affiliation, everything else is written by someone who's getting paid to create Linux. From top to bottom, of the companies that have contributed more than 1% of the current Linux kernel, the list looks like this: ..."
The Myth of the Isolated Colenel Hacker (Score:5, Funny)
Re: (Score:2)
Go to Chinatown, find Murtz, and .. you know.
Re: (Score:2)
Is that you Marty? Did you just come forward in time using Doc Brown's latest time machine?
What's the weather like back in 1998?
shocking (Score:5, Funny)
and i thought IBM and Red Hat just took the code and didn't give their changes back to everyone else
Re: (Score:3, Interesting)
No, that was Canonical. Greg K-H publicly and controversially called them out about it at a kernel developer conference a while back, but I can't find a link right now.
Re:shocking (Score:5, Interesting)
Re:shocking (Score:5, Insightful)
Re: (Score:2)
Re: (Score:2)
maybe because they only dabble in userland sruff, and let the Debian devs do all the kernel work?
Re:shocking (Score:5, Informative)
They do, see below--just not as much as some others.
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
$ cd linux-2.6
$ git shortlog --author="@canonical.com" --author="@ubuntu.com" --since="6 months ago"
Andy Whitcroft (12):
checkpatch: make in_atomic ok in the core
checkpatch: do not warn about -p0 patches when checking files
checkpatch: correctly handle type spacing in the face of modifiers
checkpatch: pointer type star may have modifiers following
checkpatch: a modifier is not an identifier at the end of a type
checkpatch: extend attribute testing to all modifiers
checkpatch: add __ref as a sparse modifier
checkpatch: version 0.28
Input: synaptics - ensure we reset the device on resume
suspend: switch the Asus Pundit P1-AH2 to old ACPI sleep ordering
mmc: add MODALIAS linkage for MMC/SD devices
acer-wmi: Cleanup the failure cleanup handling
Colin Watson (1):
parisc: expose 32/64-bit capabilities in cpuinfo
Leann Ogasawara (1):
x86: add Dell XPS710 reboot quirk
Luke Yelavich (1):
ALSA: hda - add another MacBook Pro 3,1 SSID
Scott James Remnant (13):
[SCSI] ch: Add scsi type modalias
sbus: Auto-load openprom module when device opened.
netfilter: auto-load ip6_queue module when socket opened
netfilter: auto-load ip_queue module when socket opened
[MTD] Auto-load mtdchar module when device opened.
[MTD] Auto-load nftl module when device opened.
V4L/DVB (10947): Auto-load videodev module when device opened.
floppy: provide a PNP device table in the module.
applicom: Auto-load applicom module when device opened.
cyclades: Auto-load cyclades module when device opened.
specialix: Auto-load specialix module when device opened.
usb: Auto-load cdc_acm module when device opened.
riscom8: Auto-load riscom8 module when device opened.
Re: (Score:3, Informative)
$ git shortlog -s --since="6 months ago" --author="@debian.org"
2 Andres Salomon
2 Bastian Blank
65 Moritz Muehlenhoff
1 Ron Lee
1 dann frazier
(And googling around suggests Mortiz Muehlenoff probably isn't a canonical employee.) Sure, people could also be using personal addresses, etc., though note the addresses come from git metadata,
Re: (Score:2)
The real news here is that, since isolated kernel hackers are apparently a myth, for safety reasons they should all be grounded*. That certainly explains why they spend all their time in their parents' basements.
* We wouldn't want them shocking anyone.
Re: (Score:2)
No, you're thinking of BSD (ducks)
Myth definitely false! (Score:5, Funny)
Linux isn't written by lonely nerds hiding out in their parents' basements
Of course! There's the lonely nerds hiding out in their parents' attics as well. More light, less ground water.
You know what company is shamefully absent? (Score:2, Interesting)
Re:You know what company is shamefully absent? (Score:5, Insightful)
They seem to concentrate on the userland experience..
Not a bad idea.
Comment removed (Score:4, Insightful)
Re: (Score:2)
There are a variety of kernel issues (think wireless drivers and other hardware support) that have a major impact on the userland experience.
And there's plenty drivers living in userland missing. For example anything connected by USB, the kernel can do raw read/write to all USB devices but without a driver to know where and what to write that won't do any good. A linux issue yes, but not a kernel issue.
Re: (Score:2)
While your premise is true, the implication that Canonical should contribute in a greater way towards
Re: (Score:2)
There's more to the success of an operating system than the kernel.
Re:You know what company is shamefully absent? (Score:4, Insightful)
Re: (Score:2)
given that the kernel is one of the largest parts, with probably the most dramatic changes going on, you'd think that it would be wise for anyone so dependent on it to contribute directly.
Canonical is not only not caring, they are also passing on a strategical opportunity to help out where it matters a lot.
Re: (Score:2, Insightful)
On the other hand, what Canonical are focussing on, and what makes Ubuntu popular, is the user experience. They are doing all the tidying up of the installer and package handling so that the non-techie user doesn't get baffling (to them) messages about mismatched packages etc. In some ways, you should see them more as a packager than a developer. In which case it is hardly surprising that they contribute little to kernel development. The kernel, by and large, is the bit that you don't package.
Re:You know what company is shamefully absent? (Score:4, Insightful)
Re: (Score:2, Insightful)
Re: (Score:2)
I have no idea whether this is true or not, but it might well be that Canonical is a lot more involved with the integration of desktop environments and application packages, documentation, support, and so on, and not doing much at all with the kernel. Linux kernel development is one thing, Linux distro development is another.
Re: (Score:3, Insightful)
Google.
Re: (Score:3, Interesting)
I can't answer that question, but you know what other big linux using corporation is conspiciously absent from that list?
Google.
Serious question (I must not be awake enough yet to form a proper Google query)
How much HAS Google actually contributed back to Linux?
I mean I realize they USE Linux and all, but I haven't heard of any kernel updates/patches from them.
Have they really contributed much back to the kernel? the distros? All that they make popular and well known are their apps, which is great and all, but an app is not a kernel.
And even their apps seem to usually get late ports to Linux, just after the already late port to Mac
Re: (Score:2, Insightful)
Google contributes in two ways. Directly, they provided a port to one of the Qualcomm MSM chips as part of the Android project. That's a pretty substantial chunk of code related to a pretty sophisticated microcontroller. Smallish compared to the total amount of kernel code, however, as are all platform/machine/architecture ports.
Indirectly, Google funds the the Summer of Code, which has resulted in kernel code submissions--- but all under the original author's identity and not Google's.
Overall, I don't k
Re: (Score:2)
Is it a requirement to CHANGE anything in the kernel? If they're just using stock builds, what is there to give back?
Re: (Score:2)
Is it a requirement to CHANGE anything in the kernel? If they're just using stock builds, what is there to give back?
Well, I would say to "contribute back to the Linux kernel", that yes, changing the kernel is a requirement ;}
Thus my question. Parent said Google DID contribute back to the kernel. I, like you, assumed they used a stock build.
But admittedly I did not know either way what the case was.
Re: (Score:2, Informative)
FUD much? .8%.
Since you're currently at +5 Insightful, I have to point out that they're actually on the list, the poster above cut it off at 1%, they're
Also from TFA, there's another list of companies that do sign-off patches. Google is at 10.5% on that list, behind only Red Hat, above Novell, Intel, and IBM.
To put it in perspective, the list doesn't include Linus on the list of contributors (he doesn't make the cut), but it does list him on the sign-off patches list.
Just FYI,
-t.
Re: (Score:2)
Re:You know what company is shamefully absent? (Score:5, Informative)
They're a little bit further down.
The next two rows on the list in TFA are as follows:
17: Freescale 1,375 0.9%
18: Google 1,261 0.9%
I'm not sure why the parent decided to stop where they did.
These rankings are based on number of kernel changes submitted broken down by employer.
However it seems that Google employees are making a significant contribution to Linux project management and quality processes though: Red Hat employees sign off on over 36.4% of changes, which is the highest proportion of sign-offs in the hands of a single company, but Google has second place in that table with 10.5% of all sign-offs. It looks like several Google employees are filling the roles of subsystem maintainers - they may not write as much code as some other companies but they are still contributing some senior people.
Interesting stuff!
Re:You know what company is shamefully absent? (Score:5, Interesting)
It's not really "some senior people". Google's 0.9% of code contributed and 10.5% of patches signed off on exactly match the efforts of one employee, Andrew Morton. Aside from Andrew, they have a couple of other minor contributors but he is by far the most significant.
Re: (Score:2)
That's essentially just Andrew Morton [wikipedia.org]. According to this June 8th 2008 Google tech talk [youtube.com] he was responsible for signing off on more stuff than Linus
You don't get it (Score:3, Insightful)
Free software is about freedom, not about community busybodies telling companies how they should give back. If you're a company who can take free software, respect the licenses, and make a bajillion dollars off of it, then great! That's part of what freedom is about.
Re:You know what company is shamefully absent? (Score:5, Interesting)
Seems a lot of people don't know squat about Canonical. Some rich guy invested a good bit of his fortune into making Linux widely known and acceptable on the laptop. So far, he's done a pretty good job. If he contributes nothing else back into the upstream system, he attracts some pretty bright people to the Linux community - SOME of whom go on to contribute something. Reality check: Ubuntu does contribute, whether they actually work on the kernel or not.
Mod parent up! (Score:2)
His comment is right on target.
Re: (Score:2)
Considering the mess that is userland and the desktop, you should be thankful they even exist. I mean, shaving off .0000002 ms off kernel loading time is great too, but perhaps someone should be focused on the desktop experience and maintaining a good distro without too much worrying about the kernel.
Re: (Score:2)
In that case, where are GNU and Debian?
I'd imagine that they make up a considerable portion of the 18% of contributions made by individual developers. Given that Ubuntu is a variant of Debian with a radically overhauled user interface, one would imagine that any Ubuntu kernel hackers would be encouraged to contribute upstream to Debian, rather than to Ubuntu itself.
Not quite a myth. (Score:4, Insightful)
At 18.2%, individuals are still the largest single group contributing to Linux. The next is RedHat at 12.3%.
Re: (Score:2)
Re:Not quite a myth. (Score:5, Insightful)
At 18.2%, individuals are still the largest single group contributing to Linux. The next is RedHat at 12.3%.
By your analysis, the largest single group contributing to Linux is actually the "people working for a company" group, with 81.8%.
Re: (Score:2)
No, the largest single group would be the "Linux Kernel hackers" group at 99.98% of all source contributed.
Re:Not quite a myth. (Score:4, Funny)
Something's wrong with the intartubes. Can someone switch the Dichotomy Filter back on please?
Re:Not quite a myth. (Score:4, Funny)
Re: (Score:2, Interesting)
Except if you group them as,
People who do it for a company
People who don't do it for a company
Then your 18.2% are in the minority, which I think is the point here. The company folk might represent different companies, but they're still companies.
GPL good for business (Score:4, Insightful)
I hope this finally kills off the "GPL is bad for business" myth. Every one of those companies is paying for work on the kernel because it is good for their business. Red Hat, IBM, Novell, etc. aren't charities - they sponsor Linux development because it expands their markets and brings in profits.
Re:GPL good for business (Score:5, Insightful)
Yes, once Linux was established as a viable OS, companies jumped on the bandwagon.
The real business issue about GPL'd code isn't whether established companies will support it once it is successful, but whether you can start your own for-profit software business if you license your software under the GPL.
Re:GPL good for business (Score:5, Informative)
whether you can start your own for-profit software business if you license your software under the GPL.
Depends on what the alternatives are and what your business model is. Assuming we narrow down the choices to the two best known open source licences (others are broadly similar to one of the other) and proprietary licensing:
Obviously this does not cover anything like all the possibilities, but I just want to make the point that there are business reasons for every choice.
Re: (Score:2)
If a GPL'd operating system, like Linux, came to dominate the business and consumer OS market, would that be FINANCIALLY better or worse for software developers?
If so, how? If not, why no significant action in that direction?
Re: (Score:2)
Which developers? Those who use, rather than produce OSes will probably be better off - and there are far more of them
Microsoft shareholders would take most of the loss.
OS developers would have a wider choice of employers, which might strengthen their bargaining position, but the business itself will be less profitable so there will be less money to go around. I would bet on a reduction in the number of jobs (with a lot of people moving to other types of software) rather than a huge reduction in salaries.
Th
This Linux Kernel was brought to you by... (Score:2)
Reminds me of PBS...
This Linux Kernel was brought to you by the continued support of USERS LIKE YOU.*
* And support from Red Hat, IBM, and Novell.
Where is the missing 24.1%? (Score:5, Interesting)
If you sum up the figures given in the article, it only accounts for 75.9% of the contributions. I am going to speculate that this missing quarter is contributed by many who contribute infrequently. IE, IT staff in companies that use Linux and find the occasional bug and submit a patch to correct it. If this speculation is correct, the largest group that contributes is 'Everyone Else'.
Re: (Score:2)
Re:Where is the missing 24.1%? (Score:4, Informative)
Individuals and anonymous contributors make up for the remaining 24% according to the youtube link posted in the first comment thread.
Just out of curiousity... (Score:2)
I haven't been keeping up with linux development all that much lately, but as I was looking at some of the graphs in the report, I started to become curious as to what the data might represent. For instance, the graph showing lines of code Added, Deleted, or Modified in the 2.6.x kernels. Did something get a massive re-write in 2.6.27?
This is a straw-man myth (Score:4, Insightful)
The point is that Linux would simply not exist except for the efforts of non-paid developers. The same cannot be said of Red Hat, IBM et al.
New collaboration model? (Score:5, Insightful)
For the longest time, it seems like major business have collaborated in one of several ways:
But with Linux, it seems like a new model of collaboration for companies. It's mostly a meritocracy where a company's stature cannot get a bad or only-self-serving idea pushed into the end result. But because of that discipline, the final product is so compelling that companies want/need to participate anyway.
Am I right?
It makes sense (Score:5, Insightful)
It pays for companies using Linux to contribute to the development. The long term savings of using Linux massively outweighs the small contribution of programming resources. And those contributing to development get to address the technical issues on top of their priority list. You can't get that kind of service out of Microsoft.
We're quickly approaching the time when an operating system is more like a utility than a product. A commodity delivery mechanism for business services. The potential for Linux, very quickly approaching realization, is that it can provide a unified stack from a mainframe down to embedded systems. That type of efficiency is very powerful economically. I'm sure MSFT can swim against that tide a long time but, eventually, efficiency will win.
Re: (Score:2)
And those contributing to development get to address the technical issues on top of their priority list. You can't get that kind of service out of Microsoft.
you can, but if you need to ask "how much does it cost?", you really don't have enough money to even want to know the answer.
Does not follow? (Score:2)
Just because someone gets a check from a company, doesn't mean they're not lonely nerds hiding in their mother's basement :-)
Long tail indeed. (Score:2)
What we see here is that a small number of companies is responsible for a large portion of the total changes to the kernel. But there is a "long tail" of companies (500 of which do not appear in the above list) which have made significant changes.
Yup. The top 50 contributors (including groups for "none" and "unknown") add up to about 81.5%, meaning that those other 500 companies, added together, yield 18.5% of the code--more than any other single group.
The nerd correlation is incidental... (Score:3, Funny)
Where are the ladies? (Score:2)
From the report, it appears only men substantially contribute to kernel development. Yes, I have used listed names to come to my conclusion. Where are the women? Or am I wrong?
Who's the target audience for this report? (Score:2)
I'm trying to figure this out. Is this meant to assure businesses that Linux isn't dependent on a bunch of "lonely hackers", so they'll be more comfortable bringing it into their IT department? Or is it a response to the sorts of people that seem to turn their noses up in disdain whenever the idea of corporate involvement in Linux is brought up (Slashdot users, you know who you are)?
Or maybe it's just a public "outing" to point out, by omission, who's not "giving back to the community" sufficiently (in the
Why isn't it done yet? The bloatware problem. (Score:5, Insightful)
The Linux kernel ought to be done by now, and stable.
Drivers, file systems, and networks ought not to be in the kernel. That's a big part of the problem.
Real microkernels like QNX don't change much. USB and FireWire support were added without kernel mods, for example.
Yes, microkernels require extra copying. But copying is cheap on modern CPUs, as long as what's being copied was accessed recently and is in cache. Fear of copying cost dates from older CPU architectures, where instruction cycles mattered more than cache footprint.
Re: (Score:2)
Re:the list Before a karma whore can... (Score:5, Informative)
At least attempt to format the list, mate:
1. Red Hat: 12.3%
2. IBM: 7.6%
3. Novell: 7.6%
4. Intel: 5.3%
5. Independent consultant: 2.5%
6. Oracle: 2.4%
7. Linux Foundation: 1.6%
8. SGI 1.6%
9. Parallels 1.3%
10. Renesas Technology: 1.3%
11. Academia: 1.2%
12. Fujitsu: 1.1%
13. MontaVista: 1.1%
14. MIPS Technologies: 1.1%
15. Analog Devices: 1.0%
16. HP: 1.0%
Re: (Score:2)
How are these companies "businesses that you probably don't associate with Linux?" I've heard of at least the top 8, and they are all pro-Linux companies as far as I know.
If Microsoft was high on the list, I'd be surprised, or even Apple. IBM? Novell? Not so much.
Re: (Score:2, Informative)
In other words: RTFA
Re:the list Before a karma whore can... (Score:5, Insightful)
But since there methodology was garbage all that means is that someone using a Volkswagen email address wrote some code.
It says nothing about whether it was done as part of their employment with Volkswagen, or whether it was done out of business hours while hiding in their parent's basement.
Re:the list Before a karma whore can... (Score:4, Interesting)
But since there methodology was garbage all that means is that someone using a Volkswagen email address wrote some code.
I've been contacted personally by them to ask who my commits should be credited to. I'm not sure how many people they do that for--for people that have contributed just one or two patches, or have an obvious-looking address ("joe@bigcompany.com"), perhaps they just make the best guess they can.
I'm not necessarily defending the process--I don't recall enough of the details about the methodology (I think they've written more elsewhere, but I can't find it right now)--but they are doing more than just scraping the git commits.
Re: (Score:2)
Do you pay attention at all?
The contribution from VW was regarding CAN bus support. Do you even know what CAN bus is?
Re: (Score:3, Insightful)
I don't care at all, since it's irrelevant.
But feel free to fixate on the details of the plucked out of the air company name.
Re: (Score:3, Informative)
It's obviously relevant.
CANBUS is short for Controller Area Network. It allows different automotive sensors to communicate with subsystem modules such as anti-lock braking, powertrain control modules, and engine control units. This is a good case for where a company that uses Linux, but whose product is NOT information technology specific might want to be involved in the development of Linux.
Real-time linux has had a big push from integrated systems development, where it's either "on-time" or it fails. Auto
Re: (Score:2)
If you know this area at all you also know that the authors are extremely well connected in the kernel development circles... They probably have first hand knowledge of hundreds of the most active developers and can tell which companies are working on which drivers without consulting git.
As an example, I'm pretty sure Jonathan Corbet knows the Volkswagen deal pretty well, since he has written articles about the networking stuff they wrote (btw, as far as I can remember the VW guys didn't even use volkswagen
Re: (Score:3, Funny)
How are these companies "businesses that you probably don't associate with Linux?" I've heard of at least the top 8, and they are all pro-Linux companies as far as I know.
Can you give me some info on "Independent Consultant"? .. they sound like a company I want to work for
Re:the list Before a karma whore can... (Score:5, Insightful)
Can you give me some info on "Independent Consultant"? .. they sound like a company I want to work for
Trust me, dude, you do NOT want to work for them. You have to work tons of unpaid hours, and they make you find your customers/clients, and they rarely pay you in a timely manner, and they make you do your own taxes. It's absolutely shocking, in my mind, that no one has reported them to the Better Business Bureau... I've thought about reporting them myself, but I left on decent terms, and don't want to burn any bridges.
Re: (Score:3, Informative)
It's not in the public domain. For any patch of sufficient size, the copyrights still remain with each individual developer(I'm ignoring derivative works, as that's beyond the scope of a slashdot comment).
So let's say IBM contributes a new driver. IBM keeps the copyright to the code, but gives license to use to all Linux users via the GPL. The key here is that because IBM still has that copyright, they are free to release that same driver as a closed source product as well, whereas Sun or Oracle couldn't ta
Re: (Score:2)
Re: (Score:2, Interesting)
Anyone else notice that this list only adds up to ~50%? So what happened to the other 50? Is it spread out among other corps at 1%? When you add in the 7.6%(no affiliation given) and 18.2%(independent) you still only get ~75%. And considering Red hat only comes in at 12.3%, I would say that the largest contributors are those that aren't affiliated with a company at 18.2%.
Seems like the headline and summary is a bit misleading.
Re: (Score:2)
I'm a little surprised to see that Cannonical isn't on this list. Redhat, sure, but Cannonical has a huge marketshare.
Re: (Score:2)
canonical doesn't contribute back at all - only debian does, and even debian is not a big kernel contributor
Re: (Score:2)
3. Novell: 7.6%
I'll bet this really annoys those boycottnovell kooks.
Re:the list Before a karma whore can... (Score:4, Interesting)
Never let facts get in the way of their ramblings, especially Roy. He foams at the mouth but never actually got to the reason WHY any deal was developed. Novell tried to embrace interoperability and was told that they should join as the same deal was given to Red Hat, et al, and they thought "OK, sure, lets make this work and protect our customers."
Novell contributes code to the same thing the boycottnovell mouth breathers use every day like KDE, Gnome, SAMBA and plenty of others, along with being part of the Open Invention Network using their patent portfolio as a shield. They are, at least for now, the good guys. The future may change. Also, while some may hate Mono, it opens the door to running .NET apps on Linux so its a win in a way.
Re: (Score:2)
3. Novell: 7.6% I'll bet this really annoys those boycottnovell kooks.
Not to mention all the other stuff they do with Gnome and a few other bits. Novell may have fallen for some Microsoft shtick, and to be honest, I think a lot of that was PR fluff that Big Steve pulled out of his backside at the most strategic point. But they are still pretty big contributors to the Linux platform as a whole. Good thing the open or death fanboys are so busy telling everybody how things should be done to actually bother the people who are getting things done.
Re:the list Before a karma whore can... (Score:5, Funny)
That's nonsense. Where's SCO on that list? We all know SCO wrote a big part of the Linux kernel.
Top 10 account for 43.5% (Score:2)
So, unknown "others" are still major contributors.
Re:the list Before a karma whore can... (Score:4, Funny)
0% SCO
Re:the list Before a karma whore can... (Score:4, Interesting)
Should probably be a negative number of some magnitude. ...Last: SCO -31%
Re: (Score:2)
the list is made yearly, I doubt SCO had time this year to write something. The top list comprises only kernels 2.6.24 and above. Microsoft's code has not been accepted yet and so also not counts.
Re: (Score:2)
Here's a hint: your comment should have been posted in your slashdot journal [slashdot.org], where at least six people [slashdot.org] will see it, as they will be notified that you have written a journal. The when you make an on-topic interesting, informative, or funny comment that is modded up, your comment will have a link to your journals by your username.
Some folks just copy their homepage entries to their journals. Slashdotters are more likely to click your journal than your homepage.
Re: (Score:2)
Oh that is just great!
Our main method of communication is e-mail, and now I have to either PRINT it or send screenshots!
Thank you for the info.
Re: (Score:2)
MS Project can export to a useless read-only, single large .jpg type of html.
You could buy Collabnet's TeamForge and sync your Project plans (both ways) with a web tracker/management/etc app.
I'm sure there are online, OSS, apps that do roughly he same job.
However, at my company, the MS project plan is not shown to anyone other than the project managers, that's the easiest way to convey the information; and as developers, just the way we like it :)
Re:Small problem (Score:4, Insightful)
This is a piss-poor way to determine corporate sponsorship, especially the first one. Because someone works on the kernel and uses his work email address, it does not follow that the employer sponsored his work.
If it wasn't work, I wouldn't pass that kind of thing through my work account. Could lead to all sorts of silly questions about whether you're using work time or work code (you're already using work resources...) for this, causing you more headaches as necessary.
Once you've established that it is for work it pretty much drops out of your commit stats whether you're full-time or the lone patch contributor. I short, I don't think your criticism is very valid.
Re: (Score:2)
The proper people to ask about corporation sponsorship of Linux kernel development is HR and PA, not the employees.
Chances that HR people at my employer would have the foggiest idea how to answer this question are small.
And it's enough work tracking down individual contributors (by the email addresses they provide with commits) without having to contact someone else in each organization. Agreed that they could perhaps phrase the question better (they're just asking "who you work for"), but I think self-reporting is probably good enough.
Re: (Score:2)
surprised? well, they haven't exactly sent any patches ... gee, I wonder if they are really genuinely interested in making linux better, or just run away with it and try to make money out of it.
Look in the mirror (Score:2)
This is a problem that won't go away easily. This image is perpetuated every day by stupid people that for some reason hate open source.
OpenOffice.org has been a wholly owned subsidiary of Sun.
You see a lot of that in FOSS - but it has always been something the geek has chosen to underplay.
It strips away many of his own most deeply cherished myths - and none is more deeply cherished than that of The Cowboy, The Lone Gunman.