Thanks Dan for expanding K and Rs full names! I now know which book to look for. Jeffz linked me to a very handy beginners windows programming site the other day http://winprog.org/tutorial/start.html which I would suggest would be your first step once you know how to write basic c applications. I've found it extremely helpful. After that it is simply a case of going to the bug list and finding nice little simple issues and spending time working out what is going wrong, how changing things effects the result, seeing if you can come up with work a rounds for the issue...And then using your built up knowledge attempting to fix the bug. I'm some where towards the end of that chain of steps so hopefully I'll be able to make meaningful contributions soon. Just remember that while on the out side the wine develops seem harsh and uninterested in helping (I remember that being my thoughts when I first started looking at helping wine) if you are making a genuine effort I've found answers to questions to be easily at hand and every one to be very helpful. Just have a go. On Fri, Mar 14, 2008 at 2:50 AM, Mark Knecht <markknecht@xxxxxxxxx> wrote: > > On Thu, Mar 13, 2008 at 2:02 AM, jingo811 <wineforum-user@xxxxxxxxxx> wrote: > > OK if this is the first step towards becoming a WineHQ code monkey what's the next step/milestone in this education ladder? It would be nice knowing before hand where one is aiming and not just read a bunch of text and not know for what specific sub-purpose? > > > > Step 1.) > > > > > > > Nope, just C. Go through "The C Programming Language" by > > > Kernighan and Ritchie, and do all the exercizes. > > > - Dan > > > > > > Step 2.) > > > > > ??? > > I am not a coder but I think the more or less consistent response to > step two is look at the list of bugs or uncoded parts of Windows > compatibility, pick one that you have an interest in, and then see if > you can figure out what's up. > > The ToDo list is here: > > http://wiki.winehq.org/TodoList > > hope this helps, > Mark > >
