where do I go to find out who needs help

Francois Gouget fgouget at free.fr
Wed May 9 12:17:20 CDT 2001

On Wed, 9 May 2001, Andreas Mohr wrote:

> On Wed, May 09, 2001 at 05:09:20AM -0700, Sean Callahan wrote:
> > Hi,
> >    I want to do some work for this project who do I mail 
> > Regards,
> >        seanie at www.com
> Well, I'd say that depends on what you're able to do ;-)
> At the moment I could imagine e.g. the following items:
> - web server maintenance/update work
> - improvement of documentation (this badly needs fixing !!)
> - dlls/shlwapi/reg.c: implementation of user-specific registry stuff
>   (e.g. needed by IE 5)
> Multiple choice time :-)

   Hmmm, I think I can also find a list of bugs in bugzilla that could
easily be fixed by someone new to Wine:


 * Builtin msvcrt mishandles the cmdline to argv conversion
   #234: http://wine.codeweavers.com/bugzilla/show_bug.cgi?id=234
   This prevents 'wine /mnt/win/Program\ Files\whatever\foo.exe' from
   working if you're using the builtin msvcrt!

 * I'm almost 100% certain that there's another bug in the same function
   in its handling of the environment variable.

 * PrgWin95/98: System metrics differ from the Win9x values
   #48: http://wine.codeweavers.com/bugzilla/show_bug.cgi?id=48
   One day I'll fix this one... I swear. Unless you want to work on
   it first. In that case I'll provide you with my test application and
   dumps of the metrics for Win95, Win98, NT4, ...

 * The doc about the command line arguments and the config file is out
   of date. I'm sure there are plenty of other things that are out of

 * Get the VXCL samples, test them with Wine and report the bugs in the
   bugzilla database. I know there's lots of them. Then people (or
   yourself) can start fixing these bugs in a distributed fashion.

 * PrgWin95: Listbox getting a recessed border instead of a flat one
   #56: http://wine.codeweavers.com/bugzilla/show_bug.cgi?id=56
   (I can provide you with the sample application)

 * I think it would be nice to add a tool that displays the dlls version
   information like 'About' does in the windows explorer. I have some
   code you could use as a starting point and I think it could be
   merged with winver. In fact this would be almost stabdard windows

 * There's a bug in the drawing of the border of the common control
   tabs. Fixing each of the four instances of the code is easy. It would
   be interesting to find a way to factorize some of this code.

Medium (I expect these would take longer or be a bit harder)

 * Provide a pedump utility
   #91: http://wine.codeweavers.com/bugzilla/show_bug.cgi?id=91
   I know there's sample code that does that already floating around so
   it should be relatively simple.

 * wrc fails on preprocessed files
   #115: http://wine.codeweavers.com/bugzilla/show_bug.cgi?id=115
   I believe it's just a grammar problem. You'll need to know
   (or to get cozy with) lex/yacc...

 * CreateIcon does not resize bitmaps
   #175: http://wine.codeweavers.com/bugzilla/show_bug.cgi?id=175
   I did a similar fix somewhere some time ago. I can provide a
   sample application and I might be able to point you in the right 

 * winemaker: 'winemaker --nomfc' does not have the intended effect
   #227: http://wine.codeweavers.com/bugzilla/show_bug.cgi?id=227

 * winemaker: Ignores the '--with-{mfc,wine}' options once they are
   #225: http://wine.codeweavers.com/bugzilla/show_bug.cgi?id=225
   If you're familiar with autoconf and know how configure scripts
   should behave...

 * StrokePath ignores PS_JOIN_xxx
   #11: http://wine.codeweavers.com/bugzilla/show_bug.cgi?id=11
   This should not be too difficult to fix but it would certainly help
   if you are familiar with GDI.

 * Checking the differences between what's in the Windows dlls and
   what's in our spec files... and fix the contents of our spec files
   as appropriate. I already have a list of all the APIs in
   each of the dlls for Win95, Win98, NT4 and Wine2000, plus a script
   that can show the differences.

 * Enhancing the above perl script.

   But let us know also what kind of work you would like to do and what 
kind of things you're best at:
 - C programming
 - Debugging
 - Windows programming
 - tweaking shell scripts
 - writing/fixing documentation
 - doing web stuff

   It also depends on what motivates you: getting an application to
work, implementing some new functionality, getting applications to
compile, fixing scripts, fixing documentation or writing new
   And the last parameter is how much time you have for Wine
work. In any case it's probably better to start with something simple to
see if you like it.

Francois Gouget         fgouget at free.fr        http://fgouget.free.fr/
The nice thing about meditation is that it makes doing nothing quite respectable
                                  -- Paul Dean

More information about the wine-devel mailing list