Kopete in kdenetwork

Neil Stevens neil at qualityassistant.com
Sat Feb 22 12:44:36 GMT 2003

Hash: SHA1

On Saturday February 22, 2003 03:25, Ralf Nolden wrote:
> On Samstag, 22. Februar 2003 05:52, Duncan Mac-Vicar Prett wrote:
> > Hi guys,
> >
> > The Kopete team has decided its time we should move to kdenetwork if
> > we want to be included in KDE 3.2. Martijn Klingens offered himself to
> > do the move job on Tuesday night CST if you all guys agree
> >
> > I would like to hear your opinions and what do you think about Kopete
> > being in kdenetwork

No policy objections here on the core app, but as for which plugins are 
included in kdenetwork, which go to kdeaddons, and which don't go in the 
release at all, I'd say two policy questions have to be answered:

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.

> I have two comments though: libpsi and the jabber plugin. Don't forget
> to move libpsi as well, preferrably (as kopete is the only one who uses
> it) into kdenetwork/kopete.

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.

Eventually some of us want to see the to-be-renamed jabber library in 
kdelibs, but that's another matter.

- -- 
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