From kde-core-devel Wed Feb 04 11:21:20 2015 From: Martin Klapetek Date: Wed, 04 Feb 2015 11:21:20 +0000 To: kde-core-devel Subject: Re: Moving KDE Telepathy to kdenetwork Message-Id: X-MARC-Message: https://marc.info/?l=kde-core-devel&m=142304893230303 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--e89a8f3ba085cd5107050e4164c0" --e89a8f3ba085cd5107050e4164c0 Content-Type: text/plain; charset=UTF-8 On Wed, Feb 4, 2015 at 1:51 AM, Albert Astals Cid wrote: > El Dimarts, 3 de febrer de 2015, a les 00:49:17, Martin Klapetek va > escriure: > > Hi, > > > > so we decided with KDE Telepathy to join the big guys and become > > part of KDE Applications 15.04. So I'd like to request a move of > > KDE Telepathy repos[1] to kdenetwork/. This is also a mail to Urs > > Wolfer asking for approval as per the policies. > > KTP is all KF5 based at the moment, right? > Correct. > Not being a IM user myself, how does KTP compare to kopete feature wise? > I'm not sure to be honest as I don't know what Kopete can all do. KTp does not try to be a swiss army knife of IM, that's for sure, the main objectives are ease of use, simple UIs with powerful features underneath and providing good integration in Plasma. The main advantage is the architecture and backends - it's all DBus activated (and stateless) components, super easy to extend with new protocols support using Qt, GLib or Python. Plus the Telepathy project is widely adopted in the world - Unity, Ubuntu Phone, Gnome, Jolla, N9 and maybe in other places, making it proven by usage. Small downside is that it is developed mostly by Gnome folks and can suffer from being bent to their needs only. > Kopete mailing list: is there any work happening in kopete? Are you even > thinking on a port to KF5? > > > KDE Telepathy has been through kdereview once and we've kept > > the culture of "everything goes through review" pretty high up, but > > I guess that move from extragear to main module also must go > > through kdereview? The app lifecycle page[2] does not mention > > this case. > > I'd say that given it had review already and we deemed it was good enough, > we > can just skip the code review and focus on more administrative stuff :D > Worksforme :) > > > Another part that KDE Telepathy needs is KAccounts and we'd like > > to move that one too, probably to kde-runtime but there seems to be > > some disagreements of the purpose of kde-runtime. KAccounts is > > basically a KCM, a kded module and a library for writing custom plugins > > for various KAccounts functionality. So please advise where to move > > that. Also note that this was in kdereview just a month ago so I'd like > > to just skip kdereview for this as it didn't have many changes. > > Was thinking, why not kdenetwork? I mean what kind of non network related > account would you add to KAccounts? > Well I don't have a strong opinion either way. If you think it suits better in kdenetwork, then ok. And yes at this point all accounts are network related. Cheers -- Martin Klapetek | KDE Developer --e89a8f3ba085cd5107050e4164c0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On W= ed, Feb 4, 2015 at 1:51 AM, Albert Astals Cid <aacid@kde.org> wr= ote:
El Dimarts, 3 de febrer de 2015, a l= es 00:49:17, Martin Klapetek va escriure:
> Hi,
>
> so we decided with KDE Telepathy to join the big guys and become
> part of KDE Applications 15.04. So I'd like to request a move of > KDE Telepathy repos[1] to kdenetwork/. This is also a mail to Urs
> Wolfer asking for approval as per the policies.

KTP is all KF5 based at the moment, right?

=
Correct.
=C2=A0
Not being a IM user myself, how does KTP compare to kopete feature wise?

I'm not sure to be honest as I don= 9;t know what Kopete can all do. KTp does not try
to be a swiss a= rmy knife of IM, that's for sure, the main objectives are ease of use,<= /div>
simple UIs with powerful features underneath and providing good i= ntegration in Plasma.

The main advantage is the ar= chitecture and backends - it's all DBus activated (and
statel= ess) components, super easy to extend with new protocols support using Qt,<= /div>
GLib or Python. Plus the Telepathy project is widely adopted in t= he world - Unity,
Ubuntu Phone, Gnome, Jolla, N9 and maybe in oth= er places, making it proven by usage.
Small downside is that it i= s developed mostly by Gnome folks and can suffer from
being bent = to their needs only.
=C2=A0
Kopete mailing list: is there any work happening in kopete? Are you even thinking on a port to KF5?

> KDE Telepathy has been through kdereview once and we've kept
> the culture of "everything goes through review" pretty high = up, but
> I guess that move from extragear to main module also must go
> through kdereview? The app lifecycle page[2] does not mention
> this case.

I'd say that given it had review already and we deemed it was go= od enough, we
can just skip the code review and focus on more administrative stuff :D
=

Worksforme :)
=C2=A0

> Another part that KDE Telepathy needs is KAccounts and we'd like > to move that one too, probably to kde-runtime but there seems to be > some disagreements of the purpose of kde-runtime. KAccounts is
> basically a KCM, a kded module and a library for writing custom plugin= s
> for various KAccounts functionality. So please advise where to move > that. Also note that this was in kdereview just a month ago so I'd= like
> to just skip kdereview for this as it didn't have many changes.
Was thinking, why not kdenetwork? I mean what kind of non network re= lated
account would you add to KAccounts?

Wel= l I don't have a strong opinion either way. If you think it suits bette= r in kdenetwork,
then ok. And yes at this point all accounts are = network related.

Cheers
--
Martin K= lapetek | KDE=C2=A0Developer
--e89a8f3ba085cd5107050e4164c0--