No idea what boatloaders are, but I'm all for it !

They are typically members of the longshoremen's union. Contrary to popular belief, they have a very high degree of computer literacy.

I already apologized for my typo, but I'm not going to change it---it's fun getting these little zaps.....

I find this quite interesting... I would love to work towards correcting some of these... I've done a little bit of development in the past, but really need to find something to sink my teeth into.

A lot of the dialog leading up to this was about having an Action Plan to follow up the wish list. Clearly, individuals getting involved with specific SW projects is an important component.

After we have squeezed the last input out of our LQ community, I think we need some follow-up threads discussing how people can contribute.

Keep the inputs coming!!!

PS: At first I found it curious that one of the most often asked questions at LQ (booting) is at the bottom of the priorities. I have a theory to explain this, but would like to hear other thoughts.

I'm all ears(or eyes)..!!

My theory: bootloaders are something you generally toy with once and then it works. Other things have a habit of 'changing' over time.

And booting is a problem with most of the dual-boot cases, most of the time. For complete Linux users, its never an issue.

I voted more and better drivers and better wireless support.

I think it would be nice to have a laptop where everything worked, with minimum effort, with Linux. Most laptops that I have come across with Linux have issues with suspending when the lid is closed and also other power management. Also, most laptops have wireless these days, so it would be nice to easily get Wireless working.

Graphics drivers are another issue - I would rather use the "free" Nvidia drivers than the binary ones, but they don't work.

I know these are both issues for manufacturers as opposed to the OSS comunity.

--Ian

One thing that I was not fast enough to mention when you were creating the poll but I think would be helpful.

Better documentation or simplifying some of the kernel configuration

Back in 2.4 I could basically figure everything out but now in 2.6 there is more stuff there that is kind of obscure when trying to configure a kernel. Especially with the one wire buss stuff like temp control.

Maybe this could be placed under Documentation and that is one of the things that I voted for.

1) More and Better Drivers
Specifically, vendor supported drivers. My thought is that if some one has an $VENDOR $PRODUCT and needs hardware/driver support or warranty work they should be able to contact $VENDOR for that support.

action:
Requesting (or Requiring as a condition of purchasing) support and drivers from both hardware Manufacturers and Distributors

More and better drivers should be "open" drivers...not binary.

jhibbets, I disagree. I think Drivers should work before developers start worrying about licenses.

If a hardware manufacturer does not want to release source code for their drivers that is their choice, just as it is your choice whether or not to support that company. I think the priority should be to get working drivers, then, after we have the drivers, and hardware companies can no longer feign ignorance of this OS and OSS, we can start to add pressure for the Opening of those Drivers.

I do think that free distribution should get some attention though, it would be great if a distribution could legally include proprietary drivers without worrying about a distribution license. Downloading and installing the nvidia driver (or the ATi driver) can get tedious if you're a distro hopper.

I disagree. I run linux for Open Source softwares, for the freedom even more than for the performance.

It's their choice to not give the specification of their hardware or to bother($$) developping themselves their drivers, then it's my choice to not buy it and check carefully before buying.
I've been developping drivers a few years ago and I was in contact with several manufacturers. On one side they don't give you specs and on the other side they are not able to develop descent drivers. So I had to reverse-engineer eventhough it was illegal. I hate them.
I prefer no support rather than binary driver, otherwise I would have stayed in winblows. It's a bit selfish for those unlucky that bought crappy hardware but then next time they will know how to buy their box.

I voted Wireless support.

So I would tend to agree with much of what you said as well. I think the most fustrating thing about Linux is when things don't work. Other Oper. Systems make things easy, like installing apps or drivers. A typical end-user is not going to have the skill set to troubleshoot an underlying issue. If something doesn't work, whether it's a hardware device, and installation of an application, or whatever, that user gets a bad taste. They may not "get it" at that point and get fustrated.

I'd like to see a trend from the manufactorers to develop the open source drivers first, then add their propriatary crap in it. Reverse the model to speed up the development cycle. They drivers, I think, would be much better and hopefully, more standards based.

I wanted to vote for "more and better drivers" and "improvements to wine, so gamers don't have to dual-boot Windows", but sadly there was nothing remotely resembling that second option.