Howdy,

I am a C and C++ programmer -- how can I start helping with some basic coding for wine?

Thanks,
Will

On Fri, Feb 29, 2008 at 9:16 PM, willz06jw <wineforum-user@winehq.org> wrote:

Check out this list to see what needs to be worked on:

http://wiki.winehq.org/TodoList


--
James Hawkins

Thanks James,

OK, I am going to try to fix an item in Janitorial Projects. This is my first open-souce project to work on. How do I find guidence to get me up to speed on the project/item I am working on?

I will work on the first item, 16-bit Seperation.

Thanks again,
Will

On Fri, Feb 29, 2008 at 9:34 PM, willz06jw <wineforum-user@winehq.org> wrote:

You could work on that one, but you might have better luck picking
something else. Here is a list of no-experience-required items:

CompilerWarnings
ConstifyData
CreateInstanceAggregationCheck
CrossCallsWtoA
DebugTracingCleanup (DPRINTF)
DllCanUnloadNow
IgnoredReturnValues
Links
LongLongPrintfs
MemoryLeaks
PortabilityFixes
RegeditFixes
ReplaceMalloc
SpecDiscrepencies
StandardizeAutoconfMacros
Stubs

--
James Hawkins

On Fri, Feb 29, 2008 at 9:23 PM, James Hawkins <truiken@gmail.com> wrote:

You could also dig through the bugzilla and triage/fix bugs you find
interesting:

http://bugs.winehq.org


--
James Hawkins

On Fri, Feb 29, 2008 at 7:47 PM, James Hawkins <truiken@gmail.com> wrote:

+1 on that idea, and on http://wiki.winehq.org/MemoryLeaks
Both much more useful than 16 bit separation.
- Dan

What is the simpest item on that list? What should I do first? Is there someone I should contact to better understand the item?

Thanks again,
Will

On Fri, Feb 29, 2008 at 9:55 PM, willz06jw <wineforum-user@winehq.org> wrote:

Pick one and try it out. Hand-holding will only get you so far We
all had to start somewhere...

--
James Hawkins

Just take a windows program you want to run on Linux under Wine and try to fix it. This is the way how everyone started working on Wine. Any to-do lists would be hard to impossible to decipher until you start hacking Wine yourself.

On Fri, Feb 29, 2008 at 10:27 PM, vitamin <wineforum-user@winehq.org> wrote:

Not true at all. I started with the CrossCallsWtoA task, and it was a
good way to climb up the steep learning curve. I worked for at least
two years without working on any program (advpack, hhctrl.ocx, et al.)

--
James Hawkins

You are special case And I didn't say most developers actually did fix their programs or still working on them - that's a rarity. Most of those apps still don't work right or at all.

It doesn't matter where you start. Just pick a program/task/bug and try to work on it. Dig into the source to understand what it's doing. Oh and before you get too far, show you patches to wine-devel list. People will have some comments for you.

Is there any type of change mgmt system used? How do you know if someone else is working on the same thing?

On Sat, Mar 1, 2008 at 1:11 AM, willz06jw <wineforum-user@winehq.org> wrote:

Ok, so at this point you need to take some time and read through
winehq.org, as all of the next 100 questions you could ask have
answers on the web. We've given you some tips on what to work on, now
it's your turn to make some moves.

--
James Hawkins

I second that. Wine Developer's Guide, Developers-Hints and Wine-devel mailing list are the good places to find lots of useful information.

To avoid conflicts - ask who is working on a thing you are interesting in on wine-devel mailing list.