Kopete in kdenetwork

Neil Stevens neil at qualityassistant.com
Sat Feb 22 13:01:23 GMT 2003

Hash: SHA1

On Saturday February 22, 2003 04:47, Duncan Mac-Vicar Prett wrote:
> El Saturday 22 February 2003 09:44, Neil Stevens escribió:
> > Should KDE include anything that is tied to a proprietary protocol? 
> > If not, Kopete plugins like OSCAR should remain in kdenonbeta.
> > Should KDE include anything is tied to a proprietary service (open
> > protocol or not)?  If not, Kit should be moved out, and several Kopete
> > plugins should remain in kdenonbeta.
> uhm... I think KDE should focuse in end-user, and end user wants to chat
> in MSN, icq, AOL, and they don't care religious issues. As long the
> plugins are compatible in terms of code license I see no problems.

Some of us don't think promoting AOL, Microsoft, or Yahoo services exactly 
help the end-user.

> > libpsi is nowhere near ready for a KDE release yet, therefore the
> > jabber plugin should stay in kdenonbeta or thereabouts.  It uses
> > nothing in kdelibs, and even has its own SSL implementation.  Justin
> > Karneges, Till Gerken, and I have been looking at ways to make it
> > useful for KDE apps witout forking, but nothing has been produced yet.
> libpsi is very stable, I don't know if you use Kopete jabber plugin, but
> I use it daily, not feature complete but thats not part of KDE policy.
> The KDE integration can be done slowly, but having it in KDE would
> promote jabber usage more.

The author disagrees with the state of libpsi.  Justin plans to remove it 
from public CVS soon, to rename and rewrite a lot of it.

- -- 
Neil Stevens - neil at qualityassistant.com
"Distinctions by race are so evil, so arbitrary and insidious that a
state bound to defend the equal protection of the laws must not allow
them in any public sphere." -- Thurgood Marshall
Version: GnuPG v1.2.1 (GNU/Linux)


More information about the kde-core-devel mailing list