In bullet point form.

• We’re serious about a 1.2 release in the next few months.  As Alexandre said, “it’s time”.
• 64 bit support will be the major new release goal.
• For most people, having no regressions and working with way more apps than 1.0.1 did will be the actual feature they care about.
• Users will need to make a new Wine installation to migrate from 32-bit to 64/32-bit capable.  It is left to me to figure out and code a humane way to present this.  This is also a convenient time to make their Wine folder case insensitive.
• We’re giving up on separate Pulse/ALSA/OSS/Jack sound driver layers and instead doing the smart thing: passing everything to OpenAL.  Maarten Lankhorst will handle most of it.
• Packagers like me will have to work out CJK font support for our respective distros.  Wine will need manual links to whatever font is actually provided by the distro when it’s in a CJK locale.
• We need some help from Freedesktop.org for solving bug 10841.  Essentially we need a standard way of saying “hey reset the resolution when I’m done, even if I crash.” I was “volunteered” for the task of approaching the respective projects.
• We need user help finishing up the Tahoma replacement font.  It’s still missing some glyphs for certain languages and some users report it as “ugly”.
• VMware is an ally of Wine.  They use our test suite on Thinapp, and even contribute test fixes and new tests back to us.  Tests are just as good as “real” code.
• We need more users to run git update and winetest daily (with their screens unlocked).
• Alexander announced a new patch tracking system to prevent patches from getting lost in the nether (and for devs to know when a rejection occurs)
• By far the largest concentration of wine developers is in the netherlands.  It has something to do with being below sea level, which means global warming is an ally of Wine as well.
• Francois Gouget has promised to teach me every nuance to Winelib so that I can document it properly.
• I need to update about 10 different wiki pages to give them more modern instructions, such as how to get a good backtrace (eg on Ubuntu you install wine1.2-dbg).  A recurring theme to this conference seemed to be that if it’s written in English and concerns the Wine project, it’s probably my responsibility at this point.
• Owen is going to setup planet.winehq.org, since he’s done it before for another project.  There you’ll see my blog and a few others.  I might actually update more than once a month too!
• Andre Hentschel is working on a Wine port to ARM.  I’ll see if I can get him a first generation Pandora (I had the misfortune of preordering two about a year ago, and they may actually arrive sometime next month).
• Jeremy White wants help recognizing people who should come to wineconf.
• I need to make a proper message box to indicate that Wine is loading immediately after a user opens an application (currently there can be about 5 seconds of nothing, resulting in either frustration or opening the application multiple times).  Wine should be sending the signals it needs (with xdg message) already, we just need to have the desktop listen to them.
• I need to make a “Press” page for the website, including an email address for This e-mail address is being protected from spambots. You need JavaScript enabled to view it which will probably direct to me possibly several others.  I’m curious how other projects have handled this – is it a good idea to have multiple press contacts?
• All documentation needs to be moved to the wiki.  From there it shouldn’t be too hard to setup a wiki->pdf->docbook/xml conversion script and have the documentation build automatically based on the latest wiki pages.  Then we can start shipping it with packages again (since offline documentation still matters somewhat).
• I’m going to experiment setting up Redmine for the Wine project.  If I can get it running well on a separate server and have it fully import Bugzilla, the Wiki, and our Git repositories then we can switch to it and start using its nice management features.  Budgetdedicated will provide the server.
• The winehq.org Donation link needs to go to a proper web page that actually says where the money goes and what we’ll do when we raise enough.  Currently it just dumps you off to paypal without explanation.  Amazingly, some people actually give money (enough to partially fund WineConf).  This task is also mine.