[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kopete-devel
Subject:    Re: [kopete-devel] the purpose of make-it-better (Please Read)
From:       Keef Aragon <karagon22 () comcast ! net>
Date:       2005-02-07 8:06:34
Message-ID: 4207218A.5000607 () comcast ! net
[Download RAW message or body]

Since it's on topic - I've got Yahoo webcam viewing support using code I 
dropped into libkopete and yahoo both... not sure how extendable that'll 
be into other things.  Yahoo support is still very buggy... or rather, 
has 2 severe bugs: after starting a webcam, whether it succeeds or not, 
all future receive transmissions fail (don't fail, just don't do 
anything after a request is sent to the yahoo server... all incoming 
messages from then on out don't get handled - possibly an issue with 
libyahoo2).  And if viewing a cam, closing then reopening that cam... 
segfault occurs.  I can probably fix this one pretty easily but haven't 
looked at it yet on account of the first problem.  After I have that 
implemented that I'll drop in broadcast support.  With a central 
structure (v4l only at first) inside of libkopete to be used in yahoo.  
With this as a priority, maybe there is someone out there more familiar 
with the yahoo code already there willing to help track down and kill 
this issue? ;-)

Also noting to the previous comments about concern for jpeg-2000 patent 
/ copyright issues.  I looked into it, and jpeg-2000 itself is an ISO 
format and has no legal issues in and of itself.  Lizardtech is trying 
to claim rights for a patent on HOW a jpeg-2000 images is processed... 
not the jpeg-2000 itself.

Thanks,
Keef

Matt Rogers wrote:

>Hi,
>
>I know i opened up a make-it-better branch for new stuff that we can't do 
>during the freeze, but i never really explained why i opened it for stuff 
>that could probably wait a month or so, so here it is:
>
>Right now, IMO, Kopete is in the position to overtake gaim as the primary KDE 
>IM client (if you think we're ahead, you're sorely out of touch with 
>reality). I've heard various comments about how our overall UI is nicer and 
>people like our integration with the rest of KDE. However, _every_ _single_ 
>_time_ I also hear about how Kopete doesn't have X feature that gaim has, or 
>how Kopete doesn't have Y feature that gaim has. We need to add these 
>features that gaim has that we don't. That's what make-it-better is all 
>about: Improving Kopete's support for its protocols. 
>
>Obviously, I'm not going to stop anybody from working on anything, because 
>improvement is improvement, no matter where it is. However, now is the time 
>to really improve the support for the protocols that Kopete has support for. 
>Give me a reason to make a release between KDE 3.4 and KDE 4. I want a reason 
>to make one. There won't be one if there's not a huge leap in protocol 
>support. Start implementing webcams, file transfers, group chats, chat rooms, 
>etc. Improve the functionality of the current things that are there. Make our 
>users say, "Holy shit! Kopete is awesome!" even more than they already do.
>
>Kopete's already good. Let's make it even better.
>
>Thanks,
>Matt
>
>_______________________________________________
>kopete-devel mailing list
>kopete-devel@kde.org
>https://mail.kde.org/mailman/listinfo/kopete-devel
>
>  
>

_______________________________________________
kopete-devel mailing list
kopete-devel@kde.org
https://mail.kde.org/mailman/listinfo/kopete-devel
[prev in list] [next in list] [prev in thread] [next in thread]