Code Weavers, a major Wine developer, offers a special section for pledges at their compatibility center website.The most direct method, however, is to help develop Wine itself and contribute code directly, which is exactly what Corel did for ! In any case, making a post on the Wine developers email list can go a long way.Before you install Wine, make sure that there is no previous Wine installation on your system, either from a package or from source.If you haven't yet installed Wine, you should be fine.To diagnose application problems, the first step is to run the program from the console using Wine, rather than from a GUI shortcut.This will allow Wine to output error messages to the console, the understanding of which are key to solving the problem and getting the application to work.If the application still doesn't work, it's probably due to a bug or deficiency in Wine and we'd like to hear about it.
There is no need to set DYLD_* environment variables; all paths are relative, so it should work as long as the directory structure is preserved (you can skip the /usr prefix though using --strip-components 1). See Building Wine on mac OS Note: Files in this directory are unused on mac OS unless you use a UNIX window manager and other X11 applications instead of the native Mac OS apps.
Each application should have a supermaintainer, and, if different versions of the application are substantially different (such as in Adobe Creative Suite), each subversion should have a maintainer.
If you are the developer or publisher of the application, you obviously have a very big incentive to help get your application working under Wine.
An application may not work because Wine doesn't yet fully implement one of the DLL files the application is trying to use.
If you encounter a DLL not found error, or see a lot of "FIXME:" messages while running the application in Wine, this is likely the case.