Re: [Telepathy] Project revival?
> I have reached out to jdev mailing list, as well as the author of > XMPP > Desktop Screen Sharing in Empathy. Unfortunately I was not able to > get > any major attention. I believe that the Empathy developers were also the original Telepathy team as well, so its not surprising you didn't hear much them. I'm currently fixing some stabs at fixing at least a few issues in Empathy, I'm not sure I'll have the time to do much more than bug fixes though. > > Fixing one2one Desktop Screen Sharing should be fairly simple, but > it > would be nice if we could do it in a standardized/interoperable way > so > it will work between different XMPP-clients. Compatibility would be awesome. (It's the thing XMPP was historicaly bad at). ___ telepathy mailing list telepathy@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/telepathy
Re: [Telepathy] Project revival?
On 06/11/2016 09:04 AM, Alexandr Akulich wrote: > On Fri, Jun 10, 2016 at 9:43 PM, Alexandr Akulich >wrote: >> Hi George, >> >> Can you review commits [3], [4], please? >> >> [3] >> https://github.com/TelepathyQt/telepathy-qt/commit/8864249479ea2adbb5c88378aa082fa18d55f6b0 >> [4] >> https://github.com/TelepathyQt/telepathy-qt/commit/d9354dfe8cca364e4a8c3a44c302ceb714c53911 >> Ack to both. > > I'm writing NEWS for the 0.9.7 release and thus checking bugzilla for > TpQt related bugs and just found exists bugreport [1] for my fix [2]. > > Can someone confirm that my fix isn't worse than the patch, attached > to the bugreport? > > [1] https://bugs.freedesktop.org/show_bug.cgi?id=65981 > [2] > https://github.com/TelepathyQt/telepathy-qt/commit/d9354dfe8cca364e4a8c3a44c302ceb714c53911 Your patch may not be entirely correct because for some reason all the tpqt_*_generator calls have a DEPENDS some-xincludator, which is what the other patch uses to depend onto, while you depend directly on the spec files. However, this xincludator DEPENDS seems unused and to be honest I don't understand it at all, so for the time being I would say I prefer your patch, since it's cleaner. If you can confirm that it fixes the issue, then that's it. I plan to take a closer look at this build system soon, since it's one of the things that have annoyed me the most in the past. I think it can be simplified a lot. > Do anyone have an idea for codename for the release? Not really, but you can be creative, I'm sure :) Something that relates perhaps to your decision to make the release, or something that relates to the season, or something with the features / bugfixes? Regards, George ___ telepathy mailing list telepathy@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/telepathy
Re: [Telepathy] Project revival?
On Fri, Jun 10, 2016 at 9:43 PM, Alexandr Akulichwrote: > Hi George, > > Can you review commits [3], [4], please? > > [3] > https://github.com/TelepathyQt/telepathy-qt/commit/8864249479ea2adbb5c88378aa082fa18d55f6b0 > [4] > https://github.com/TelepathyQt/telepathy-qt/commit/d9354dfe8cca364e4a8c3a44c302ceb714c53911 > I'm writing NEWS for the 0.9.7 release and thus checking bugzilla for TpQt related bugs and just found exists bugreport [1] for my fix [2]. Can someone confirm that my fix isn't worse than the patch, attached to the bugreport? [1] https://bugs.freedesktop.org/show_bug.cgi?id=65981 [2] https://github.com/TelepathyQt/telepathy-qt/commit/d9354dfe8cca364e4a8c3a44c302ceb714c53911 Do anyone have an idea for codename for the release? ___ telepathy mailing list telepathy@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/telepathy
Re: [Telepathy] Project revival?
Hi George, I'm using github [1] as a platform for TelepathyQt-related projects development and we have some kind of "dev" branch of tp-qt here too [2]. For sure, fd.o is the only official TpQt host, while github repo is an "experimental fork" with untested and WIP features, which is open for pull requests and direct commits from some more devs. I review changes and push them to fd.o. Actually, only Niels Ole Salscheider used this opportunity so far. That said, I just pushed changes to github. Can you review commits [3], [4], please? I think we can release 0.9.7 this weekend. I'll check (again) distributives for possible patches, fulfil changelog entry, check Qt4 / Qt5 build and make release. [1] https://github.com/TelepathyQt [2] https://github.com/TelepathyQt/telepathy-qt [3] https://github.com/TelepathyQt/telepathy-qt/commit/8864249479ea2adbb5c88378aa082fa18d55f6b0 [4] https://github.com/TelepathyQt/telepathy-qt/commit/d9354dfe8cca364e4a8c3a44c302ceb714c53911 On Fri, Jun 10, 2016 at 10:00 AM, George Kiagiadakiswrote: > Hi Alexandr, > > On 09.06.2016 22:58, Alexandr Akulich wrote: >> >> Hi George, >> >> It's great to hear about more devs get work on Telepathy. >> >> I'm TelepathyQt maintainer for a year now and I'm planning to release >> 0.9.7 as soon as I'll made a future-proof commit with fix of >> https://bugs.freedesktop.org/show_bug.cgi?id=95376 for Qt-5.8. >> >> It would be helpful if someone would acknowledge or review my changes. > > > I'm definitely up for that. :) > > >> Since commit [1] there is no QDBusArgument operators overload for >> QList. I reported the problem [2] and it seems that the "bad" commit >> will be reverted for 5.7, but our current approach is deprecated since >> [3]. >> >> I'm going to change tools/qt-types-gen.py script to generate such >> operators in types-body.hpp: >> >> TP_QT_EXPORT QDBusArgument <<(QDBusArgument , const UIntList >> ) >> { >> int id = qMetaTypeId(); >> arg.beginArray(id); >> for (int i = 0; i < list.count(); ++i) { >> arg << list.at(i); >> } >> arg.endArray(); >> return arg; >> } >> >> TP_QT_EXPORT const QDBusArgument >>(const QDBusArgument , >> UIntList ) >> { >> arg.beginArray(); >> list.clear(); >> while (!arg.atEnd()) { >> uint item; >> arg >> item; >> list.append(item); >> } >> arg.endArray(); >> return arg; >> } >> >> As far as I see, this would be a full equivalent to the current >> behaviour, but I didn't fully tested it yet. >> >> Would you acknowledge such approach or I'm missing something >> important? Comment in types.h says that we "needed to have a discrete >> type in the Qt type system" and we actually do qDBusRegisterMetaType >> in types-body.hpp, but at the same time we're relying on QList stream >> operators overload, which ignores any T parts except the base and has >> no references to the original list object metatype. > > > As far as I understand, the argument "ignores any T parts except the base" > does not apply to our type here because T is int and int is a native type > that doesn't need further operator overloads. But I can see how for the > generic case it's true. > > In any case, I think your approach is sane. Please go ahead and ping me for > a review if you wish. > > Regards, > George > > >> >> [1] >> >> http://code.qt.io/cgit/qt/qtbase.git/commit/?id=5f542f3cca13f2da58b82aee2efbaffefeee00a7 >> [2] https://bugreports.qt.io/browse/QTBUG-53376 >> [3] >> >> http://code.qt.io/cgit/qt/qtbase.git/commit/?id=c7d4858c921c7602dc90d56cdd903cd2cbc6 >> >> On Thu, Jun 9, 2016 at 8:02 PM, George Kiagiadakis >> wrote: >>> >>> Hello all, >>> >>> For those of you that don't know me, I'm an old kde-telepathy & >>> telepathy-qt developer who's been inactive in telepathy for a couple of >>> years. Recently I've been looking again into what is going on in this >>> project and it looks like it's dead, which is a pity. However, I can see >>> there is some limited activity around telepathy-qt, with some people >>> writing new Qt-based CMs (cool!). This little activity makes me hope >>> that maybe it's possible to revive the rest of the project? >>> >>> I'm basically writing this email to declare my interest in attempting a >>> revival. I think free communication is quite important and it's being >>> neglected a lot recently in the FOSS world, which motivates me enough to >>> spend some time again in this project. >>> >>> As a start, I would like to get in touch with all of you who are still >>> working on something related to telepathy. It would be nice to start a >>> conversation about project needs and future plans. So, if you are >>> interested, please get in touch. I am 'gkiagia' on irc and various other >>> places on the internet. >>> >>> Regards, >>> George >>> ___ >>> telepathy mailing list >>> telepathy@lists.freedesktop.org >>>
Re: [Telepathy] Project revival?
Hi George, Answers below: On 10/06/16 06:42, George Kiagiadakis wrote: Hello Niklas, On 09.06.2016 18:55, Niklas Andersson wrote: Hi George, We have a project going on that might be of interest. We have worked like crazy to basically bring feature-parity between MS Lync and Pidgin (using the SIPE-plugin) Think of it as the MS Lync client (or Skype for Business), but fully open source, directly available in your software repository. That's all super cool. I am interested to hear about all the XMPP additions as well as upstreaming all necessary changes to allow this to work in telepathy as well. I'm sure interested to try and participate in talks about the XMPP semantics. Regarding empathy, as far as I remember, desktop sharing was working with vino & vinagre through telepathy stream tubes. I guess though you are talking about some more standardized way? Yes. The standardization work needs to be done in XEP-0167: Jingle RTP Sessions [1]. We need to sort out during initial hand-shake which protocol/application/codec should be used. For example I believe RDP delivers a more rapid, crisp experience suitable for desktop screen sharing. A small example to get the idea through. (We apply the SIP nomenclature from Lync applied in XMPP) Also relevant is XEP-0176: Jingle ICE/UDP Transport Method. I have reached out to jdev mailing list, as well as the author of XMPP Desktop Screen Sharing in Empathy. Unfortunately I was not able to get any major attention. Fixing one2one Desktop Screen Sharing should be fairly simple, but it would be nice if we could do it in a standardized/interoperable way so it will work between different XMPP-clients. Desktop Screen Sharing (as well as give/take control) would be a nice first step. Getting support for conferencing would be great, but would be a major feature leap I guess... i.e need for much more developer resources. [1] http://xmpp.org/extensions/xep-0167.html ___ telepathy mailing list telepathy@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/telepathy
Re: [Telepathy] Project revival?
Hi Alexandr, On 09.06.2016 22:58, Alexandr Akulich wrote: Hi George, It's great to hear about more devs get work on Telepathy. I'm TelepathyQt maintainer for a year now and I'm planning to release 0.9.7 as soon as I'll made a future-proof commit with fix of https://bugs.freedesktop.org/show_bug.cgi?id=95376 for Qt-5.8. It would be helpful if someone would acknowledge or review my changes. I'm definitely up for that. :) Since commit [1] there is no QDBusArgument operators overload for QList. I reported the problem [2] and it seems that the "bad" commit will be reverted for 5.7, but our current approach is deprecated since [3]. I'm going to change tools/qt-types-gen.py script to generate such operators in types-body.hpp: TP_QT_EXPORT QDBusArgument <<(QDBusArgument , const UIntList ) { int id = qMetaTypeId(); arg.beginArray(id); for (int i = 0; i < list.count(); ++i) { arg << list.at(i); } arg.endArray(); return arg; } TP_QT_EXPORT const QDBusArgument >>(const QDBusArgument , UIntList ) { arg.beginArray(); list.clear(); while (!arg.atEnd()) { uint item; arg >> item; list.append(item); } arg.endArray(); return arg; } As far as I see, this would be a full equivalent to the current behaviour, but I didn't fully tested it yet. Would you acknowledge such approach or I'm missing something important? Comment in types.h says that we "needed to have a discrete type in the Qt type system" and we actually do qDBusRegisterMetaType in types-body.hpp, but at the same time we're relying on QList stream operators overload, which ignores any T parts except the base and has no references to the original list object metatype. As far as I understand, the argument "ignores any T parts except the base" does not apply to our type here because T is int and int is a native type that doesn't need further operator overloads. But I can see how for the generic case it's true. In any case, I think your approach is sane. Please go ahead and ping me for a review if you wish. Regards, George [1] http://code.qt.io/cgit/qt/qtbase.git/commit/?id=5f542f3cca13f2da58b82aee2efbaffefeee00a7 [2] https://bugreports.qt.io/browse/QTBUG-53376 [3] http://code.qt.io/cgit/qt/qtbase.git/commit/?id=c7d4858c921c7602dc90d56cdd903cd2cbc6 On Thu, Jun 9, 2016 at 8:02 PM, George Kiagiadakiswrote: Hello all, For those of you that don't know me, I'm an old kde-telepathy & telepathy-qt developer who's been inactive in telepathy for a couple of years. Recently I've been looking again into what is going on in this project and it looks like it's dead, which is a pity. However, I can see there is some limited activity around telepathy-qt, with some people writing new Qt-based CMs (cool!). This little activity makes me hope that maybe it's possible to revive the rest of the project? I'm basically writing this email to declare my interest in attempting a revival. I think free communication is quite important and it's being neglected a lot recently in the FOSS world, which motivates me enough to spend some time again in this project. As a start, I would like to get in touch with all of you who are still working on something related to telepathy. It would be nice to start a conversation about project needs and future plans. So, if you are interested, please get in touch. I am 'gkiagia' on irc and various other places on the internet. Regards, George ___ telepathy mailing list telepathy@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/telepathy ___ telepathy mailing list telepathy@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/telepathy ___ telepathy mailing list telepathy@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/telepathy
Re: [Telepathy] Project revival?
Hello Niklas, On 09.06.2016 18:55, Niklas Andersson wrote: Hi George, We have a project going on that might be of interest. We have worked like crazy to basically bring feature-parity between MS Lync and Pidgin (using the SIPE-plugin) Think of it as the MS Lync client (or Skype for Business), but fully open source, directly available in your software repository. We have touched pidgin, libpurple, libnice, freerdp, gstreamer, farstream to make this happen. And now we support (fully interoperable with MS Lync/SFB): - File Transfer - Desktop Screen Sharing - Conferencing - Video (one2one for now) - SRTP encryption - Lync Enterprise Voice (call-in and call-out via gateway). This is a great start, but I would like to see the same features in other open libraries, and thus available for other clients. Right now it is Pidgin only, which is a pity. Also, I have reached out to the XMPP-community (with not much of response actually..), telling them about this effort and that it would be great to take all these features to XMPP. Right now it is a MS Lync Server-only thing, which is not open source. I would like to see all of this handled by ejabberd for example. That's all super cool. I am interested to hear about all the XMPP additions as well as upstreaming all necessary changes to allow this to work in telepathy as well. There have been efforts in Empathy to implement Desktop Screen Sharing, and I've reached out to the contributor (without getting a response). It would be nice if we could do a joint-effort and make sure there can be some common ground with respect to how the semantics should look like in the XMPP-messages in order to be interoperable. I'm sure interested to try and participate in talks about the XMPP semantics. Regarding empathy, as far as I remember, desktop sharing was working with vino & vinagre through telepathy stream tubes. I guess though you are talking about some more standardized way? All our code is available on Github [1]. SIPE [2] is where we have our wiki [3] The goal is to have all features in the Lync/Skype For Business eco-system, but with protocols and code according to the F/OSS-philosopy. [1] https://github.com/tieto [2] https://github.com/tieto/sipe [3] https://github.com/tieto/sipe/wiki Best regards, Niklas Thanks for letting me know. Regards, George ___ telepathy mailing list telepathy@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/telepathy
Re: [Telepathy] Project revival?
On 09.06.2016 18:47, Daniel Pocock wrote: On 09/06/16 17:02, George Kiagiadakis wrote: Hello all, For those of you that don't know me, I'm an old kde-telepathy & telepathy-qt developer who's been inactive in telepathy for a couple of years. Recently I've been looking again into what is going on in this project and it looks like it's dead, which is a pity. However, I can see there is some limited activity around telepathy-qt, with some people writing new Qt-based CMs (cool!). This little activity makes me hope that maybe it's possible to revive the rest of the project? I'm basically writing this email to declare my interest in attempting a revival. I think free communication is quite important and it's being neglected a lot recently in the FOSS world, which motivates me enough to spend some time again in this project. As a start, I would like to get in touch with all of you who are still working on something related to telepathy. It would be nice to start a conversation about project needs and future plans. So, if you are interested, please get in touch. I am 'gkiagia' on irc and various other places on the internet. George, thanks for being proactive about this Several students are participating as part of GSoC this year, under the umbrella of the Debian project One thing that would help a lot is increasing the pool of mentors, some students are sharing a mentor at the moment. If you or anybody else with C, C++ or Python experience can volunteer as a mentor, please contact me privately. Another thing I would encourage is joining the Free-RTC mailing list, that is where we discuss some of the more strategic possibilities with free software, not just limited to Telepathy: https://lists.fsfe.org/mailman/listinfo/free-rtc Hello Daniel, Great to hear from you. I've heard about the GSoC projects and I'm very happy that you managed to get those students to work in Tp. Being around, I will sure try to answer questions from students, if I can. Also thanks for letting me know about the Free-RTC mailing list. I have now subscribed there as well. Regards, George ___ telepathy mailing list telepathy@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/telepathy
Re: [Telepathy] Project revival?
On 09.06.2016 18:44, Martin Klapetek wrote: Hey George, nice to see you back! On Thu, Jun 9, 2016 at 11:02 AM, George Kiagiadakiswrote: Hello all, For those of you that don't know me, I'm an old kde-telepathy & telepathy-qt developer who's been inactive in telepathy for a couple of years. Recently I've been looking again into what is going on in this project and it looks like it's dead, which is a pity. However, I can see there is some limited activity around telepathy-qt, with some people writing new Qt-based CMs (cool!). This little activity makes me hope that maybe it's possible to revive the rest of the project? I'm basically writing this email to declare my interest in attempting a revival. I think free communication is quite important and it's being neglected a lot recently in the FOSS world, which motivates me enough to spend some time again in this project. As a start, I would like to get in touch with all of you who are still working on something related to telepathy. It would be nice to start a conversation about project needs and future plans. So, if you are interested, please get in touch. I am 'gkiagia' on irc and various other places on the internet. So KDE Telepathy is right now pretty much in maintenance mode for lack of developers, but there is some development by me going into a new KDE/Qt/QML client called SpaceBar, which does not have any public releases yet and is moreless built on top of ktp-common-internals fork, which I would love to get back to master. The primary focus was/is Plasma mobile, but it's very well usable on desktop as well with some nice features like endless-history-on- scroll and full emoji support plus all the goodness of ktp-text-ui filters. Hey Martin, Glad to hear you are still around :) I'm also really happy to learn about your new client. I'm looking forward to see it in action. Cheers, George ___ telepathy mailing list telepathy@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/telepathy
Re: [Telepathy] Project revival?
Hi George, It's great to hear about more devs get work on Telepathy. I'm TelepathyQt maintainer for a year now and I'm planning to release 0.9.7 as soon as I'll made a future-proof commit with fix of https://bugs.freedesktop.org/show_bug.cgi?id=95376 for Qt-5.8. It would be helpful if someone would acknowledge or review my changes. Since commit [1] there is no QDBusArgument operators overload for QList. I reported the problem [2] and it seems that the "bad" commit will be reverted for 5.7, but our current approach is deprecated since [3]. I'm going to change tools/qt-types-gen.py script to generate such operators in types-body.hpp: TP_QT_EXPORT QDBusArgument <<(QDBusArgument , const UIntList ) { int id = qMetaTypeId(); arg.beginArray(id); for (int i = 0; i < list.count(); ++i) { arg << list.at(i); } arg.endArray(); return arg; } TP_QT_EXPORT const QDBusArgument >>(const QDBusArgument , UIntList ) { arg.beginArray(); list.clear(); while (!arg.atEnd()) { uint item; arg >> item; list.append(item); } arg.endArray(); return arg; } As far as I see, this would be a full equivalent to the current behaviour, but I didn't fully tested it yet. Would you acknowledge such approach or I'm missing something important? Comment in types.h says that we "needed to have a discrete type in the Qt type system" and we actually do qDBusRegisterMetaType in types-body.hpp, but at the same time we're relying on QList stream operators overload, which ignores any T parts except the base and has no references to the original list object metatype. [1] http://code.qt.io/cgit/qt/qtbase.git/commit/?id=5f542f3cca13f2da58b82aee2efbaffefeee00a7 [2] https://bugreports.qt.io/browse/QTBUG-53376 [3] http://code.qt.io/cgit/qt/qtbase.git/commit/?id=c7d4858c921c7602dc90d56cdd903cd2cbc6 On Thu, Jun 9, 2016 at 8:02 PM, George Kiagiadakiswrote: > Hello all, > > For those of you that don't know me, I'm an old kde-telepathy & > telepathy-qt developer who's been inactive in telepathy for a couple of > years. Recently I've been looking again into what is going on in this > project and it looks like it's dead, which is a pity. However, I can see > there is some limited activity around telepathy-qt, with some people > writing new Qt-based CMs (cool!). This little activity makes me hope > that maybe it's possible to revive the rest of the project? > > I'm basically writing this email to declare my interest in attempting a > revival. I think free communication is quite important and it's being > neglected a lot recently in the FOSS world, which motivates me enough to > spend some time again in this project. > > As a start, I would like to get in touch with all of you who are still > working on something related to telepathy. It would be nice to start a > conversation about project needs and future plans. So, if you are > interested, please get in touch. I am 'gkiagia' on irc and various other > places on the internet. > > Regards, > George > ___ > telepathy mailing list > telepathy@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/telepathy ___ telepathy mailing list telepathy@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/telepathy
Re: [Telepathy] Project revival?
Hi George, We have a project going on that might be of interest. We have worked like crazy to basically bring feature-parity between MS Lync and Pidgin (using the SIPE-plugin) Think of it as the MS Lync client (or Skype for Business), but fully open source, directly available in your software repository. We have touched pidgin, libpurple, libnice, freerdp, gstreamer, farstream to make this happen. And now we support (fully interoperable with MS Lync/SFB): - File Transfer - Desktop Screen Sharing - Conferencing - Video (one2one for now) - SRTP encryption - Lync Enterprise Voice (call-in and call-out via gateway). This is a great start, but I would like to see the same features in other open libraries, and thus available for other clients. Right now it is Pidgin only, which is a pity. Also, I have reached out to the XMPP-community (with not much of response actually..), telling them about this effort and that it would be great to take all these features to XMPP. Right now it is a MS Lync Server-only thing, which is not open source. I would like to see all of this handled by ejabberd for example. There have been efforts in Empathy to implement Desktop Screen Sharing, and I've reached out to the contributor (without getting a response). It would be nice if we could do a joint-effort and make sure there can be some common ground with respect to how the semantics should look like in the XMPP-messages in order to be interoperable. All our code is available on Github [1]. SIPE [2] is where we have our wiki [3] The goal is to have all features in the Lync/Skype For Business eco-system, but with protocols and code according to the F/OSS-philosopy. [1] https://github.com/tieto [2] https://github.com/tieto/sipe [3] https://github.com/tieto/sipe/wiki Best regards, Niklas On 09/06/16 17:02, George Kiagiadakis wrote: Hello all, For those of you that don't know me, I'm an old kde-telepathy & telepathy-qt developer who's been inactive in telepathy for a couple of years. Recently I've been looking again into what is going on in this project and it looks like it's dead, which is a pity. However, I can see there is some limited activity around telepathy-qt, with some people writing new Qt-based CMs (cool!). This little activity makes me hope that maybe it's possible to revive the rest of the project? I'm basically writing this email to declare my interest in attempting a revival. I think free communication is quite important and it's being neglected a lot recently in the FOSS world, which motivates me enough to spend some time again in this project. As a start, I would like to get in touch with all of you who are still working on something related to telepathy. It would be nice to start a conversation about project needs and future plans. So, if you are interested, please get in touch. I am 'gkiagia' on irc and various other places on the internet. Regards, George ___ telepathy mailing list telepathy@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/telepathy ___ telepathy mailing list telepathy@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/telepathy
Re: [Telepathy] Project revival?
On 09/06/16 17:02, George Kiagiadakis wrote: > Hello all, > > For those of you that don't know me, I'm an old kde-telepathy & > telepathy-qt developer who's been inactive in telepathy for a couple of > years. Recently I've been looking again into what is going on in this > project and it looks like it's dead, which is a pity. However, I can see > there is some limited activity around telepathy-qt, with some people > writing new Qt-based CMs (cool!). This little activity makes me hope > that maybe it's possible to revive the rest of the project? > > I'm basically writing this email to declare my interest in attempting a > revival. I think free communication is quite important and it's being > neglected a lot recently in the FOSS world, which motivates me enough to > spend some time again in this project. > > As a start, I would like to get in touch with all of you who are still > working on something related to telepathy. It would be nice to start a > conversation about project needs and future plans. So, if you are > interested, please get in touch. I am 'gkiagia' on irc and various other > places on the internet. > George, thanks for being proactive about this Several students are participating as part of GSoC this year, under the umbrella of the Debian project One thing that would help a lot is increasing the pool of mentors, some students are sharing a mentor at the moment. If you or anybody else with C, C++ or Python experience can volunteer as a mentor, please contact me privately. Another thing I would encourage is joining the Free-RTC mailing list, that is where we discuss some of the more strategic possibilities with free software, not just limited to Telepathy: https://lists.fsfe.org/mailman/listinfo/free-rtc ___ telepathy mailing list telepathy@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/telepathy
Re: [Telepathy] Project revival?
Hey George, nice to see you back! On Thu, Jun 9, 2016 at 11:02 AM, George Kiagiadakiswrote: > Hello all, > > For those of you that don't know me, I'm an old kde-telepathy & > telepathy-qt developer who's been inactive in telepathy for a couple of > years. Recently I've been looking again into what is going on in this > project and it looks like it's dead, which is a pity. However, I can see > there is some limited activity around telepathy-qt, with some people > writing new Qt-based CMs (cool!). This little activity makes me hope > that maybe it's possible to revive the rest of the project? > > I'm basically writing this email to declare my interest in attempting a > revival. I think free communication is quite important and it's being > neglected a lot recently in the FOSS world, which motivates me enough to > spend some time again in this project. > > As a start, I would like to get in touch with all of you who are still > working on something related to telepathy. It would be nice to start a > conversation about project needs and future plans. So, if you are > interested, please get in touch. I am 'gkiagia' on irc and various other places on the internet. > So KDE Telepathy is right now pretty much in maintenance mode for lack of developers, but there is some development by me going into a new KDE/Qt/QML client called SpaceBar, which does not have any public releases yet and is moreless built on top of ktp-common-internals fork, which I would love to get back to master. The primary focus was/is Plasma mobile, but it's very well usable on desktop as well with some nice features like endless-history-on- scroll and full emoji support plus all the goodness of ktp-text-ui filters. Cheers -- Martin Klapetek | KDE Developer ___ telepathy mailing list telepathy@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/telepathy
[Telepathy] Project revival?
Hello all, For those of you that don't know me, I'm an old kde-telepathy & telepathy-qt developer who's been inactive in telepathy for a couple of years. Recently I've been looking again into what is going on in this project and it looks like it's dead, which is a pity. However, I can see there is some limited activity around telepathy-qt, with some people writing new Qt-based CMs (cool!). This little activity makes me hope that maybe it's possible to revive the rest of the project? I'm basically writing this email to declare my interest in attempting a revival. I think free communication is quite important and it's being neglected a lot recently in the FOSS world, which motivates me enough to spend some time again in this project. As a start, I would like to get in touch with all of you who are still working on something related to telepathy. It would be nice to start a conversation about project needs and future plans. So, if you are interested, please get in touch. I am 'gkiagia' on irc and various other places on the internet. Regards, George ___ telepathy mailing list telepathy@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/telepathy