Lots of pretty mockups though.
Not to derail the conversation too much, but Inkscape also needs some improvement where UI is concerned, many things that should be easy are not.
Granted it's fantastic once you know how to use it, but good luck with that.
That being said, one thing they did EXTREMELY well was put shortcut keys on all of the things that you do frequently. After doing Inkscape for a while I get really frustrated by the lack of easy navigation.
First, to switch between different applications, OS X just uses application switching whereas Windows and GNOME/KDE use window switching. IMO, window switching is a terrible design decision because it clutters the application switcher and the taskbar/dock and breaks operations that should logically apply to entire applications (quit, hide, Exposé etc.) Another desktop OS that uses application switching instead of window switching is Haiku (a BeOS descendant). Anyhow, if GIMP ran on OS X, you wouldn't need to sift through a bunch of separate windows when you wanted to focus on GIMP. You'd just switch to GIMP the application instead of separately bringing each of GIMPs eighty seven windows to the front first.
Second, when a document based application loses focus, OS X will hide all floating toolbars and panels and all you will see are your document windows. In Exposé, too, all floating panels and toolbars are hidden. This would mean GIMP's myriad tool windows would become invisible when you switched from the GIMP to another application, or when you viewed GIMP's windows in Exposé. No more needles visual clutter!
Third, OS X has a top menubar. This means each of GIMP's windows wouldn't need to have a separate menubar. The global menubar would enable and disable menu entries as you focused on different windows.
I'll be happy when the single-window version is released.
window management should be handled by the window manager, not by each application.
Also, there are no standards for schools of design. There is no professional course that teaches the basics of ergonomics for the web the same way architectural web development can be taught. Most of the people like myself just follow a few major blogs.
I know many designers who would love to donate to open source projects.
There are schools that offer courses in interaction design. In addition many visual communication courses offer interaction design in addition to the usual print oriented design.
I think OSS in general could benefit from giving a designer such broad-brush authority over an entire ecosystem.
2. Make it discrete - What needs to be designed? The entire UI and workflows? The application icon? The internal navigation glyphs? Redesigning an entire app that has tens or hundreds of contributors can be daunting, but getting someone started with something small can be a gateway.
3. Leave it alone - One of the other commenters mentioned how a designer contributed something and then it was overwritten and ruined. Typically you don't want to have dozens of designers all working on a project unless there are fairly strict guidelines to work from. Have a working group at the beginning that can set the UI tone and create guidelines from that. Also a small review committee to review changes is smart, just as they do for code.
4. Version Control for Dummies - Put together a short explanation of how to use the version control system of choice, assuming no knowledge beyond Photoshop. Or find someone on the technical side who can be an intermediary/GIT trainer. The human part of this is very important.
Do those things and you should see prettier projects in the future. I know I'd love to get involved, but have no idea where to get started!