<br><br><div class="gmail_quote">On Sun, Jul 3, 2011 at 1:37 AM, Damjan Jovanovic <span dir="ltr"><<a href="mailto:damjan.jov@gmail.com" target="_blank">damjan.jov@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div></div><div><br>
</div></div>Hi Keith<br>
<br>
Having worked at Microsoft, you of all people should appreciate the<br>
size and complexity of the driver architecture on Windows. So I would<br>
say that "failure" is mostly from the scale of the problem to be<br>
solved.<br>
<br>
My attempts at adding USB support to Wine have been painful and slow.<br></blockquote><div><br>Hi Damjan et al;<br><br>I don't know much about the USB architecture as my contributions to Windows were via RichEdit. I just know that the Linux kernel has mature USB support, WINE in general does many things, and you've got a big team now. Your contributor list shows 1250 and you've got 2M lines of code. I'm amazed at how many things work -- or almost work.<br>
<br>If you had a leaky roof in a house on fire, what would you work on first? It appears from the outside that the answer for WINE would be random.<br><br>In general, people can work where they want, but it is better if some work is prioritized. You don't need to use the buglist for this. When Linus finds a bug he needs fixed before he can make a release, he posts to the LKML and all the developers read it and the relevant ones respond. Typically he reverts, but sometimes he requests help, and he gets it within hours. He doesn't wait for someone to check in code that works.<br>
<br>You don't have to work like that. I am just pointing out that if you have goals (do not ship without certain apps working) or priorities (certain bugs are higher priority), or something, things will be better for the same amount of effort.<br>
<br>Regards,<br><br>-Keith<br><a href="http://keithcu.com/" target="_blank">http://keithcu.com/</a><br></div></div>