On Mon, 18 Dec 2006 00:09:52 -0500, Nicolas Melo wrote
> I've been a Gaim user for a couple years now, but I'm new to the
> open source developer community.
> I'm not sure if spamming everyone is the "right" way to get started,
> but if possible, I'd like to help make a dent in that daunting
> buglist on sourceforge. I'm sure the set of core Gaim developers
> has a better idea of which bugs are important to get 2.0 released so
> if anyone wants to try pushing some of those on to me, with possibly
> a little guidance, let me know... I currently work for a software
> company developing with C++ and C# in a Windows environment, but I'm
> looking to gain experience with C and Linux.
> I know it is late in the 2.0 game - and possibly no one wants to
> deal with a newbie - so if I'm not in the right place - no need to
> reply (please don't rip me a new one!)
> - nick
First off, here's a question and answer from our FAQ:
"Can I help?"
"But of course. Just find something that's bugging you and fix it. There
are a slew of a bug reports in Gaim's bug report tracker - you could pick one
and try to tackle it and submit a patch. You could also help with general bug
triage by going through the bug reports and leaving comments such as "this has
been fixed" or "this is a duplicate of bug #12345." As always, make sure you
follow the same coding style used in Gaim, and make sure you don't break the
That being said... if you're interested in devloping/fixing bugs/writing
patches, the first step is to set up a build environment on your system and
get acquainted with compiling. There are some instructions for Windows at
After that it's up to you. You could look through the bug tracker and find a
bug that looks like it'd be fun to fix. Or, here's one that might not be too bad:
1. Open edit window for a Buddy Pounce
2. 'Browse' for a command to execute or a sound to play
3. Close edit window
4. Close file browser
The fix is to change the Edit a Buddy Pounce window so that it closes the file
browser if the edit window is closed. You would need to modify the struct
that keeps information for each pounce dialog and add a pointer/handle that
keeps track of the file browser. Then, in the destroy event for the edit
window, destroy the file browser as well.
Hope that helps. Ask us if you have questions! Good luck!