Pidgin

Gaim can also use one more developer.  There is a pretty steep learning curve,
in my opinion, but if you're really interested in helping, I'd suggested
checking out a copy of Gaim cvs and going from there.  I've already got my
brain around file transfer and file sharing for AIM, so I'd stay away from
that.  I'm not sure if anyone is actively doing anything for the other protocols.
-Mark

On Sat, 10 May 2003 17:13:05 -0400, Julien Barnoin wrote
> Hi everyone !
> 
> I've been using gaim for quite some time now, and I'm really pleased 
> with it, except that I'd really like to be able to transfer files. 
> So I thought I'd try to help getting it to work, if I can. I'm 
> pretty good at C and have experience in network programming under 
> both linux and windows. Can I be of any help? Or if enough people 
> are working on that, I'd be glad to help in an other area. I've 
> never participated in a Sourceforge project yet though, so I don't really
> know where I should start... so if someone can help me get started,
>  please do :)
> 
> jb

--
O      O  Mark Doliner
 \     |    mark@...
  \    |      http://www.kingant.net
"I'd rather be rich than stupid."

On Mon, May 12, 2003 at 11:35:19PM -0500, Mark Doliner wrote:
> Gaim can also use one more developer.  There is a pretty steep learning c=
urve,
> in my opinion, but if you're really interested in helping, I'd suggested
> checking out a copy of Gaim cvs and going from there.  I've already got my
> brain around file transfer and file sharing for AIM, so I'd stay away from
> that.  I'm not sure if anyone is actively doing anything for the other pr=
otocols.
> -Mark

I'm developing the MSN prpl, and I believe Paco-Paco is working on the
IRC module.

The learning curve really is steep. My advice is to find something you
want in gaim and find out how to make it happen. Keep in mind that
everything must be core/ui split. If you're implementing anything new,
that's important to consider. If you have any questions about doing
that, I can help answer them.

Christian
=20
--=20
Christian Hammond         <>  The GNUpdate Project
chipx86@...      <>  http://www.gnupdate.org/
   0x2B | ~0x2B
      -- Hamlet

En r=E9ponse =E0 Christian Hammond <chipx86@...>:
> On Mon, May 12, 2003 at 11:35:19PM -0500, Mark Doliner wrote:
> > Gaim can also use one more developer.  There is a pretty steep learni=
ng
> curve,
> > in my opinion, but if you're really interested in helping, I'd sugges=
ted
> > checking out a copy of Gaim cvs and going from there.  I've already g=
ot my
> > brain around file transfer and file sharing for AIM, so I'd stay away=
 from
> > that.  I'm not sure if anyone is actively doing anything for the othe=
r
> protocols.
> > -Mark
>=20
> I'm developing the MSN prpl, and I believe Paco-Paco is working on the
> IRC module.
>=20
> The learning curve really is steep. My advice is to find something you
> want in gaim and find out how to make it happen. Keep in mind that
> everything must be core/ui split. If you're implementing anything new,
> that's important to consider. If you have any questions about doing
> that, I can help answer them.
>=20
> Christian

Thanks, Christian and Mark!
Ok, I've read the HACKING file, which I hadn't noticed at first... many
interesting things, it basically got me started (in understanding the cod=
e at
least). Now I'm getting more familiar with the code, reading and understa=
nding
parts... might take some time... I hope I'll be able to help.
I'm glad to hear that AIM, MSN and IRC transfers are being developed. I'l=
l see
if i can do anything for ICQ or Yahoo, then. Or other things...
Oh, and what's the procedure? Once I change something and am satisfied, w=
here
should I post/who should i email the patch?

Julien

On Tue, May 13, 2003 at 02:13:50PM -0400, Julien Barnoin wrote:
> En r?ponse ? Christian Hammond <chipx86@...>:
> > On Mon, May 12, 2003 at 11:35:19PM -0500, Mark Doliner wrote:
> > > Gaim can also use one more developer.  There is a pretty steep learning
> > curve,
> > > in my opinion, but if you're really interested in helping, I'd suggested
> > > checking out a copy of Gaim cvs and going from there.  I've already got my
> > > brain around file transfer and file sharing for AIM, so I'd stay away from
> > > that.  I'm not sure if anyone is actively doing anything for the other
> > protocols.
> > > -Mark
> > 
> > I'm developing the MSN prpl, and I believe Paco-Paco is working on the
> > IRC module.
> > 
> > The learning curve really is steep. My advice is to find something you
> > want in gaim and find out how to make it happen. Keep in mind that
> > everything must be core/ui split. If you're implementing anything new,
> > that's important to consider. If you have any questions about doing
> > that, I can help answer them.
> > 
> > Christian
> 
> Thanks, Christian and Mark!
> Ok, I've read the HACKING file, which I hadn't noticed at first... many
> interesting things, it basically got me started (in understanding the code at
> least). Now I'm getting more familiar with the code, reading and understanding
> parts... might take some time... I hope I'll be able to help.
> I'm glad to hear that AIM, MSN and IRC transfers are being developed. I'll see
> if i can do anything for ICQ or Yahoo, then. Or other things...
> Oh, and what's the procedure? Once I change something and am satisfied, where
> should I post/who should i email the patch?

you can send the patch here or you can post it to the patch tracker on 
our sf project page. basically it works thusly: anyone of us will commit 
a patch fixing a bug. a patch adding a feature though will be directed 
to the attention of whoever is handling that body of code. thus icq for 
instance, being handled by oscar (libfaim) will go to kingant, and a new 
msn patch to chipx86. 

don't work with the icq prpl code, that's the old protocol that the 
servers don't really support now. work towards icq within the framework 
of libfaim (the src/protocols/oscar directory).

and as chipx86 said, feel free to ask questions.
luke

> 
> Julien
> 
> 
> -------------------------------------------------------
> Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
> The only event dedicated to issues related to Linux enterprise solutions
> http://www.enterpriselinuxforum.com
> 
> _______________________________________________
> Gaim-devel mailing list
> Gaim-devel@...
> https://lists.sourceforge.net/lists/listinfo/gaim-devel

> don't work with the icq prpl code, that's the old protocol that the 
> servers don't really support now. work towards icq within the framework 
> of libfaim (the src/protocols/oscar directory).
> 
> and as chipx86 said, feel free to ask questions.
> luke
> 

If this code is obsolete, then why isn't it removed ?

Budtse

On Tue, May 13, 2003 at 08:47:25PM +0200, Peter Budts wrote:
> > don't work with the icq prpl code, that's the old protocol that the 
> > servers don't really support now. work towards icq within the framework 
> > of libfaim (the src/protocols/oscar directory).
> > 
> > and as chipx86 said, feel free to ask questions.
> > luke
> > 
> 
> If this code is obsolete, then why isn't it removed ?

good question. removing it is rob's call.
luke

> 
> Budtse
> 
> 
> 
> -------------------------------------------------------
> Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
> The only event dedicated to issues related to Linux enterprise solutions
> http://www.enterpriselinuxforum.com
> 
> _______________________________________________
> Gaim-devel mailing list
> Gaim-devel@...
> https://lists.sourceforge.net/lists/listinfo/gaim-devel

Luke Schierer wrote:

>On Tue, May 13, 2003 at 08:47:25PM +0200, Peter Budts wrote:
>  
>
>>>don't work with the icq prpl code, that's the old protocol that the 
>>>servers don't really support now. work towards icq within the framework 
>>>of libfaim (the src/protocols/oscar directory).
>>>
>>>and as chipx86 said, feel free to ask questions.
>>>luke
>>>
>>>      
>>>
>>If this code is obsolete, then why isn't it removed ?
>>    
>>

I had a reason for not removing it, but honestly, I can't remember 
anymore...

I'm in favor of keeping it.  Mostly because it still works (even if it is not compiled/
installed).
-Mark

On Tue, 13 May 2003 15:15:24 -0400, Luke Schierer wrote
> On Tue, May 13, 2003 at 08:47:25PM +0200, Peter Budts wrote:
> > > don't work with the icq prpl code, that's the old protocol that the 
> > > servers don't really support now. work towards icq within the framework 
> > > of libfaim (the src/protocols/oscar directory).
> > > 
> > > and as chipx86 said, feel free to ask questions.
> > > luke
> > > 
> > 
> > If this code is obsolete, then why isn't it removed ?
> 
> good question. removing it is rob's call.
> luke
> 
> > 
> > Budtse

--
O      O  Mark Doliner
 \     |    mark@...
  \    |      http://www.kingant.net
"I'd rather be rich than stupid."

On Tue, May 13, 2003 at 02:29:06PM -0500, Mark Doliner wrote:
> I'm in favor of keeping it.  Mostly because it still works (even if it is=
 not compiled/
> installed).
> -Mark

Not anymore. I purposefully didn't port it to the new plugin API, so
that any copies of libicq.so sitting around would just fail to load
and thus not show up in the protocols list. I felt this would
eliminate the problem of all these people yelling at us when their
libicq wasn't working as they thought it should :) Porting it is easy.
I just don't feel it's wise, but I guess as long as a person has to
manually go in there and compile/install it, rather than that
happening automatically, it's no big deal, since they _should_
(keyword: should) know what they're doing at that point.

Christian
=20
--=20
Christian Hammond         <>  The GNUpdate Project
chipx86@...      <>  http://www.gnupdate.org/
   The surest sign that intelligent life exists elsewhere in the universe is
   that it has never tried to contact us.
      -- Calvin and Hobbes

On Tue, 13 May 2003 13:49:17 -0700, Christian Hammond 
<chipx86@...> wrote:
> On Tue, May 13, 2003 at 02:29:06PM -0500, Mark Doliner wrote:
>> I'm in favor of keeping it.  Mostly because it still works (even if it 
>> is not compiled/
>> installed).
>> -Mark
>
> Not anymore. I purposefully didn't port it to the new plugin API
...
> happening automatically, it's no big deal, since they _should_
> (keyword: should) know what they're doing at that point.

Uh, Can I suggest putting a big README (in all caps) file in the directory,
that says "this is obsolete code, use ../oscar to access ICQ instead".  
Even better, remove it from the distribution, except for a README that says 
"obsolete code, see CVS".

No reason to have things clutter up without documentation on /why/ they're 
let fallow.
Sometimes, it's hard to tell the difference between an Environmental 
Studies Lab and
a corner of the yard that nobody wants to mow.

	-=-James Mastros